excalidash-repo-to-system-design

Converts structured repository analysis into framed, flow-routed system-design diagrams in Excalidraw.

2|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-repo-to-system-design-gabedsam01
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: excalidash-repo-to-system-design
Source: https://github.com/gabedsam01/excalidash-v2/tree/main/skills/excalidash/excalidash-repo-to-system-design
Command: npx skills add https://github.com/gabedsam01/excalidash-v2 --skill excalidash-repo-to-system-design-gabedsam01

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a codebase analysis into an accurate as-built architecture diagram is slow and error-prone: nodes get invented, flows lose their routing, and secrets from .env files leak into exported drawings. This Skill takes a structured repository analysis and produces a framed, validated system-design diagram via the ExcaliDash MCP server. ## Core Features & Use Cases - Zone-framed generation: Builds one frame per zone (Client, Edge, Services, Async, Data, External, Cross-cutting) from the rich intermediate model using create_from_repo_analysis, with request flows rendered solid and event flows dashed. - Mandatory quality loop: Runs lint, score, repair, polish, and validate_architecture until the drawing scores at least 95 with zero hard blockers, with rollback to saved versions on regression. - Secret redaction: Redacts database connection strings, IdP secrets, API keys, and webhook secrets before any tool call and re-scans the export. - Use Case: After running an analyzer over a monorepo, hand the resulting JSON (actors, services, queues, databases, integrations, flows) to this Skill to get a shareable, exportable system-design diagram with a zone legend. ## Quick Start Draw this repository analysis as a framed system-design diagram with routed request and event flows and a zone legend.

Frequently Asked Questions about excalidash-repo-to-system-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a repository analysis into a system design diagram?▼

Pass the structured analysis model (actors, services, queues, databases, integrations, flows) to create_from_repo_analysis with the architecture preset. It builds one frame per zone, routes one labeled arrow per flow step, and emits a zone legend.

What input format does the repo-to-system-design skill expect?▼

It expects a structured intermediate model with typed sections: actors, apps, gateways, services, workers, queues, databases, integrations, auth, observability, risks, and flows. Prose paragraphs are not accepted; use a prompt-based fallback or run an analysis first.

When should I not use repo analysis for architecture diagrams?▼

Avoid it when you only have prose, when you need a single canonical view like a C4 container diagram or sequence diagram, or when there is no repository analysis to ground the nodes. Use a dedicated pattern skill or prompt-based generation instead.

How are database credentials and API keys handled in generated diagrams?▼

All connection strings, IdP secrets, integration API keys, JWT signing keys, and webhook secrets must be redacted in the model before any tool call, using placeholders like [REDACTED_DATABASE_URL]. The exported drawing is re-scanned for leaks.

Why does my architecture diagram fail validation?▼

Common causes are nodes outside their zone frames, integrations placed inside a service zone, flow labels intersecting arrows, or dangling flow endpoints. Run lint_drawing, repair_drawing, and validate_architecture in a loop until the score reaches 95 with no hard blockers.