The best developers have toolkits. With Claude Code, your toolkit becomes a collection of refined prompts and patterns.
Why Build a Toolkit?
Great prompts are discovered, not invented. When you find something that works, save it. Refine it. Reuse it.
My Essential Templates
The Debug Template
"I’m seeing [error/behaviour]. Expected: [what should happen]. Actual: [what’s happening]. Relevant code: [paste]. What are the most likely causes and how do I diagnose each?"
The Architecture Review Template
"I’m building [feature] with [constraints]. Here’s my proposed approach: [description]. What are the trade-offs? What alternatives should I consider? What will I regret in 6 months?"
The Learning Accelerator
"Explain [concept] as if teach…
The best developers have toolkits. With Claude Code, your toolkit becomes a collection of refined prompts and patterns.
Why Build a Toolkit?
Great prompts are discovered, not invented. When you find something that works, save it. Refine it. Reuse it.
My Essential Templates
The Debug Template
"I’m seeing [error/behaviour]. Expected: [what should happen]. Actual: [what’s happening]. Relevant code: [paste]. What are the most likely causes and how do I diagnose each?"
The Architecture Review Template
"I’m building [feature] with [constraints]. Here’s my proposed approach: [description]. What are the trade-offs? What alternatives should I consider? What will I regret in 6 months?"
The Learning Accelerator
"Explain [concept] as if teaching a developer who understands [related concept] but not [this concept]. Use analogies from [their domain]."
The Test Generator
"Generate tests for [function] that cover: happy path, edge cases, error conditions, boundary values. Include setup and teardown. Format for [testing framework]."
The Documentation Writer
"Document [code] for three audiences: a quick reference for experienced users, a detailed guide for new team members, and inline comments explaining the ‘why’."
Building Your Own
Start by saving prompts that get good results. After each session, ask yourself: "Would I use this prompt again?" If yes, save it.
Refine by iteration. Each time you use a template, note what worked and what didn’t. Update the template.
Organise by task. Group prompts by what you’re trying to accomplish: debugging, documentation, learning, code generation.
The Meta-Toolkit
The most powerful prompt: "I want to accomplish [goal]. What questions should I be asking you to get the best result?"
Let Claude Code help you build better prompts.
At Logic Leap, we help teams develop systematic approaches to AI-assisted development. Want to build a team-wide prompt toolkit? We can help.
Share your favourite prompt templates below!