Built on Claude Code best practices
Proven prompts for
Proven prompts for
coding with Claude
A curated directory of short, high-signal prompts for every stage of your
workflow. Copy one, fill in the <blanks>, and ship.
20 prompts 4 categories updated Jul 2026
The library
Pick a category
Four stages of the coding loop. Each opens a filterable directory.
Build
Scaffold features, endpoints, and components with a plan-first approach.
5 prompts →Debug
Find root causes, reproduce failures, and fix bugs without guesswork.
5 prompts →Refactor
Restructure and simplify code safely while preserving behavior.
5 prompts →Review
Audit diffs for correctness, security, and readiness before shipping.
5 prompts → Start here
Highest-signal prompts
If you only take four, take these.
Diff review A focused correctness pass on the change you just made. Review review correctness
Review my current diff for correctness bugs and edge cases only. List findings by severity (high/medium/low). Skip style nits and formatting.Extract & dedupe Remove duplication without altering behavior. Refactor dry extraction
@<file> has repeated logic in <functions>. Extract a shared helper without changing behavior. Keep the public API identical, and run the tests to confirm nothing broke.Plan-first scaffold Get an agreed plan before a single line is written. Build planning scaffolding
Before writing any code, outline a short plan for <feature>: the files you'll create or touch, the key functions, and the data flow between them. Wait for my OK, then implement.Root-cause first Understand a bug before touching any code. Debug diagnosis triage
Here's the error: <paste>. Don't fix anything yet — trace the root cause, list the top 2 hypotheses ranked by likelihood, and tell me which files to look at.