c4-architecture-docslisted

Use this skill to document the architecture of a big issue / epic / feature with the C4 model (c4model.com) -- producing system context, container, component, and dynamic diagrams as Mermaid .mmd plus a narrative doc. Trigger phrases: 'C4 model', 'architecture diagram', 'system context / container / component diagram', 'document the architecture of this epic', 'draw the containers for this feature'. Don't use it for: rendering an existing .mmd to HTML (use the project's Mermaid viewer/renderer, or the `mmdc` CLI); FigJam whiteboard diagrams (use figma:figma-generate-diagram); a pure decision record with no diagrams (use the ADR template — `.claude/templates/adr-template.md`, falling back to core's `templates/adr-template.md`).
atretyak1985/swarmery · ★ 3 · AI & Automation · score 65

Install: claude install-skill atretyak1985/swarmery

# Purpose Produce house-consistent **C4 architecture documentation** for a big issue: a small set of Mermaid C4 diagrams (`.mmd`) plus a short narrative doc, filed in the task dir and rendered for review. C4 gives "maps of your code" at fixed zoom levels (System Context -> Container -> Component -> Code, plus supplementary types — System Landscape, Dynamic, Deployment) so every diagram is typed, labelled, and self-explanatory instead of "a confused mess of boxes and lines" (c4model.com, Simon Brown). This skill owns the **HOW** — level selection, diagram grammar, boundary/technology-labelling rules, and the file-and-promote workflow. It authors `.mmd` source and narrative; it does **not** render (hand the `.mmd` to the project's Mermaid viewer/renderer) and it does **not** replace an ADR (that is the ADR template). The project's own tiers, repos, and containers are **not** baked into this skill — read them from `.claude/project.json` (`repos`, `apps`, `mainApp`, `device`, `stack`) and the project's `CLAUDE.md`. Ground every box in that real inventory. # When to use this skill - User says "document the architecture", "draw the C4 / system context / container / component diagram", "give me an architecture diagram for this feature/epic". - A big issue (epic, cross-tier feature, incident post-mortem, audit) needs a durable structural picture before or after implementation. - `@architecture-designer` reaches its "design architecture" step and needs the C4 grammar. - You need