Tell an AI "make it like Habitica" and it will interpret that its own way. Most disappointing vibe-coding results are not a code problem — they are a communication problem.
This tool walks you through the big decisions behind an app or game — product type, platform, scope, accounts and data, monetization, navigation, core game screen, camera, art direction, character proportions, asset spec and stack — with visual examples, then turns your choices into a Markdown blueprint any AI coding tool can follow.
Every option has an ID (e.g. N1, G2) and an implementation spec, so the blueprint reads like "[S2] Sticky header + scrolling list → pinned top region (≤35% of viewport); only the lower list scrolls". Less room for guessing.
If your product has a character, you also get an asset spec: base resolution, foot baseline, scale ratios (door 1.5 · house 3 · props 0.3–0.5), direction count by camera, and an estimate of how many images you need — so style and size stay consistent to the end.
Pick accounts, push, payments, location or community features and a pre-launch checklist is added automatically (not legal advice).
1) Go step by step, or start from a similar product (Habitica, Finch, Duolingo, Toss, Cookie Run…). 2) Leave anything you are unsure about blank — the blueprint tells the AI to propose defaults and confirm. 3) On the last step, copy the full blueprint, summary or build plan into Claude, Cursor, Lovable or v0.
Only in this browser; nothing is sent to a server. Copy the share link to open the same blueprint on another device or send it to someone.