When to use each, the variables to fill, copyable text, a filled example, and a misuse warning. Good prompts raise the odds; preview and tests still decide.
24 recipes
Clarify an app idea p01-clarify-idea
You have a vague idea and need one user plus one first version.
My idea: [idea]. It helps [who]. Suggest the smallest first version: one user, one main task, three must-have features, and what stays out of scope.
abm02l5 · aba04
Example, expected output, misuse
Filled: neighborhood bakery page for phone orders. Output: one page, three sections, order by phone first.
A narrowed scope you can check: user, task, three features. Check: can you name what is out?
Misuse: Pasting the idea and asking for the full finished app at once.
Describe the target user p02-target-user
The idea fits everyone and therefore no one; pick one user.
Candidates: [candidate users]. Situation: [situation]. Pick one primary user and explain in two sentences why the others wait for later.
abm02l5 · aba04
Example, expected output, misuse
Filled: plumber on a phone call. Others (office staff, suppliers) wait.
One named user plus a waiting list. Check: does every feature serve that user?
Misuse: Listing five users and building for all of them.
Narrow the scope p03-narrow-scope
The feature list keeps growing; split must, later, never.
Features: [feature list]. Sort into MUST (first version), LATER, NEVER. Drop anything needing payment, login or booking from MUST.
Forbidden files untouched. Check: review the diff file list.
Misuse: Allowing all files then complaining about breakage.
Review the diff p17-review-diff
A change is proposed; decide line by line.
Diff: [paste the diff]. Explain each hunk in one line: what changed, why, and which check covers it. Flag anything unrelated.
abm06l22 · aba16
Example, expected output, misuse
Filled: two-hunk fix. Output: two lines plus one flagged extra.
Unrelated changes spotted. Check: is there a hunk no check covers?
Misuse: Accepting a long diff without reading it.
Write a bug report p18-bug-report
It is broken and you cannot say how; package the facts.
Expected: [expected]. Actual: [actual]. Steps: [steps]. Last change: [last change]. Turn this into a short report with the next three checks. Remove any secrets first.
abm07l26 · aba19
Example, expected output, misuse
Filled: button dead after style edit. Report: repro, suspect, three checks.
Someone else could reproduce. Check: hand it to a friend unedited.
Misuse: Sending it is broken with a screenshot of the whole screen.
Test one hypothesis p19-one-hypothesis
Three guesses at once; slow down to one.
Guesses: [guesses]. Pick the cheapest to test, tell me the single check, and what each outcome proves. One at a time.
abm07l28 · aba20
Example, expected output, misuse
Filled: string plus number. Test: log the types first.
One test, one conclusion. Check: did you change only one thing?
Misuse: Changing code, data and config together.
Write the five tests p20-write-tests
It opens so it must work; prove it with cases.
Feature: [feature]. Write five checks: normal, empty, invalid, mobile 360px, and one old feature that must keep working.
abm07l27 · aba21
Example, expected output, misuse
Filled: quote math. Output: five runnable steps with expected values.
Failing test first, passing after fix. Check: does one test fail before the fix?
Misuse: Only testing the happy path.
Regression check p21-regression
A fix lands; prove nothing else broke.
Fixed: [what was fixed]. Old features: [old features]. Re-run each old check and report pass or fail with the evidence.
abm07l27 · aba20
Example, expected output, misuse
Filled: button fix, save must survive. Output: save check passes with reload proof.
Old suite green. Check: is every old check listed, not just the fixed one?
Misuse: Testing only the fixed line.
Plan the rollback p22-rollback-plan
About to try something risky; know the way back.
Working state: [current working state]. Risky change: [risky change]. Tell me how to snapshot now, how to restore, and how user data survives the restore.
abm06l22 · aba17
Example, expected output, misuse
Filled: working tracker, risky filter rewrite. Plan: copy files, restore steps, data safe.
Restore practiced once. Check: can you restore in under five minutes?
Misuse: Trying the risky change with no saved copy.
Hand off the context p23-handoff
Starting a fresh chat; carry the project along.
Goal: [goal]. Decisions: [decisions]. Open bugs: [open bugs]. Next: [next task]. Pack this into a handoff under 20 lines, no secrets, no full chat history.
abm06l23 · aba18
Example, expected output, misuse
Filled: tracker app, filter decision, save bug open, next is export. Output: compact handoff.
New chat continues without re-asking. Check: does it ask for anything already decided?
Misuse: Pasting the entire chat history as context.
Write the README p24-readme
Project works; explain it honestly for delivery.
Does: [what it does]. Does not: [what it does not]. AI helped with: [AI contribution]. Write a short README with limits first and the five tests listed.
abm08l32 · aba24
Example, expected output, misuse
Filled: tracker does tasks and streak, no sharing, AI helped with filter logic.
Limits visible before features. Check: is the not-list longer than one line?
Misuse: Claiming the app does everything with no limits.