:CODE [language:plaintext]
Read the three files I linked. Do not write code yet.
Tell me which of them owns the thing I am about to change,
and tell me what will break if I change it there.


:INFO
Prompts that produced real things
Every prompt on this page shipped something. That is the only bar. There is no theory here and no framework, because the prompts that survive contact with a real codebase are boring and specific, and the clever ones you screenshot for the timeline mostly are not. The one above is the highest leverage thing here. Asking for the blast radius before asking for the change turns a confident wrong answer into a useful question.


:CODE [language:plaintext]
That worked. Now delete everything you added that we did not use,
and show me the diff before you apply it.
---
You have tried this three times. Stop.
Explain what you think the code does, line by line,
and I will tell you where you are wrong.
---
Write the test first. Make it fail for the right reason.
Show me the failure output before you touch the implementation.


:POLL
Which of these do you actually use?
Ask for the blast radius first
Make it explain before it retries
Test first, prove the failure
I write one line and hope

:LINK
https://docs.claude.com/en/docs/claude-code/overview
The tool most of these were written against