How to write prompts that produce production-grade code, not toy snippets.
Section
CRISP Framework
Context, Role, Intent, Structure, Proof. Every serious prompt has all five.
Section
Give Real Context
Paste the file. Paste the schema. Never say "the user table" — show it.
Section
State Constraints Up Front
No new dependencies. No breaking API changes. Must pass the existing tests.
Section
Ask for Structure
"Return a diff." "Return only the modified functions." "Return JSON matching this shape."
Section
Review, Do Not Rubber-Stamp
Read every line. Reject the ones you would not have written yourself.