Claude Code Starter Rules 💻

From @techyai_cj. Two things here: the exact first task to try if you just downloaded Claude Code, and the rules file that makes it follow YOUR rules in every session after that. You do not need to know how to code for either one.

The exact first task to try

1. Make a new folder on your desktop called practice.

2. Open Claude Code and point it at that folder. That is the only question it asks you.

3. Paste the prompt below and hit enter.

Build me a single page workout tracker I can open in my browser. Dark theme, works on my phone. I add an exercise, sets, and reps, and it saves them so they are still there when I come back. Explain what you built in two sentences when you are done.

It asks permission before every step. Say yes. When it finishes, open the file it made and actually use it. That is the moment this clicks. Then change something: "make the buttons bigger" or "add a weight column." Same folder, plain English, still no code.

There is also a terminal version if you are a developer. Same tool, black screen, no window. The desktop app is easier if you are starting out.

Then: the rules file

1. Open your project folder in Claude Code.

2. Create a file named CLAUDE.md in the project root (or run /init and let Claude draft one).

3. Paste the rules below and edit them to your project. Done. It reads them automatically from now on.

The starter rules

# Project rules

## How to work with me
- Before changing anything, give me a short plan and wait for my ok.
- Explain what you changed in plain English, one short paragraph.
- If you are not sure what I meant, ask. Do not guess on big decisions.
- When something fails, show me the actual error before trying fixes.

## Code style
- Match the style that already exists in this project.
- Small changes over big rewrites. Never refactor what I did not ask about.
- No new dependencies without asking me first.

## Off limits
- Never touch: [folders or files you want protected, like .env, secrets, deploy scripts]
- Never commit or push unless I say so.

## About this project
- What it is: [one sentence about your project]
- How to run it: [the command, like npm run dev]
- How to test it: [the command, like npm test]

Why these work: the plan-first rule saves you from surprise rewrites, the plain English rule keeps you in control even if you do not read every line, and the off-limits list is your seatbelt. The project section pays off forever: Claude stops asking you how to run things.

Level up: you can also say "add a rule to CLAUDE.md: [rule]" whenever Claude does something you never want again. The file grows with you. That is the whole trick.

© 2026 CJ · free to use, share it with a developer