From ultraship
Auto-generates Mermaid diagrams mapping codebase architecture: system overview, API routes, database schema, data flow. Analyzes dependencies, concerns, and saves to docs/architecture/.
npx claudepluginhub houseofmvps/ultraship --plugin ultrashipThis skill is limited to using the following tools:
Auto-generates and maintains architecture diagrams from your actual code. Always up-to-date.
Automatically analyzes codebases to generate zero-config architecture diagrams by detecting project type, tech stack, and structure. For repo overviews without custom specs.
Maps system architecture by reading codebase, identifying services and connections, and outputting C4-level Mermaid diagrams with descriptions. Use for architecture overviews or system diagrams.
Scans codebases to auto-generate Mermaid diagrams like ER for DB schemas/models, sequence for API routes, architecture for services, and state diagrams from file structure.
Share bugs, ideas, or general feedback.
Auto-generates and maintains architecture diagrams from your actual code. Always up-to-date.
node ${CLAUDE_PLUGIN_ROOT}/tools/architecture-mapper.mjs <project-directory>
Parse the JSON output for architecture data and diagrams.
Display each Mermaid diagram with context:
System Architecture: High-level view of all components and how they connect.
[system diagram from tool output]
API Route Map: All endpoints organized by resource.
[routes diagram from tool output]
Database Schema: Entity-relationship diagram of all tables and relations.
[database ER diagram from tool output]
Data Flow: Sequence diagram showing how a typical request flows through the system.
[data flow diagram from tool output]
Based on the scanned data, provide analysis:
Strengths:
Concerns:
Service Dependencies: List all external services and how they're used. Flag any that are single points of failure.
Save architecture documentation:
docs/architecture/ directorydocs/architecture/ARCHITECTURE.md with all diagramsThe document should be self-contained and renderable in GitHub (GitHub supports Mermaid in markdown).
Based on architecture analysis:
Recommend running /architecture after any significant structural change:
The diagrams are generated from code, so they're always accurate when re-run.
The map IS the territory. Architecture diagrams that drift from reality are worse than no diagrams. Because these are auto-generated from code, they're always truthful.