Usage
/init-project <PROJECT_SUMMARY_OR_NAME>
Objective
Initialize project AI context using a mixed strategy of "concise at root + detailed at module level":
- Generate/update
CLAUDE.md at repository root (high-level vision, architecture overview, module index, global standards).
- Generate/update local
CLAUDE.md in identified module directories (interfaces, dependencies, entry points, tests, key files, etc.).
- ✨ For improved readability, automatically generate Mermaid structure diagrams in the root
CLAUDE.md and add navigation breadcrumbs to each module CLAUDE.md.
Orchestration Instructions
Step 1: Call the get-current-datetime sub-agent to obtain the current timestamp.
Step 2: Call the init-architect sub-agent once, with input:
project_summary: $ARGUMENTScurrent_timestamp: (timestamp from step 1)
Execution Strategy (Agent adapts automatically, no user parameters needed)
- Stage A: Repository Census (Lightweight)
Quickly count files and directories, identify module roots (package.json, pyproject.toml, go.mod, apps/, packages/, services/*, etc.).
- Stage B: Module Priority Scanning (Medium)
For each module, perform targeted reading and sampling of "entry/interfaces/dependencies/tests/data models/quality tools".
- Stage C: Deep Supplementation (As Needed)
If repository is small or module scale is small, expand reading scope; if large, perform batch supplemental scanning on high-risk/high-value paths.
- Coverage Measurement and Resumability
Output "scanned files / estimated total files, covered module ratio, ignored/skipped reasons" and list "recommended next-step deep-dive sub-paths". When running
/init-project repeatedly, perform incremental updates and breakpoint resumable scanning based on previous index.
Security and Boundaries
- Only read/write documentation and indexes, do not modify source code.
- Ignore common generated artifacts and binary large files by default.
- Print "summary" in main dialog, write full content to repository.
Output Requirements
- Print "Initialization Result Summary" in main dialog, including:
- Whether root-level
CLAUDE.md was created/updated, major section overview.
- Number of identified modules and their path list.
- Generation/update status of each module's
CLAUDE.md.
- ✨ Explicitly mention "Generated Mermaid structure diagram" and "Added navigation breadcrumbs for N modules".
- Coverage and major gaps.
- If not fully read: explain "why stopped here" and list recommended next steps (e.g., "suggest priority supplemental scanning: packages/auth/src/controllers").
1---2name: init-project3description: Initialize project AI context, generate/update root-level and module-level CLAUDE.md indexes4---5
6## Usage
7
8`/init-project <PROJECT_SUMMARY_OR_NAME>`
9
10## Objective
11
12Initialize project AI context using a mixed strategy of "concise at root + detailed at module level":
13
14- Generate/update `CLAUDE.md` at repository root (high-level vision, architecture overview, module index, global standards).
15- Generate/update local `CLAUDE.md` in identified module directories (interfaces, dependencies, entry points, tests, key files, etc.).
16- ✨ **For improved readability, automatically generate Mermaid structure diagrams in the root `CLAUDE.md` and add navigation breadcrumbs to each module `CLAUDE.md`**.
17
18## Orchestration Instructions
19
20**Step 1**: Call the `get-current-datetime` sub-agent to obtain the current timestamp.
21
22**Step 2**: Call the `init-architect` sub-agent once, with input:
23
24- `project_summary`: $ARGUMENTS
25- `current_timestamp`: (timestamp from step 1)
26
27## Execution Strategy (Agent adapts automatically, no user parameters needed)
28
29- **Stage A: Repository Census (Lightweight)**
30 Quickly count files and directories, identify module roots (package.json, pyproject.toml, go.mod, apps/_, packages/_, services/\*, etc.).
31- **Stage B: Module Priority Scanning (Medium)**
32 For each module, perform targeted reading and sampling of "entry/interfaces/dependencies/tests/data models/quality tools".
33- **Stage C: Deep Supplementation (As Needed)**
34 If repository is small or module scale is small, expand reading scope; if large, perform batch supplemental scanning on high-risk/high-value paths.
35- **Coverage Measurement and Resumability**
36 Output "scanned files / estimated total files, covered module ratio, ignored/skipped reasons" and list "recommended next-step deep-dive sub-paths". When running `/init-project` repeatedly, perform **incremental updates** and **breakpoint resumable scanning** based on previous index.
37
38## Security and Boundaries
39
40- Only read/write documentation and indexes, do not modify source code.
41- Ignore common generated artifacts and binary large files by default.
42- Print "summary" in main dialog, write full content to repository.
43
44## Output Requirements
45
46- Print "Initialization Result Summary" in main dialog, including:
47 - Whether root-level `CLAUDE.md` was created/updated, major section overview.
48 - Number of identified modules and their path list.
49 - Generation/update status of each module's `CLAUDE.md`.
50 - ✨ **Explicitly mention "Generated Mermaid structure diagram" and "Added navigation breadcrumbs for N modules"**.
51 - Coverage and major gaps.
52 - If not fully read: explain "why stopped here" and list **recommended next steps** (e.g., "suggest priority supplemental scanning: packages/auth/src/controllers").
UfoMiao