Setup / Claude Code

My Claude Code Setup

Skills, agents, hooks, slash commands, references, plus the behavior rules in CLAUDE.md and AGENTS.md. The full setup I run, browsable file by file.

CLAUDE.md

# Claude Code Setup

Behavior contract and skill orchestration rules for Claude Code. Loaded into every session.

## Project Structure

```
skills/       → Core skills (SKILL.md per directory)
agents/       → Reusable agent personas (code-reviewer, test-engineer, security-auditor)
hooks/        → Session lifecycle hooks
.claude/commands/ → Slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship)
references/   → Supplementary checklists (testing, performance, security, accessibility)
docs/         → Setup guides for different tools
```

## Skills by Phase

**Define:** spec-driven-development
**Plan:** planning-and-task-breakdown
**Build:** incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design
**Verify:** browser-testing-with-devtools, debugging-and-error-recovery
**Review:** code-review-and-quality, code-simplification, security-and-hardening, performance-optimization
**Ship:** git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, shipping-and-launch

## Conventions

- Every skill lives in `skills/<name>/SKILL.md`
- YAML frontmatter with `name` and `description` fields
- Description starts with what the skill does (third person), followed by trigger conditions ("Use when...")
- Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification
- References are in `references/`, not inside skill directories
- Supporting files only created when content exceeds 100 lines

## Commands

- `npm test`: Not applicable (this is a documentation project)
- Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description

## Boundaries

- Always: Follow the skill-anatomy.md format for new skills
- Never: Add skills that are vague advice instead of actionable processes
- Never: Duplicate content between skills: reference other skills instead

# Claude Code Setup Behavior contract and skill orchestration rules for Claude Code. Loaded into every session. ## Project Structure ``` skills/ → Core skills (SKILL.md per directory) agents/ → Reusable agent personas (code-reviewer, test-engineer, security-auditor) hooks/ → Session lifecycle hooks .claude/commands/ → Slash commands (/spec, /plan, /build, /test, /review, /code-simplify, /ship) references/ → Supplementary checklists (testing, performance, security, accessibility) docs/ → Setup guides for different tools ``` ## Skills by Phase **Define:** spec-driven-development **Plan:** planning-and-task-breakdown **Build:** incremental-implementation, test-driven-development, context-engineering, source-driven-development, doubt-driven-development, frontend-ui-engineering, api-and-interface-design **Verify:** browser-testing-with-devtools, debugging-and-error-recovery **Review:** code-review-and-quality, code-simplification, security-and-hardening, performance-optimization **Ship:** git-workflow-and-versioning, ci-cd-and-automation, deprecation-and-migration, documentation-and-adrs, shipping-and-launch ## Conventions - Every skill lives in `skills/<name>/SKILL.md` - YAML frontmatter with `name` and `description` fields - Description starts with what the skill does (third person), followed by trigger conditions ("Use when...") - Every skill has: Overview, When to Use, Process, Common Rationalizations, Red Flags, Verification - References are in `references/`, not inside skill directories - Supporting files only created when content exceeds 100 lines ## Commands - `npm test`: Not applicable (this is a documentation project) - Validate: Check that all SKILL.md files have valid YAML frontmatter with name and description ## Boundaries - Always: Follow the skill-anatomy.md format for new skills - Never: Add skills that are vague advice instead of actionable processes - Never: Duplicate content between skills: reference other skills instead