Help us improve
Share bugs, ideas, or general feedback.
From techne
Draws faithful architecture or structure diagrams of real codebases by scanning the repo. Supports system architecture, request lifecycle, data models, state transitions, and type structure diagrams.
npx claudepluginhub lynxlangya/techne --plugin techneHow this skill is triggered — by the user, by Claude, or both
Slash command
/techne:vizThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Investigate by diagramming. The diagram is the byproduct; the value is forcing
Generates Mermaid diagrams from codebase analysis for database schemas, APIs, components, and architecture. Activated by 'draw', 'diagram', 'visualize', or 'architecture'.
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 flowcharts visualizing high-level codebase component relationships. Use for onboarding, PR reviews, and understanding system structure.
Share bugs, ideas, or general feedback.
Investigate by diagramming. The diagram is the byproduct; the value is forcing real investigation before drawing.
diagramKind from the table below. If the
user's intent fits multiple kinds, ask one short clarification instead of
guessing.architecture, enumerate roots,
manifests, workspace/build/native/container/edge/infra/source-only signals.
For other kinds, find the bounded entrypoint, schema, state enum, workflow,
or module/type namespace before drawing.architecture, state one project shape and
cite evidence: single-frontend, single-backend, coupled-fullstack,
monorepo, library, native, native+edge, source-only code, or
non-code. For other kinds, state the bounded scope and the files that prove
it.architecture at 12-15 top-level nodes by
default. For other kinds, use the validator's participant/message,
entity/relationship, state/transition, or type/member limits. Split into
drill-down diagrams when needed.%% techne:source <elementRef> <path>[#<symbol>] or, for relationship-like
elements only, %% techne:inferred <relationshipRef> <reason>. Entity-like
elements always need verified techne:source; relationship-like elements
need file+symbol proof unless explicitly inferred with sourced endpoints.
Use actor for human sequence participants so the actor path-only allowance
is mechanically scoped. Solid relationships mean read-from-code. Dashed or
labeled relationships mean inference only where the selected Mermaid type
supports it.scripts/store_viz.py, always build
the self-contained viewer, and only open it when the session is interactive.| User intent | diagramKind | Mermaid type | Evidence focus |
|---|---|---|---|
| Project architecture, module/service/package topology | architecture | flowchart / graph | Manifests, workspaces, imports, services, bindings, infra edges. |
| Request lifecycle, command/job flow, actor conversation | interaction | sequenceDiagram | Entrypoint, ordered calls/messages, handlers, clients, queues. |
| Tables, entities, persistence relationships | data-model | erDiagram | Schema, migrations, ORM/entity declarations, foreign keys, associations. |
| Status/order/task/review lifecycle | state-model | stateDiagram-v2 / stateDiagram | Status constants, state machines, reducers, guards, transition handlers. |
| Classes, interfaces, structs, protocols, bounded type structure | type-structure | classDiagram | Type declarations, inheritance, implementation, composition, public method groups. |
Examples:
architecture.interaction.data-model.state-model.type-structure.node skills/viz/scripts/validate-mermaid.mjs diagram.md --project /path/to/project --max-nodes 15python3 skills/viz/scripts/store_viz.py --project /path/to/project --name login-flow --title "Login flow" --diagram diagram.md --shape monorepopython3 skills/viz/scripts/build_viewer.py --project /path/to/project --openThe validator expects mermaid@11.15.0 and jsdom to be installed in one of
these places: TECHNE_VIZ_NODE_MODULES, skills/viz/scripts/node_modules, the
current working directory, or an ancestor directory.
.techne/ content inside this repository while authoring the
skill itself.