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.
Cards don't line up politely here
$2.99 · In-app purchases
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.
Your first Build Kit is free with a verified email.
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 ArcFlush: Roguelike Solitaire: map the core Games 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.
Cards don't line up politely here. They're stacked in layers — the way mahjong tiles are stacked, except these are playing cards, and one of the maps is on fire. Which means there are two games sitting on top of each other: getting a card out of the pile, and knowing what to do with it once you have it. HOW IT WORKS · The map is a layered formation. Anything underneath is locked until you clear what's covering it, so every card you take decides what you're allowed to take next. That half is solitaire. · Play up to five of the cards you've taken as a poker hand. A pair is fine. A Flush is better. A Straight Flush means you planned ahead — or got lucky and will claim you planned ahead. That half is poker. · Beat the stage's target score, spend what you earned in the Shop, and do it again. And again. Until the target has grown a couple of digits and you're no longer certain which of your trinkets is doing the heavy lifting. WHAT'S IN IT · Every map is built around exactly one idea. Ice Lake freezes cards. Furnace sets them alight. Dark Pool turns the lights off and invites you to feel your way out. · Clear a map and its Twist unlocks: the same map, in a considerably worse mood. · Trinkets. Some add points. Some quietly rewrite a rule you'd assumed was permanent. The legendary ones turn up rarely enough that finding the right one feels like the run has decided to help you, just this once. · A Shop between stages, because a roguelite without a shop is just a difficult puzzle. · A tutorial that leaves quickly and waits in Settings in case you ever want it back. WHAT'S NOT IN IT · Ads. · In-app purchases. · A season pass, a battle pass, or a little bar that refills while you sleep. · An internet connection. This app has never phoned home and wouldn't know who to call. Buy it once and own all of it — every map, every trinket, every Twist. There is nothing else to sell you, and we are not going to think of anything. One deck, thirteen languages. Good luck.
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: Limited replayability due to fixed card mechanics
Validate with people who use this workflow before building.
Hypothesis 2
Assumption to check: Some users may find the learning curve steep
Validate with people who use this workflow before building.
Hypothesis 3
Assumption to check: Potential for in-app purchase fatigue
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.
Not assessed in a Build Kit yet.
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.