plugins/cartograph/skills/architecture-diagram/SKILL.md
Generates a Mermaid architecture diagram showing high-level component relationships. Use when visualizing how plugins or modules fit together.
npx skillsauth add athola/claude-night-market architecture-diagramInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a Mermaid flowchart showing high-level component relationships in a 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.
Transform the structural model into a Mermaid flowchart.
Rules for architecture diagrams:
flowchart TD (top-down) for hierarchical systemsflowchart LR (left-right) for pipeline/flow systems[Rectangle] for modules/packages([Stadium]) for entry points/commands[(Database)] for data stores{Diamond} for decision pointsExample output:
flowchart TD
subgraph sanctum[Sanctum Plugin]
commit[Commit Messages]
pr[PR Preparation]
workspace[Workspace Review]
end
subgraph leyline[Leyline Plugin]
git[Git Platform]
patterns[Error Patterns]
end
commit --> git
pr --> workspace
pr --> git
workspace --> patterns
Call the Mermaid Chart MCP to render:
mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
prompt: "Architecture diagram of [scope]"
mermaidCode: [generated syntax]
diagramType: "flowchart"
clientName: "claude-code"
If rendering fails, fix the Mermaid syntax based on the error message and retry (max 2 retries).
Show the rendered diagram to the user with a brief summary of what it depicts (2-3 sentences).
research
Generate diverse solution candidates with category-spanning ideation methods and rotation. Use when stuck on a design or fighting repetitive LLM output.
tools
--- name: validate-pr description: Use when you need a diff-derived test plan for a PR: reads the diff, groups changes by area, runs targeted verifications, and proves revert-tests are genuine guards, not dead assertions. alwaysApply: false category: validation tags: - pr - validation - test-plan - diff - revert-test - evidence tools: [] usage_patterns: - diff-derived-test-plan - revert-test-quality-check - evidence-capture complexity: intermediate model_hint: standard estimated_tokens: 650
development
Contract for the project decision journal (tradeoffs and lessons-learned logs). Use when recording a decision, tradeoff, or lesson, or building a consumer hook.
development
Ramps implementation ambition a notch only after the prior increment is understood. Use when building a feature you must understand, not just ship.