Starting your first project

Download the starter CLAUDE.md

epivo.ai/starter/CLAUDE.md — save it as CLAUDE.md in your project folder.

In VS Code:

  1. Create a new folder anywhere on your computer — this is your project
  2. Open VS Code → File → Open Folder → select your project folder
  3. Move the downloaded CLAUDE.md into the folder
  4. Open Claude Code: click the Claude icon in the left sidebar, or press Cmd+Shift+P (Mac) / Ctrl+Shift+P (Windows) and type "Claude Code"
  5. Send your first message: "Read CLAUDE.md and tell me what the process is before we start."

From the terminal (Claude Code CLI):

  1. mkdir my-project && cd my-project
  2. Move the downloaded CLAUDE.md into this folder
  3. Run claude to start a session
  4. Send your first message: "Read CLAUDE.md and tell me what the process is before we start."
Starting your first project

What the file contains

Mandatory Process is the 7-step workflow Claude follows for any non-trivial change. The review agent step deserves attention: it works because the reviewer has no context from the original conversation. This cold read catches assumptions and complexity that you and the implementing Claude both missed. The shortcut pre-authorizes the full cycle — use it when the task is clear and you want fast turnaround.

Writing Plans translates directly from experience. AI tools tend to propose complex solutions because they have seen many patterns. The three bullets target the most common failure modes: new tables instead of columns, excessive UI tabs, and complex rebuild jobs when simple queries would do. The plan format — Title, Problem, Solution, Verification — is intentionally minimal. The goal is a fast artifact, not a specification document.

Working Conventions handles the session boundary problem. Claude has no memory across sessions. Without a changelog, each new session starts blind. With one, Claude reads recent entries and immediately understands what changed and why. The conventional commits format supports automated tooling and makes the git history readable to anyone who opens the repository later.

What the file contains

First message after setup

Read CLAUDE.md and tell me what the process is before we start.

Claude will repeat the 7-step process back to you. That confirms the file was absorbed correctly. Then give it your first task.

Frequently asked questions

Do I need to update CLAUDE.md as the project evolves?
Yes. CLAUDE.md is a living document. Add sections as your project develops specific conventions — deployment commands, tech stack notes, recurring patterns. Remove sections that no longer apply. The goal is that any new Claude session can read CLAUDE.md and immediately understand how to work in this project.
What is the difference between using the shortcut and not using it?
Without the shortcut, Claude stops at step 4 for explicit approval before implementing. The shortcut — saying 'follow the process' — means the original task is the approval: Claude writes the plan, spawns the review, incorporates feedback, and implements without pausing. Use the shortcut when the task is clear and you want fast turnaround. Pause at step 4 when the task is ambiguous or consequential.
Do I need separate template files for changelogs and plans?
No. The format specifications in CLAUDE.md are enough. Claude will produce consistent changelog entries with Added, Changed, and Fixed sections, and plans with Title, Problem, Solution, and Verification sections, based on the inline instructions. Template files are optional extras for teams that want a formal starting point — they are not needed for the methodology to work.
Learn the Socratic approach to AI development →