AutoSkillit: Skill for Claude Code

Make-Arch-Diag: Architecture Diagram Generation

Creates comprehensive architecture diagrams for selected components or systems using mermaid syntax.

When to Use

• Documenting a new feature or component
• Updating architecture documentation after changes
• Onboarding new team members
• Explaining complex system interactions
• Before making significant architectural changes

Critical Constraints

ALWAYS:

• Ask user which component/system to diagram
• Use the /mermaid skill for diagram creation
• Include multiple views (data flow, component structure, sequence diagrams)
• Save diagrams to temp/make-arch-diag/{component-name}/
• Use consistent color coding across all diagrams

NEVER:

• Create diagrams without understanding the code
• Skip reading the actual implementation
• Use generic placeholder names
• Create diagrams that contradict the code

---

Workflow

Step 1: Component Selection

Ask the user which area they want diagrammed:

Which component or system would you like to diagram?

Examples:
- Authentication system
- Database layer
- API endpoints
- Message queue processing
- State management
- Specific feature (e.g., "user registration flow")

Please specify the component/system:

Step 2: Scope Definition

Based on user input, determine:

• Boundaries: What's in scope vs out of scope
• Level of Detail: High-level architecture vs detailed implementation
• Audience: Developers, architects, stakeholders

Step 3: Code Exploration

Investigate the codebase:

• Find entry points (main, CLI, API routes)
• Trace execution flows
• Identify components and their relationships
• Map data flows
• Document external dependencies

Step 4: Diagram Types Selection

Choose appropriate diagram types:

Component Diagram (Always include)

• Shows major components and their relationships
• Good for: Understanding system structure

Data Flow Diagram (Include if data transformation is central)

• Shows how data moves through the system
• Good for: Understanding pipelines, ETL, processing