claude-diagramlisted
Install: claude install-skill erclx/toolkit
# Claude diagram
## Guards
- If no `.claude/ARCHITECTURE.md`, no `.claude/REQUIREMENTS.md`, and no top-level folder structure to scan, stop: `❌ No source signal. Add .claude/ARCHITECTURE.md or run inside a project folder.`
## Step 1: read sources in parallel
Read these from the project root, skipping any that do not exist:
- `.claude/ARCHITECTURE.md`: layered components, key technical decisions
- `.claude/REQUIREMENTS.md`: tech stack, MVP feature list
- `CLAUDE.md`: project type, conventions
- `package.json`, `pyproject.toml`, `Cargo.toml`: language and framework markers
- Top-level folder layout and root config files via `ls`: deploy targets, infrastructure config, component boundaries
Run all reads in parallel. Do not recurse speculatively.
## Step 2: pick which diagrams to emit
Emit a diagram only when its source signal exists. Skip the rest, do not pad the file.
- **Components** (`flowchart TB` with `subgraph` boundaries): always, when any signal exists. Shows the layered structure of the system.
- **Request flow** (`sequenceDiagram`): when prose describes a request lifecycle, an agent loop, or interaction between actors
- **Data pipeline** (`flowchart TB`): when prose mentions retrieval, ranking, queues, ETL, or pipelines
- **Deployment** (`flowchart TB`): when the top-level listing contains deploy or infrastructure config, or `.claude/ARCHITECTURE.md` has a deploy section
Stay inside `flowchart` and `sequenceDiagram`. Do not emit C4, state, ER, or class diagra