manastalukdar/ai-devstudio/architecture-diagram

Claude Code and agent skill by manastalukdar/ai-devstudio

Trust tier 1
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Generate architecture diagrams in Mermaid, PlantUML, or diagrams.net formats

Install

npx vskill@latest install manastalukdar/ai-devstudio/architecture-diagram

SKILL.md

Architecture Diagram Generator

I'll analyze your codebase and generate visual architecture diagrams showing component relationships, data flow, and system structure.

Arguments: $ARGUMENTS - diagram type or format (e.g., "mermaid", "plantuml", "component", "data-flow")

Strategic Analysis Process

<think> Effective architecture diagrams require understanding:

  1. Project Structure Analysis
  • What's the application architecture? (monolith, microservices, serverless)
  • What layers exist? (frontend, backend, database, services)
  • How do components communicate?
  • What are the major modules and their responsibilities?
  • Are there clear architectural patterns? (MVC, MVVM, Clean Architecture)
  1. Diagram Type Selection
  • Component diagram: Show major components and relationships
  • Sequence diagram: Show interaction flows
  • Data flow diagram: Show how data moves through system
  • Deployment diagram: Show infrastructure and deployment
  • Class diagram: Show object-oriented structure
  • Entity-relationship: Show database schema
  1. Format Decision
  • Mermaid: Simple, version-controllable, GitHub/GitLab rendering
  • PlantUML: More features, complex diagrams, requires rendering
  • Diagrams.net (Draw.io): Visual editing, XML format
  • ASCII art: Terminal-friendly, simple visualizations
  1. Detail Level
  • High-level overview: Major components only
  • Medium detail: Components + key interactions
  • Detailed: All modules, functions, data flows
  • Focus on what's most valuable for documentation

</think>

Phase 1: Architecture Discovery

MANDATORY FIRST STEPS:

  1. Analyze project structure and file organization
  2. Identify architectural patterns from code
  3. Map component dependencies
  4. Detect technology stack and frameworks

Let me analyze your project architecture:

bash
# Analyze project structure
echo "=== Architecture Analysis ==="
# Detect project type
if [ -d "src/components" ] || [ -d "components" ]; then
echo "Frontend components detected"
fi
if [ -d "src/api" ] || [ -d "api" ] || [ -d "routes" ]; then
echo "API/Backend layer detected"
fi
if [ -d "src/models" ] || [ -d "models" ]; then
echo "Data models detected"
fi
if [ -d "src/services" ] || [ -d "services" ]; then
echo "Service layer detected"
fi
# Count major components
echo ""
echo "Component counts:"
find src -type f -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" 2>/dev/null | wc -l | xargs echo "Files:"
find src -type d -maxdepth 2 2>/dev/null | wc -l | xargs echo "Directories:"
# Identify framework
if grep -q "\"next\"" package.json 2>/dev/null; then
echo "Framework: Next.js"
elif grep -q "\"react\"" package.json 2>/dev/null; then
echo "Framework: React"
elif grep -q "\"vue\"" package.json 2>/dev/null; then
echo "Framework: Vue"
elif grep -q "\"express\"" package.json 2>/dev/null; then
echo "Framework: Express (Node.js)"
fi

Phase 2: Component Relationship Mapping

I'll map relationships between components:

Analysis Methods:

  • Import/export analysis (module dependencies)
  • API endpoint mapping (request/response flows)
  • Database relationship detection (foreign keys, relations)
  • Event system mapping (event emitters/listeners)
  • Service dependencies (dependency injection patterns)

Using Native Tools:

  • Grep to find import statements and dependencies
  • Glob to identify component files by pattern
  • Read key architectural files (routers, services, models)
  • Pattern detection for architectural styles

I'll analyze:

  • Frontend component hierarchy
  • Backend route handlers and middleware
  • Service layer dependencies
  • Database entity relationships
  • External API integrations

Phase 3: Diagram Generation

Based on analysis, I'll generate appropriate diagrams:

Mermaid Diagrams (Default)

Component Diagram:

mermaid
graph TB
subgraph Frontend
UI[User Interface]
Components[React Components]
Store[State Management]
end
subgraph Backend
API[API Layer]
Services[Business Services]
Models[Data Models]
end
subgraph Infrastructure
DB[(Database)]
Cache[(Redis Cache)]
Queue[Message Queue]
end
UI --> Components
Components --> Store
Components --> API
API --> Services
Services --> Models
Models --> DB
Services --> Cache
Services --> Queue

Data Flow Diagram:

mermaid
flowchart LR
User((User)) --> UI[User Interface]
UI --> Auth{Authentication}
Auth -->|Valid| API[API Gateway]
Auth -->|Invalid| Login[Login Page]
API --> Service[Business Logic]
Service --> DB[(Database)]
DB --> Service
Service --> API
API --> UI
UI --> User

Sequence Diagram:

mermaid
sequenceDiagram
participant User
participant Frontend
participant API
participant Service
participant DB
User->>Frontend: Click Action
Frontend->>API: HTTP Request
API->>Service: Process Request
Service->>DB: Query Data
DB-->>Service: Return Results
Service-->>API: Format Response
API-->>Frontend: JSON Response
Frontend-->>User: Update UI

System Architecture:

mermaid
graph TB
subgraph Client Layer
Web[Web App]
Mobile[Mobile App]
end
subgraph API Gateway
Gateway[API Gateway]
Auth[Auth Service]
end
subgraph Services
UserService[User Service]
ProductService[Product Service]
OrderService[Order Service]
end
subgraph Data Layer
PostgreSQL[(PostgreSQL)]
Redis[(Redis)]
S3[S3 Storage]
end
Web --> Gateway
Mobile --> Gateway
Gateway --> Auth
Auth --> Gateway
Gateway --> UserService
Gateway --> ProductService
Gateway --> OrderService
UserService --> PostgreSQL
ProductService --> PostgreSQL
OrderService --> PostgreSQL
ProductService --> Redis
OrderService --> S3
PlantUML Diagrams

Class Diagram:

plantuml
@startuml
class User {
+id: string
+email: string
+name: string
+authenticate()
+updateProfile()
}
class Product {
+id: string
+name: string
+price: number
+getDetails()
}
class Order {
+id: string
+userId: string
+items: Product[]
+total: number
+createOrder()
+processPayment()
}
User "1" -- "*" Order
Order "*" -- "*" Product
@enduml

Component Diagram:

plantuml
@startuml
package "Frontend" {
[React Components]
[Redux Store]
[API Client]
}
package "Backend" {
[Express Server]
[Auth Middleware]
[Business Logic]
}
package "Data" {
database "PostgreSQL"
database "Redis"
}
[React Components] --> [Redux Store]
[React Components] --> [API Client]
[API Client] --> [Express Server]
[Express Server] --> [Auth Middleware]
[Auth Middleware] --> [Business Logic]
[Business Logic] --> PostgreSQL
[Business Logic] --> Redis
@enduml
Deployment Diagram

Infrastructure Visualization:

mermaid
graph TB
subgraph Cloud Provider
subgraph Frontend
CDN[CDN / CloudFront]
Static[Static Hosting]
end
subgraph Application
LB[Load Balancer]
App1[App Server 1]
App2[App Server 2]
App3[App Server 3]
end
subgraph Data
Primary[(Primary DB)]
Replica[(Read Replica)]
Cache[(Redis Cluster)]
end
subgraph Queue
MQ[Message Queue]
Worker1[Worker 1]
Worker2[Worker 2]
end
end
Users((Users)) --> CDN
CDN --> Static
Users --> LB
LB --> App1
LB --> App2
LB --> App3
App1 --> Primary
App2 --> Primary
App3 --> Primary
App1 --> Replica
App2 --> Replica
App3 --> Replica
App1 --> Cache
App2 --> Cache
App3 --> Cache
App1 --> MQ
MQ --> Worker1
MQ --> Worker2
Worker1 --> Primary
Worker2 --> Primary

Phase 4: Diagram Output

I'll create diagram files in your project:

File Creation:

  • docs/architecture/components.mmd - Component diagram
  • docs/architecture/data-flow.mmd - Data flow diagram
  • docs/architecture/deployment.mmd - Deployment diagram
  • docs/architecture/sequence.mmd - Sequence diagrams
  • docs/architecture/README.md - Documentation with rendered diagrams

Markdown Integration:

markdown
# System Architecture
## Component Diagram

[diagram content]

## Data Flow

[diagram content]

This automatically renders on GitHub, GitLab, and many documentation platforms.

Token Optimization

Expected range: 1,400–4,200 tokens (initial), 500 tokens (cache hit)

Caching: Caches architecture analysis in .claude/cache/architecture/ for 7 days. Invalidated when source structure changes.

Early exit: Returns cached diagram immediately if project structure has not changed.

Patterns used: Grep-before-Read, early exit, caching, Bash for system queries

Security

  • Security scanPassedPattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
7-day trend score
8

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/manastalukdar/ai-devstudio/architecture-diagram/badge)](https://verified-skill.com/skills/manastalukdar/ai-devstudio/architecture-diagram)

Something wrong with this skill or its page? Tell us.