Create concise Mermaid architecture diagrams from a chapter, system, component, dependency flow, or supplied description. The skill checks the diagram syntax before presenting the diagram and a brief explanation of its key flow.
Create concise, syntax-verified Mermaid architecture diagrams. Use when the user asks to diagram a chapter topic, system, component, dependency flow, or supplied description in Mermaid.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Draw a mermaid architecture diagram in markdown for: $ARGUMENTS
svc[api-gateway]. Use [(...)] for datastores, [[...]]-style queues only if the chapter does. Humans (user, operator) are triangles: user@{ shape: tri, label: "user" }.cron["nightly compaction job (spawned, exits when done)"]). Never draw a manual procedure as a peer of running infrastructure; give it its own subgraph titled as manual.A --> B means A calls/reads/writes B — never the reverse. Label an edge (A -->|gRPC| B) only when the relationship isn't obvious.flowchart TB; LR only if much wider than deep. subgraph only for real boundaries (region, cluster, trust zone, sync vs. async path).en/<file>.md) — don't diagram from guesswork. Keep names consistent with the chapter's prose.Syntax gotchas: quote labels containing (, ), [, { (a["Queue (SQS)"]); never name a node bare end or graph; quote subgraph titles with spaces.
.mmd file under .agents/tmp/ (gitignored).npx -y @mermaid-js/mermaid-cli@11.16.0 -i <file>.mmd -o <file>.svg; exit 0 means valid. The version is pinned deliberately (supply chain) — bump consciously.A single ```mermaid fenced block plus a short explanation of the key flow. If asked to put it in a file, insert the verified block there.
Book caveat: the GitBook build (gitbook-cli, Node 10) does not render Mermaid fences by default. For published chapters, either render the verified .mmd to an image under images/ (-o images/<name>.svg, referenced as ../images/<name>.svg) or confirm a Mermaid plugin is enabled in book.json before leaving a raw fence in a chapter. Mirror the diagram in both en/ and zh-CN/ (translate labels only).
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Answer questions about a book, its chapters, or system design by consulting relevant material without changing files. For repository questions, ground the response in the source and cite file paths and lines; use web search for general topics when freshness matters.
Work through a `.pm` workstream backlog one actionable item at a time. Triage pending milestones, tasks, and inbox notes, then implement and ship them, close items already satisfied, block work with an unblock condition, or remove invalid items until no actionable work remains.
Manage and inspect a book project's public work board: organize workstreams, notes, milestones, and tasks, and update their status as work changes. Use it to materialize proposals, track blockers, or check current board state.
Break down a book roadmap topic into prioritized milestone and task proposals, considering reader impact, scope, dependencies, and effort. The skill outputs text for a separate board workflow to apply; it does not write board files.
Prepare pending changes on the tracked working branch for publishing: check the branch and repository state, rebase on the latest origin changes, commit selected files, and push. It is intended for an explicit ship or publish request.