From memstack
Generates Mermaid diagrams for database schemas, API endpoints, components, architecture, and data flows by scanning migrations, directories, package.json, and codebase.
npx claudepluginhub cwinvestments/memstack --plugin memstackThis skill uses the workspace's default tool permissions.
*Generate Mermaid diagrams showing project architecture, schema, and data flow.*
Generates Mermaid diagrams from codebases: flowcharts, class diagrams, sequence diagrams, ER diagrams from DB schemas. Use for architecture visualizations, onboarding, reviews, docs.
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.
Generates Mermaid diagrams (flowcharts, sequences, ER, state, Gantt, etc.) from context and opens shareable interactive mermaid.live URLs in browser for code, architecture, process visuals.
Share bugs, ideas, or general feedback.
Generate Mermaid diagrams showing project architecture, schema, and data flow.
When this skill activates, output:
👁️ Sight — The hidden becomes clear.
Then execute the protocol below.
| Context | Status |
|---|---|
| User asks for a diagram or visualization | ACTIVE — generate diagram |
| User says "draw", "diagram", "architecture" | ACTIVE — generate diagram |
| User asks to "show" or "map" the structure | ACTIVE — generate diagram |
| Discussing diagrams conceptually | DORMANT — do not activate |
| User is looking at existing diagrams | DORMANT — do not activate |
Determine diagram type from context:
erDiagramflowchart TDgraph TDflowchart TD (system overview)sequenceDiagramScan the relevant code:
database/src/app/api/src/app/Generate Mermaid diagram as a code block
Optionally save to docs/diagrams/{name}.mermaid
User: "draw the AdminStack database schema"
👁️ Sight — The hidden becomes clear.
```mermaid
erDiagram
accounts ||--o{ organizations : "has"
accounts ||--o{ cc_sessions : "tracks"
organizations ||--o{ projects : "contains"
organizations ||--o{ contacts : "stores"
organizations ||--o{ orders : "processes"
accounts {
uuid id PK
text email
boolean is_platform_admin
}
cc_sessions {
uuid id PK
text name
text status
}
```