Prompt templates and rules so Claude nails it on the first try.

Prompts that actually work

Most people prompt wrong — they write one sentence and wonder why the output is mid. Here's how to instruct Claude Code so the first output is the one you ship.

The breadcrumbs method

Instead of writing one giant prompt, feed Claude context piece by piece. Like breadcrumbs leading to your goal.

How it works

1. Start with the goal: "I want a landing page for my course"
2. Add context: "Audience is solopreneurs learning Claude Code"
3. Set constraints: "Next.js and Tailwind, one page max, keep it tight"
4. Show examples: "Here's a page I like: [URL]"
5. Iterate: "Hero is good, but the headline needs to be shorter" Every step gives Claude more context. Output gets better with each one — instead of stuffing everything into one prompt and praying.

Prompt templates to copy

Writing code

Build [what] in [language/framework].
Requirements:
- [requirement 1]
- [requirement 2]
- [requirement 3]
Use [library/pattern]. No boilerplate, just what's needed.

Reviewing code

Review this code for:
1. Bugs and edge cases
2. Performance issues
3. Security holes
4. Readability
Give me concrete feedback with line numbers. No praise, just fixes.

Refactoring

Refactor [file/function].
Goal: [what should improve — performance/readability/maintainability]
Constraints:
- External API must stay the same
- Tests must keep passing
- No new dependencies
Show me the plan before you start.

Debugging

Bug: [what's happening]
Expected: [what should happen]
Repro: [steps]
Already tried: [what you've tested]
Find the root cause — no quick fix.

Creating content

Write a [format: reel script / LinkedIn post / newsletter] on [topic].
Audience: [who]
Tone: [casual/professional/provocative]
Hook style: [contradiction/specificity/urgency]
CTA: [what should the reader do]
Length: [word count or duration]

Analysis & research

Analyze [what — site/competitor/data].
I want to know:
1. [question 1]
2. [question 2]
3. [question 3]
Give me real numbers and examples, not generic statements.

Prompt rules that make everything better

1. Be specific

"Make a website" → bad. "Build a one-page landing for a Claude Code course in Next.js and Tailwind. Hero with headline, 3 feature sections, pricing, CTA button." → good. The more specific the prompt, the fewer iterations you need.

2. Give examples

If you want a specific style, show Claude an example. "Write like this LinkedIn post: [example]" works 10x better than "professional but casual."

3. Say what you DON'T want

"No emojis. No intro. No bullet points. Get to the point." — negative constraints often beat positive ones.

4. Let Claude plan first

For complex stuff: "Show me your plan before you start." Saves tokens and nerves because you catch mistakes in the plan before any code gets written.

5. Iterate instead of perfecting

Your first prompt doesn't have to be perfect. Start rough, see what comes back, refine. Three iterations beat 30 minutes of polishing.

Pro tip

If a prompt keeps giving you the same output you want: turn it into a skill. Write it once, call it as a slash command forever. Just tell Claude Code:

Turn this prompt into a skill called "/review": [PROMPT TEXT]. Save it to ~/.claude/commands/review.md and show me how to call it.

🚀 These templates are the starting point. In the community you get 20+ ready-made skills built on the same ideas — install, run, done.

Plus: I share the prompts I actually use that aren't in here.

→ Join the Claude Code Mastery Community

Updated regularly — follow @vine.codes for more.