Feature spec
Goal: Send a clear invoice after finishing a job.
- Add a client, line items, a due date, and payment instructions.
- Preview the total before exporting a PDF.
- Keep an editable draft if export fails.
Suna is a cookbook that behaves like a kitchen tool.
$6.99
Evidence scope: No current overall US chart position is available. Category-chart positions shown in discovery are a separate scope. Revenue is a directional model estimate, not verified earnings.
A product spec, screen plans, and build steps for your coding agent.
First kit free with a verified email
Combine features and design from your favorite apps.
Kit ready. Verify your email to download it.
Generating… usually about a minute.
What should your app do differently? Your note travels with the kit so your coding agent builds around your idea.
A product spec, phased build plan, differentiation notes, and screen references.
Illustrative example: an invoice app for independent contractors. Your kit is tailored to the app you choose; this is not its generated content.
Goal: Send a clear invoice after finishing a job.
Invoice editor: Client at the top, editable line items in the middle, total and preview action at the bottom.
States: Empty draft, validation errors beside each field, exporting, and a retry action that preserves the draft.
Hypothesis: Contractors need faster repeat invoices more than more templates.
First experiment: Test duplicating a previous job with five contractors. Watch where they hesitate before expanding the feature set.
The full kit adds a phased build plan, evidence notes, tool prompts, and implementation guidance. It is a plan for your coding agent, not a finished app.
Usage: Mechanics are fair game; never reuse the original name, branding, assets, or verbatim copy.
JavaScript is required to complete mailbox verification.
Good fit for mobile-first iOS and Android prototypes with managed app scaffolding.
Rork plan preview for Suna Recipes: map the core Food & Drink workflow, choose the smallest differentiated feature set, define the data and monetization boundaries, then prototype the riskiest user journey first.
Preview ready. Verify your email to reveal and copy the full prompt.
JavaScript is required to complete mailbox verification. Return to this prompt preview.
Affiliate link: CloneChart may earn a commission at no extra cost
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Suna is a cookbook that behaves like a kitchen tool. Thousands of recipes, every one of them readable with no signal — on a train, in a cellar kitchen, or on a phone with no data left. Nothing to load, nothing to wait for. COOKING, NOT SCROLLING Cook Mode shows one step at a time in type you can read from across the counter, and keeps the screen awake while your hands are covered in flour. No life story before the ingredients. No video that starts playing by itself. SCALING THAT UNDERSTANDS FOOD Change the servings and every quantity moves with them — but not all in the same way. Double a stew and you do not double the salt or the chilli, and Suna knows the difference. It tells you when a bigger batch needs a bigger pan, too. A SHOPPING LIST THAT WRITES ITSELF Add a recipe and its ingredients land in the list already sorted by aisle, with duplicates merged and anything in your cupboard left out. Share one list with the people you live with and it stays in step on every phone, even offline. ALLERGIES ARE HIDDEN, NOT FLAGGED Tell Suna what you cannot eat and those recipes disappear from the whole app. Not a warning you have to notice halfway down a page — gone. WHAT SHALL I COOK? - Three ideas, chosen for the hour and for what you have not cooked lately - "What can I make?" — tap what is in the fridge and see what it adds up to - A weekly plan, so Thursday is decided on Sunday - A daily reminder, if you want one, that says what is on the plan NO ACCOUNT NEEDED Browsing, searching, cooking, scaling, planning, your cupboard, your allergies and your own shopping list all work without signing in, and always will. An account is only needed for four things: writing a review, reporting or blocking one, sharing a list with a household, and deleting your account. Your allergies, saved recipes, cupboard and meal plan stay on your phone either way — they are never sent anywhere. Made by people who cook.
Written user reviews are not shown here. Check current App Store reviews >
These are generated suggestions, not verified review quotations. Check current App Store reviews and speak with users before treating a possible gap as a requirement.
Hypothesis 1
Assumption to check: High delivery fees
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Inaccurate ETAs
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Limited restaurant selection
Validate with people who use this workflow before building.
Plan a focused first version with your coding agent. These are planning assumptions, not a delivery guarantee.
Choose one audience and one core workflow. Use the kit to agree on its screens, data, and acceptance criteria before building.
Decide which secondary features, integrations, and platform support can wait. Your version does not need to reproduce everything in the original.
Validate external services, specialist technology, data access, and ongoing costs for your chosen scope.
From the Build Kit assessment.
A reliable timeline needs an agreed scope and a technical check. Ask your agent to estimate the phases in BUILD_PLAN.md after that review.