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.
Five hundred cocktails, chosen one at a time.
$4.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 The Mixologeist: 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
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: Limited variety of cocktail recipes compared to larger apps
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: No social features for sharing experiences
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Only basic filtering options for searching cocktails
Validate with people who use this workflow before building.
Hypothesis 4
Assumption to check: Paid app with no free trial
Validate with people who use this workflow before building.
Original App Store material. Ratings and screenshots describe the existing app, not proof of demand for your version.
Five hundred cocktails, chosen one at a time. Not five thousand scraped off the internet and left to rot. The classic canon in full - the drinks a bartender is expected to know cold - alongside the modern standards that earned the title, and the house recipes worth the trouble of tracking down. Every one is specified properly. Measures written out, down to the dash. The glass, the ice, the method, the garnish. 277 ingredients cataloged behind them, so a recipe calling for amontillado means amontillado, and says so. The name is the promise: a mixologist's catalog kept with an ear to the zeitgeist. What the canon settled, what the last twenty years added, and what is being poured this year. • The full classic canon - Martini, Manhattan, Daiquiri, Negroni, Sazerac, Last Word, and the several hundred others that matter. • Modern classics: Penicillin, Paper Plane, Naked & Famous, Gold Rush, Division Bell. • Whole chapters most books skip - 44 tiki drinks, the flips and fizzes, the swizzles and cobblers, 37 sherry cocktails and a proper low-ABV aperitif hour. • Glass, ice, method and garnish on every drink, because a Manhattan up is not a Manhattan on the rocks. • Scale any recipe from a single serving to a pitcher of twelve. • Read the measures as written, or convert to fl oz, ml or cl. • An ABV on every drink, worked out from what is in it. • Search all 500 drinks and 277 ingredients by name. • Keep favorites, and write your own recipes in alongside the catalog. • New drinks land in the catalog regularly, and arrive on their own - there is no app update to wait for. • Everything you save follows you across your devices through iCloud. Each drink is drawn rather than photographed - its own glassware, the liquid layered by what is in it, the garnish set where a bartender would set it. It moves when you do, though that is the least of what it does. No account. No advertising. No tracking. Nothing to subscribe to. The whole catalog is open the moment you are. Pick a glass. Make something properly.
Written user reviews are not shown here. Check current App Store reviews >
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.