← ClaudeAtlas

architecture-diagramlisted

Turns one design document (a design-doc.md, for example .designs/NNN/design-doc.md) into architecture diagrams only: a C4 system context and container view, plus component, sequence, deployment and security data-flow views when the document states that content. Every element and relationship cites a line of the document, and every name, summary, technology, data item, flow message and assertion is a verbatim quote, checked by bundled gates; relationship verbs are short phrasings of a cited statement. Writes model.json, Mermaid files, Miro-paste Mermaid and one interactive index.html into an architecture-diagrams folder beside the document. Use when asked to diagram, visualize, draw, map or picture a design doc, to show a CTO or reviewer how a proposed design fits together, or to put a design on a Miro board, even if the request never says diagram, C4 or Mermaid. Not for documenting the current codebase from code (that is architecture-docs); never writes prose and never edits the design document.
stempeck/agentfactory · ★ 3 · AI & Automation · score 72
Install: claude install-skill stempeck/agentfactory
# Architecture diagrams from a design doc Input: `$ARGUMENTS` — a design-doc.md path, or a directory holding one. Empty means discover. ## Hard rules 1. **Diagrams only.** Output is `model.json`, Mermaid files and `index.html`. Never write a `.md` file, a report, or an ADR; never edit the design doc. 2. **The design doc is the only source.** Every element, relationship, boundary, technology, change marker and assertion comes from a verbatim, line-cited quote in it; relationship verbs restate a cited sentence in at most six words, using the doc's own words where it has them. When the doc is silent, the model is silent (`null`, `unstated`, a skipped view). 3. **Never invent to fill a view.** A view without stated facts is skipped or marked not-produced with its reason. A placeholder actor, a guessed technology or a descriptive cluster name is a defect. 4. **Scripts render; you never hand-write Mermaid or HTML.** Every fix goes into `model.json`, then render again. Generated files are never edited by hand. 5. **Gates are not optional.** Run every gate on every doc, small or large. Each gate allows at most 3 repair rounds after its first run, then HALT with the gate output quoted verbatim. Passing gates is necessary, not sufficient: read the generated `views/*.mmd` against the doc, and if they misstate it, fix `model.json` and run P3–P5 again (this uses the same per-gate budget). 6. **Never ask the operator a question.** Ambiguity becomes an `open` item or a recorded skip. 7.