Prompting guide
How to describe what you want and get a great result.
Codify handles vague prompts fine — but specific prompts get you a product that feels designed for you on the first try.
Say what it does
Lead with the job: “an invoice tracker for freelancers”, “a flashcard app for med students”. The builder infers screens, data, and flows from the job better than from a feature list alone.
Name the screens you care about
“Home shows today’s tasks, a stats page with weekly charts, and a settings page” gives the architecture pass exactly what it needs. Four or more distinct surfaces automatically routes your build through the multi-file pipeline.
Set the vibe in a few words
“Clean and minimal”, “playful like Duolingo”, “dark, pro, like a trading terminal” — the design system responds strongly to one clear direction.
For games, describe the moment-to-moment
“A side-scrolling runner where I dodge obstacles and collect coins, gets faster over time” produces a better game than “make a fun game”. Mention a setting (“neon city at night”) and the art pass will build the scene around it.
Iterate in small steps
After the first build, make one change per message. Small asks are patched quickly and cheaply; giant “change everything” asks are slower and easier to get wrong. Every change is checkpointed, so you can always roll back.