Find the Claude Code piece you need.
Describe what keeps going wrong and get the one fix that fits.
Example result
1. THE PIECE
.claude/settings.json permissions — a settings file that lists exactly which files Claude Code is allowed (or not allowed) to touch.
2. WHY THIS ONE
Your homepage keeps getting edited when you didn't ask for it, so you need a hard stop — not a polite note. CLAUDE.md is guidance only, so Claude can read "don't touch the homepage" and still do it; a permission rule blocks the file for real.
3. THE FIRST STEP
Open your project folder and check for a .claude folder. No .claude folder? Make one. Then make an empty file inside it called settings.json. That's it — you've got the slot ready. Takes two minutes.
4. WHAT TO SAY TO CLAUDE CODE
Paste this:
In .claude/settings.json, add a permission rule that denies any edits to index.html — my homepage — so you can never change that file. Show me the exact JSON before you save it, and explain in one plain sentence what it does.
One more thing: once that's working, a short line in CLAUDE.md ("the homepage is off-limits") helps Claude understand why — but the permission rule is what actually stops it.
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
How to use the prompt
- 1Write what keeps going wrong in your own words
- 2Add one line about your project
- 3Paste the prompt into Claude
- 4Copy its request into Claude Code
More like thisSetup prompts
Browse all →