backend-visualize
Installation
SKILL.md
Backend Visualize
Turns real project sources into Mermaid diagrams that render, read well in light and dark themes, and use one color model across every diagram type.
When to Use
- The user asks for any diagram of the backend: data model, classes, roles and access, a process, a request flow, a lifecycle, or the system architecture.
- After
backend-db-design,backend-architectorbackend-refactor, to draw the result. - Not for designing: schema decisions belong to
backend-db-design, architecture choices tobackend-architect. This skill draws what exists or what the user describes.
Before You Start
- Resolve the shared docs folder (""): first
_shared/inside this skill's folder (bundled installs), then../_shared/next to it; other fallbacks are in<shared>/context-loading.md-> Resolving_shared/Files. A missing shared doc is a warning, not a stop. - Read
<shared>/tool-rules.md(mode=auto contract, checkpoints) and<shared>/host-tools.mdif the actions named here do not match your host's tool names. - Load project memory per
<shared>/context-loading.md, but only the files the chosen diagram type needs (see the Sources table). If memory is missing or stale and the source is the codebase, suggestbackend-scanand continue from code.- Skip project and memory checks when the source is a user description or pasted DDL/models. A quick sketch needs no project root.
- If the detected stack matches a file in
<shared>/stacks/, read it (for example ORM and migration layout hints).