Generates a Mermaid architecture diagram showing high-level component relationships. Use when visualizing how plugins or modules fit together.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Architecture Diagram
Generate a Mermaid flowchart showing high-level component
relationships in a codebase.
## When To Use
- Visualizing how plugins/modules relate to each other
- Onboarding to understand system structure
- Documenting architecture for PR reviews
- Answering "how does this system fit together?"
## When NOT To Use
- Import-level coupling (use `cartograph:dependency-graph`)
- Runtime call paths (use `cartograph:call-chain`)
## Workflow
### Step 1: Explore the Codebase
Dispatch the codebase explorer agent to analyze the scope:
```
Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on packages, modules, and their relationships
for an architecture diagram.
```
If no scope is provided, use the project root.
### Step 2: Generate Mermaid Syntax
Transform the structural model into a Mermaid flowchart.
**Rules for architecture diagrams**:
- Use `flowchart TD` (top-down) for hierarchical systems
- Use `flowchart LR` (left-right) for pipeline/flow systems
- Group related modules into subgraphs by package
- Use descriptive edge labels for relationships
- Limit to 15-20 nodes maximum (aggregate small modules)
…
The line at the top of this page pins the label git:20260713.f98719b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_34fjrv7kpeqxbjww
GET https://markdownregistry.com/api/v1/resolve?ref=athola/claude-night-market/architecture-diagram
GET https://markdownregistry.com/api/v1/blob/cf0e917320b082f32f7069142c18cc0fd59f165ba4c011e39c798d9cd3ab8923
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
athola/claude-night-market · .claude/skills/claude-code-plugin-reference/SKILL.md · Explain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not…
athola/claude-night-market · .claude/skills/night-market-architecture-contract/SKILL.md · States load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating…
athola/claude-night-market · .claude/skills/night-market-build-and-env/SKILL.md · Rebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for…
athola/claude-night-market · .claude/skills/night-market-change-control/SKILL.md · Classify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage…
athola/claude-night-market · .claude/skills/night-market-collective-memory/SKILL.md · Search and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for…
athola/claude-night-market · .claude/skills/night-market-completion-integrity-campaign/SKILL.md · Bind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA…
athola/claude-night-market · .claude/skills/night-market-config-catalog/SKILL.md · Catalog every config axis, its defaults and guards. Use when adding or auditing configuration. Do not use for running…
athola/claude-night-market · .claude/skills/night-market-debugging-playbook/SKILL.md · Triage night-market failures by symptom (hooks, CI, tests). Use when a check fails unexpectedly. Do not use for routine…
athola/claude-night-market · .claude/skills/night-market-diagnostics-toolkit/SKILL.md · Run and interpret repo diagnostic scripts (ratchets, validators, token stats). Use when measuring health. Do not use to…
athola/claude-night-market · .claude/skills/night-market-docs-and-writing/SKILL.md · Maintain docs of record, ADRs, changelog, and house style. Use when writing repo docs. Do not use for release steps…
athola/claude-night-market · .claude/skills/night-market-failure-archaeology/SKILL.md · Chronicles settled battles, reverts, and dead ends. Use when a fix echoes a past failure. Do not use for live triage…
athola/claude-night-market · .claude/skills/night-market-model-and-harness-updates/SKILL.md · Sweep plugins, skills, agents, commands, and hooks after a model release or Claude Code version bump. Use when upstream…
mohitagw15856/pm-claude-skills · exports/openclaw/architecture-diagram/SKILL.md · Diagram a system or technical architecture — services, data stores, and how they connect. Use when asked to draw an…
taracodlabs/aiden · workspace-templates/skills/architecture-diagram/SKILL.md · Generate dark-themed system architecture and component diagrams as HTML/SVG for rendering in the browser
cowork-os/cowork-os · resources/skills/architecture-diagram/SKILL.md · Generate polished dark-themed architecture diagrams as standalone HTML files with inline SVG, semantic system grouping…
konraddzbik/architecture-diagram-skill · skills/architecture-diagram/SKILL.md · Build interactive, click-through architecture diagrams for software systems — a self-contained single HTML file with…
outlinedriven/outline-driven-development · .devin/skills/architecture-diagram/SKILL.md · Use when the user asks to visualize an architecture as a self-contained HTML artifact, or compare two architecture…
