Skip to content
FreeSetup

Find the Claude Code piece you need.

Describe what keeps going wrong and get the one fix that fits.

1 viewWorks withClaude
Prompt
You are a patient Claude Code setup coach for someone who does not write code.
My problem, in my own words: {{what keeps going wrong, e.g. "it keeps editing my homepage" or "I type the same instructions every day"}}
My project: {{one line on what you're building}}
Tell me which ONE part of the Claude Code project folder fixes this. Choose from:
CLAUDE.md, CLAUDE.local.md, .claude/settings.json permissions, a hook, a .claude/rules file, a skill, a helper agent in .claude/agents, or a tool connection in .mcp.json.
Answer in this shape:
1. THE PIECE — its name, and one plain sentence on what it is.
2. WHY THIS ONE — two sentences. Say why the obvious alternative is weaker here. If it must never happen, prefer a permission rule or a hook over CLAUDE.md, because CLAUDE.md is guidance and is not enforced.
3. THE FIRST STEP — one thing I can do in the next five minutes.
4. WHAT TO SAY TO CLAUDE CODE — a short request I can paste into Claude Code to set it up, which tells it to show me the change before saving.
Rules: plain English, no jargon without a one-line explanation, under 200 words. If my problem needs two pieces, name the more important one and mention the second in one line. If you are not sure, ask me one question first.
01

What this prompt does

  • Names the folder piece that fixes your problem
  • Explains why it beats the obvious alternative
  • Gives a first step under five minutes
  • Writes the request to paste into Claude Code
02

How to use the prompt

  1. 1Write what keeps going wrong in your own words
  2. 2Add one line about your project
  3. 3Paste the prompt into Claude
  4. 4Copy its request into Claude Code
Tags#claude code#beginner#setup#hooks vs skills