CLAUDE.md

Claude Code Notes

• Claude Code reads CLAUDE.md at session start; keep this file concise, specific, and under 200 lines.
• Use this file for project facts Claude should know every session: commands, conventions, architecture, and repeat corrections.
• Move multi-step procedures into .claude/skills/<skill-name>/SKILL.md.
• Move path-specific conventions into .claude/rules/*.md with paths frontmatter when the rule only applies to part of the repo.

Fill This In First

Material	Starter value
Memory location	./CLAUDE.md for root project memory, or ./.claude/CLAUDE.md when the team keeps Claude config together
Claude Code behavior	Plan mode guidance, memory boundaries, rules, skills, permissions, or verification conventions
First files to inspect	README files, package manifests, CI config, docs, and existing scripts
Common Claude Code task	install dependencies, run the right checks, and make a small safe change
Main risk	too much generic guidance hides the few project facts Claude should load every session

Memory Boundaries

• Keep always-loaded memory short: commands, architecture landmarks, repeat corrections, and hard constraints.
• Every line should be something Claude needs in most sessions; remove tutorials, stale notes, and generic advice.
• Put path-specific rules in .claude/rules/ so they load only when matching files are relevant.
• Put repeatable procedures in skills so their full instructions load only when invoked.

Commands

• Install dependencies: pnpm install
• Lint: pnpm run lint
• Typecheck: pnpm run typecheck
• Test: pnpm run test
• Build: pnpm run build

Project Context

• Context source to inspect first: README files, package manifests, CI config, docs, and existing scripts.
• Primary audience: Claude Code sessions entering a shared project.
• Common Claude Code task: install dependencies, run the right checks, and make a small safe change.

Verification

• Prefer focused checks that match the edit before running the full suite.
• For UI changes, capture a browser screenshot or describe the visual check performed.
• Report commands run and any checks skipped with the reason.
• Use /memory to inspect loaded project memory when behavior does not match this file.

Rules And Skills Split

• Use .claude/rules/testing.md for test conventions that only matter near test files.
• Use .claude/rules/frontend.md for UI conventions that only apply under frontend paths.
• Use .claude/skills/<skill-name>/SKILL.md for repeatable workflows with inputs, steps, and outputs.
• Keep this file as navigation and durable memory, not a long procedure manual.

Critical Warnings

• Do not store personal sandbox URLs, private tokens, or local-only preferences here; put them in CLAUDE.local.md and gitignore it.
• Remove outdated or contradictory rules during review.
• Risk to watch for this pathway: too much generic guidance hides the few project facts Claude should load every session.

Local Notes

• Personal notes belong in CLAUDE.local.md, not in this shared file.
• Personal cross-project preferences belong in ~/.claude/CLAUDE.md.

Test Prompt

Ask Claude Code: "Summarize the CLAUDE.md, CLAUDE.local.md, and .claude/rules files you loaded for this repo. What would you do before a Claude Code project onboarding change?"