# Starter kit: Running a company with Claude Code

Cleaned template files from the guide "Running a company with Claude Code: the whole setup" by Robert Dainowski, Stelar Digital. They are cleaned versions modelled on the real setup, with every name, address, customer and number removed. The main-seat block was written for this kit. Take them, change them, make them yours.

Anything you must fill in is written like this: [YOUR NAME]. Search the kit for an open square bracket followed by a capital letter to find them all.

All example content (the bakery-supplies shop, its people and numbers) is invented.

## Set it up in this order (a weekend, as in the guide)

Do not copy everything at once. Add a piece only when something bites you.

Day one
1. Copy RULES-ONE-PAGE.md to a file named CLAUDE.md in your project folder. Fill in the placeholders. Five rules at most.
2. Write your "what is mine" list inside it. Decide what counts as an order from you and what does not.

Day two
3. Copy seats/builder.md and seats/reviewer.md into the .claude/agents folder of your project. That gives you one seat that builds and one that reviews. The reviewer has no write or edit tools and is told to change nothing.
4. Copy REVIEW-LEVELS.md next to your rules and decide the level of each job at the start.
5. Copy commands/shift-end.md into .claude/commands. Copy HANDOFF.md to your project folder. The rules page tells the AI to read it at the start of each session.

Later, when it earns its place
6. seats/reader.md (into .claude/agents/ too), and the block in seats/main-seat.md (pasted into your rules page).
7. commands/open.md and commands/wrapup.md (into .claude/commands/).
8. The memory folder (memory/MEMORY.md plus one small file per lesson).

## Where things live

- Your rules page is the file Claude Code loads as CLAUDE.md, in the project root.
- memory/ and HANDOFF.md live in the project root too, next to the rules page. The rules page tells the AI to read them at the start of every session.
- seats/builder.md, reader.md and reviewer.md go in .claude/agents/. The three commands go in .claude/commands/.

## What each file is

- RULES-ONE-PAGE.md : the one page of rules, as a template, with five worked-example rules and the rule about rules.
- REVIEW-LEVELS.md : three review levels (critical, medium, low) and what each one asks for.
- HANDOFF.md : the empty four-list handoff note.
- HANDOFF-EXAMPLE.md : one filled example, invented. Do not copy it into your handoff.
- seats/main-seat.md : not an agent file. A block to paste into your rules page, for the seat you talk to. It decides and holds the checks. It writes no code.
- seats/reader.md : the cheap, fast seat that finds and reads things and returns a short summary.
- seats/builder.md : the seat that writes code once there is a plan. Two rounds, then you decide.
- seats/reviewer.md : the seat with no write or edit tools. It passes all of the done list or none of it.
- commands/open.md : sitting down. Read everything fresh, show one screen, then wait.
- commands/shift-end.md : leaving the desk. Write the handoff, keep it small, then go.
- commands/wrapup.md : end of a session. Save what the next session needs to know.
- memory/MEMORY.md : the memory index template, one line per memory file.
- memory/user_example.md, feedback_example.md, project_example.md, reference_example.md : one example of each of the four kinds of memory.

## Two things to check before you rely on it

- Model names change. The seat files name the models used when this was written. Put in the ones you have.
- Commands and seats only help if you enforce what they say. A rule you would not enforce should not be on your page.