PROMPT GUIDE
Emergent is an agentic builder that decomposes your request into its own task plan. It does not want step-by-step instructions — it wants a clear goal, constraints, and acceptance criteria it can self-check against. Here is that shape, plus a free generator that writes it for you.
Generate your prompt — free, no sign-up
Say what must be true when done and what must not change. Let Emergent design the how — giving it code-level steps fights its strength.
"A web app" or "a mobile-friendly web app" — one line up front. It shapes every downstream decision Emergent makes.
Emergent self-checks well. "A visitor can submit the form and see a success state; submissions appear in the admin list" — checkable statements get checked.
"Integrate Stripe checkout" — naming the capability (or vendor, when you care) lets Emergent wire providers itself instead of stubbing them.
When Emergent shows its decomposition, read it. Fixing a wrong task at planning time costs one edit; after the build, it costs the build.
Goal: [one-sentence outcome]. Platform: web app (mobile-friendly). Requirements: - [Checkable requirement] - [Checkable requirement] Constraints: - Do not change [existing thing that must stay]. - [Performance/style constraint if any]. Integrations: [e.g., "Stripe checkout", "transactional email"]. Accept when all requirements above are demonstrably met.
No — it builds its own task plan and follows instructions better as goals than as recipes. Spend your prompt on the outcome, the constraints, and checkable acceptance criteria.
State it as a constraint in plain words: "do not modify the existing checkout flow." Constraints are one of the two things Emergent respects most, alongside criteria it can verify.
Under-specifying the goal. "Build me a booking app" leaves Emergent guessing the entire domain. One extra sentence of who books what, and when, changes the build completely.
replit · base44 · coding agent