diagram-excalidraw
Generate Excalidraw architecture diagrams from codebase analysis. Use when user says "create an architecture diagram", "visualize the system design", "generate an excalidraw diagram", "draw the component structure", "create a visual representation of the codebase", or "diagram the data flow".
What this skill does
# Excalidraw Diagram Generator Generate valid `.excalidraw` JSON files representing system architecture from codebase analysis. ## Quick Start Works without existing diagrams, Terraform, or specific file types. Analyzes any codebase structure. If the codebase has more than ~30 distinct components, limit scope to top-level packages or services only to keep the diagram readable. ## Critical Implementation Rules **Four non-negotiable constraints:** 1. **No Diamond Shapes**: Diamond arrow connections are broken in raw Excalidraw JSON. Use styled rectangles instead: - Orchestrators: coral background with thick stroke - Decision points: orange background with dashed stroke 2. **Label Architecture**: The `label` property does NOT work in raw JSON. Every labeled element requires: - A shape with `boundElements` referencing the text element - A separate text element with `containerId` pointing to the shape 3. **Arrow Formatting**: Multi-point arrows need: - `"elbowed": true` - `"roundness": null` - `"roughness": 0` 4. **Edge Positioning**: Arrows must start/end at shape edges, not centers: - Top: `(x + width/2, y)` - Bottom: `(x + width/2, y + height)` - Left: `(x, y + height/2)` - Right: `(x + width, y + height/2)` ## Generation Workflow 1. **Analyze codebase structure** - Identify components, services, and relationships 2. **Plan layout grid** - Determine rows, columns, and spacing 3. **Generate shape elements** - Create rectangles, ellipses, text labels; derive element IDs from component names (e.g., `api-server`, `api-server-text`) and verify all IDs are unique 4. **Add connection arrows** - Connect components with proper edge positioning 5. **Apply grouping** - Group related elements (namespaces, services, etc.) 6. **Validate and write output** - Check all constraints before writing file ## Input Parsing Extract from user's request: - `scope`: What part of codebase to diagram (full, specific module, etc.) - `type`: Type of diagram (architecture, data flow, deployment, etc.) - `depth`: Level of detail (high-level overview vs detailed) - `output`: Output file path (defaults to `./architecture.excalidraw`) ## Output Format Generate a valid `.excalidraw` JSON file with: - Proper file structure (type, version, elements, appState) - All shapes with unique IDs - Proper text bindings for labels - Correct arrow connections at shape edges - Logical groupings with dashed rectangles ## Validation Checklist Before writing output, verify: - [ ] No duplicate element IDs - [ ] All labels have proper shape-text bindings - [ ] No diamond shapes used - [ ] All arrows positioned at shape edges - [ ] JSON is valid and properly formatted ## Reference Documentation For detailed implementation guidance, see: - [JSON Format Reference](references/json-format.md) - Complete element structure - [Arrow Routing Guide](references/arrows.md) - Arrow positioning and patterns - [Color Palettes](references/colors.md) - Component type color schemes - [Examples](references/examples.md) - Layout patterns and templates - [Validation Rules](references/validation.md) - Pre-output verification
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.