Make Every Claude Prompt Smarter Over Time

Most people’s prompts are frozen in time. You wrote it in March, you’ve run it 80 times since, and it’s basically the same prompt it was on day one.

Here’s the 3-point review block I add to the bottom of every prompt I rely on, plus the weekly habit that keeps it getting better instead of going stale.

When you first build a prompt, you tune it hard. It misses your brand voice, so you add a voice paragraph. It writes generic openings, so you add three examples.

Then it gets good enough and you stop touching it. From there it slowly drifts away from what you actually need. Your business changes, your taste sharpens, and the models get updated, but the prompt stays the same.

The fix is to build the upgrade loop into the prompt itself, so you never have to remember to do it (you won’t).

Paste this at the bottom of any prompt

Add it to the end of any prompt, skill or Project instructions. Every time Claude finishes the main task, it hands you a short, honest debrief.

Review Block

At the end of every response, add a section called REVIEW with exactly three bullet points: 1. WHAT WORKED. The strongest part of what you just produced and why. Be specific: cite the line, the choice, or the input that made it work. 2. WHAT WAS WEAK. The part that felt worst. Where you had to guess, fall back on generic language, hedge, or skip a real answer. Be honest, not diplomatic. 3. WHAT TO ADD BEFORE NEXT RUN. The single highest-leverage change to this prompt, its examples, the instructions, or the knowledge files that would have made this run noticeably better. Write it as a concrete line I can paste in, and say exactly where it goes. Always include REVIEW. Keep each bullet to 2 sentences max. No marketing tone. Treat it like an honest post-run debrief between you and me.

I tested 5-question versions, 7-question versions and full rubrics. They all bloat the output and stop being useful by week three. Three is what survives.

Skim the reviews

Once a week, open the chats for the prompts you use most and scroll through that week’s REVIEW sections. Most are minor. About one in five has something genuinely useful, like a missing instruction or an example you should add.

Let Claude do the rewrite

Paste the current prompt and the week’s notes into a new chat with this.

Weekly Prompt Upgrade

You're helping me upgrade a prompt I use every week. Here is the current prompt: [PASTE THE PROMPT, SKILL OR PROJECT INSTRUCTIONS] Here are the REVIEW sections from this week's runs: [PASTE THE REVIEW NOTES] Do this: 1. Group the "what was weak" and "what to add" notes into themes. Ignore one-offs that only showed up once and don't matter. 2. Pick the 1 to 3 changes that would improve the most future runs. For each, tell me why in one sentence. 3. Rewrite the full prompt with those changes built in. Keep my wording everywhere else, and don't make it longer than it needs to be. 4. Show me a short "what changed" list at the top so I can approve or reject each change. Don't add new rules I didn't ask for, and don't remove anything that the reviews say is working.

Approve and save

Keep the changes you agree with and paste the new version back wherever the prompt lives. After a month it’s noticeably smarter than the day you wrote it.

Instead of pasting the block into every prompt, install it once as a skill. I made it for you.

↓ Download the Self-Review skill (.zip)

Turn on code execution. In Claude, go to Settings, then Capabilities, and turn on Code execution and file creation (called Create and edit files in some accounts).
Upload it. Go to Customize (being renamed Plugins), then Skills. Click +, then Create skill > Upload a skill, and pick the ZIP. Don’t unzip it first.
Use it. Add "with self-review" to any request and Claude adds the REVIEW at the end.

Claude decides when to use a skill by reading its description. (How skills work)

Make EveryClaude PromptSmarter Over Time

Make Every
Claude Prompt
Smarter Over Time