documentation-help git:20261023.652c011A

Immutable. This exact content never changes and is served at /api/v1/blob/f2e1cb81c5806251.

---
name: "documentation-help"
description: "Overview of documentation and diagram commands"
---
<!-- GENERATED by claude-power-pack - scripts/codex-skill-sync.py; edit .claude/commands/documentation/help.md instead -->

## Codex harness adaptations

Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:

- MCP tools: use the MCP servers configured in `~/.codex/config.toml`, or fall back to the referenced repo scripts and CLI entry points.
- Helper scripts are bundled under `scripts/` in this skill directory (byte-identical copies from the claude-power-pack checkout). Commands run them as `"${CPP_SKILL_DIR:-/dev/null}"/scripts/<name>`: `CPP_SKILL_DIR` is the absolute directory containing THIS SKILL.md - the location the skills catalog gives, with any alias such as `r0` expanded. A shell resolves a bare `scripts/<name>` against your working directory (the target project), never this skill, so substitute that directory, or set it in the same command (`CPP_SKILL_DIR=/abs/skill/dir; ...`) - each command is a fresh shell. "Not a directory" on `/dev/null/scripts/<name>` (exit 126, or 127 in some shells) means `CPP_SKILL_DIR` is unset: set it and re-run; never run the target project's own `scripts/<name>` in its place. Read every "exit 127" fallback in this skill as "exit 127, or 126 Not a directory": set the variable and re-run before falling back. A helper whose verdict gates a step and that prints no verdict line after the whole fallback chain did not run - for the finish gate, no `FLOW_FINISH_GATE:` verdict line: STOP, never read it as skipped, never commit on it (issue #1547). A bare `scripts/<name>` inside a command is a CPP-checkout operation that the text says so about; in prose, `scripts/<name>` NAMES the bundled helper. Some helpers expect sibling repo resources, so prefer a full checkout when one is available.

# Documentation & Diagram Commands

Generate architecture documentation and professional presentations.

## Commands

| Command | Purpose |
|---------|---------|
| `/documentation-c4` | Generate C4 architecture diagrams (all 4 levels) |
| `/documentation-pptx` | Create PowerPoint presentations with optional diagrams |
| `/documentation-help` | This help overview |

## PowerPoint Generation

PowerPoint/PPTX generation is provided by the native Anthropic `pptx` skill (not an MCP server). Install it into a project with:

```bash
npx skills add anthropics/skills@pptx
```

`/documentation-pptx` drives the skill to build slide decks.

## C4 Diagram Rendering

`/documentation-c4` renders C4 diagrams as GitHub-renderable Mermaid via a zero-dependency Python engine (`scripts/c4-mermaid.py`, issue #411). It analyzes the project, builds a C4 model (`docs/architecture/c4-model.json`), then emits L1-L3 as Mermaid `flowchart` (with `subgraph` boundaries and C4 `classDef` colors) and L4 as `classDiagram`. Output is one `.mmd` per level plus an `index.md` that renders inline on GitHub, and a `c4-manifest.json`. The engine enforces an edge-validity QA gate (every edge/relation endpoint must be a defined node) and flags dense diagrams for splitting.

### C4 Node Types

| Type | C4 Concept | Color |
|------|-----------|-------|
| `person` | Actor / User | Dark blue (pill shape) |
| `system` | External System | Grey |
| `system-focus` | System of Interest | Blue |
| `container` | Container (app, DB, service) | Green |
| `component` | Component within container | Purple |
| `code` | Class / module / interface | Amber |

### Makefile Integration

Add an `update_docs` target to your Makefile to run C4 diagram generation and doc review as part of `/flow-auto` and `/flow-finish`.

### Related

- `/cpp-load-mcp-docs` - Load all MCP server documentation
- Upstream `@playwright/mcp` - Browser automation for screenshots