claudecode-boilerplate/CLAUDE.md

Project Memory

Technology Stack

• Development environment: devcontainer
• Node.js v24.11.0
• TypeScript 5.x
• Package manager: npm

Basic Principles of Spec-Driven Development

Basic Flow

1. Document creation: Define "what to build" in persistent documents (docs/)
2. Work planning: Plan "what to do this time" in steering files (.steering/)
3. Implementation: Implement according to tasklist.md and update progress as you go
4. Verification: Testing and operation checks
5. Update: Reconcile all docs/ documents with the implemented feature (see /add-feature Step 8)

Important Rules

When Creating Documents

Create one file at a time, and always obtain the user's approval before moving on to the next.

When waiting for approval, communicate clearly:

"The creation of [document name] is complete. Please review the content.
Once you approve, I will proceed to the next document."

Checks Before Implementation

Before starting a new implementation, always check the following:

1. Read CLAUDE.md
2. Read the related persistent documents (docs/)
3. Search for existing similar implementations with Grep
4. Understand existing patterns before starting implementation

Steering File Management

Create .steering/[YYYYMMDD]-[task-name]/ for each piece of work:

• requirements.md: The requirements for this work
• design.md: The implementation approach
• tasklist.md: A concrete task list

Naming convention: 20250115-add-user-profile format

Steering File Management

Use the steering skill when planning work, implementing, and verifying.

• When planning work: Mode 1 (creating steering files) via Skill('steering')
• When implementing: Mode 2 (implementation and tasklist.md update management) via Skill('steering')
• When verifying: Mode 3 (retrospective) via Skill('steering')

Detailed procedures and update-management rules are defined within the steering skill.

Directory Structure

Persistent Documents (docs/)

Define "what to build" and "how to build it" for the entire application:

Drafts and Ideas (docs/ideas/)

• Outputs of brainstorming and ideation
• Technical research notes
• Free-form (minimal structure)
• Automatically loaded when /setup-project is run

Official Documents

• product-requirements.md - Product requirements document
• functional-design.md - Functional design document
• architecture.md - Technical specification
• repository-structure.md - Repository structure definition document
• development-guidelines.md - Development guidelines
• glossary.md - Ubiquitous language definitions

Design Documents (docs/design/)

• design-brief.md - UI/UX direction
• design-tokens.json - Styling tokens (source of values)
• ui-blueprint.json - UI structure (source of truth for UI generation)
• platform-mapping.md - How the design maps to Web / Flutter / WinUI 3
• screens/*.svg - Visual wireframes (references only)
• Created by /define-design, updated by /update-design, consumed by /generate-app and /add-feature

Work-Unit Documents (.steering/)

Define "what to do this time" for a specific development task:

• requirements.md: The requirements for this work
• design.md: The design of the changes
• tasklist.md: The task list

Claude Code Configuration (.claude/)

• .claude/agents/ - Subagent definitions (doc-reviewer, implementation-validator)
• .claude/commands/ - Slash commands (setup-project, define-design, generate-app, update-design, add-feature, review-docs)
• .claude/skills/ - Task-specific skills (prd-writing, functional-design, architecture-design, repository-structure, development-guidelines, glossary-creation, ui-design, design-tokens, platform-ui-generation, steering)

Development Process

Initial Setup

1. Use this template
2. Create persistent documents with /setup-project (automatically creating six)
3. Define the UI/UX design with /define-design (creates docs/design/)
4. Review and refine the UI/UX with /update-design (or re-run /define-design) until approved — before generating code
5. Generate the initial app with /generate-app web | flutter | winui3
6. Implement features with /add-feature [feature]

Day-to-Day Usage

Basically, just make requests through normal conversation:

# Editing documents
> Please add a new feature to the PRD
> Review the performance requirements in architecture.md
> Add a new domain term to glossary.md

# Adding features (use commands for the standard flow)
> /add-feature edit user profile

# Design phase
> /define-design
> /generate-app web
> /update-design add a profile screen

# Detailed review (when a detailed report is needed)
> /review-docs docs/product-requirements.md

Key point: You do not need to be conscious of the details of spec-driven development. Claude Code will determine and load the appropriate skill.

Principles of Document Management

Persistent Documents (docs/)

• Describe the fundamental design
• The "north star" for the entire project
• Kept in sync with every feature: at the end of /add-feature (Step 8), all six documents are reconciled with the implemented feature (product-requirements, functional-design, architecture, repository-structure, development-guidelines, glossary)

Work-Unit Documents (.steering/)

• Specialized for a specific task
• Created anew for each piece of work
• Retained as history