Prompts that get better code back

Give it the constraint, not just the goal. Weak: "add search" Better: "add search over the tools table using Postgres full text, no new dependencies" Name the files. Weak: "fix the login bug" Better: "in the auth actions file, sign-in fails silently when the password is wrong" Say what done looks like. "Done when a signed-out visitor hitting /bookmarks lands on /login and comes back after signing in." Ask for the smallest version first. "Simplest thing that works. No abstraction for one caller." Make it show you, not tell you. "Run the tests and paste the output" beats "make sure the tests pass". When it goes wrong, give it the error text verbatim. A paraphrased error is a different error.