Start from a templatePopular starting points — or write your own below
Objective*One outcome, verb-first. Say what is different in the world when it's done.GoodAdd CSV export to the admin users table that respects the current filtersAvoidImprove the admin pagewhat must be accomplished
ContextFacts the model can't guess: stack and versions, what exists today, scale, who it's for.GoodNext.js 16 App Router + Supabase. users table ~40k rows. Exports are done manually via SQL today.AvoidOur appstack, codebase, constraints
AudienceWho reads it, what they already know, and what they need to decide or do.GoodOps leads at 50–500 person companies; non-technical; skimming on mobileAvoidEveryonewho it's for
ToneTwo to four adjectives plus one thing to avoid.GoodPlain, confident, a little dry — no hype words or exclamation markshow it should sound
DeliverableThe concrete artifact and its shape: PR, doc, JSON, email — with size or sections.GoodA PR with route handler, export button component, and testsAvoidA solution
Success criteriaTestable checks, one per line. If you couldn't verify it, rewrite it.Good10k-row export completes in < 5s
CSV opens cleanly in Excel (UTF-8 BOM)
All tests and typecheck passAvoidWorks well · is fastone per line
Must-dos & don'tsHard limits plus the reason. Reasons let the model generalise to cases you didn't list.GoodNo new dependencies — because the bundle budget is already at its limitAvoidBe careful · follow best practicesthe why makes models follow them
because
Write an objective to continue.
Output
Describe what you need (or pick a template) → answer a few quick questions → get a prompt that's ready to paste.
Then tweak it in plain English.
Your draft and versions are saved in this browser. Sign in to sync them.