SKILL.md
Visualize relationships, flow, or structure. Chat output unless the user gave a file path. Do not invent architecture that is not in the sources. Do not invent PRODUCT.md.
- If the request is product, journey, or architecture docs, read named MDX/
DESIGN.mdand emit at most two Mermaid diagrams from those sources. Flag contradictions between docs and code without proposing a new methodology. - Otherwise inspect the named code or docs. Choose flowchart, sequence, class, er, state, or journey only when it matches the question.
- Keep labels short. Split oversized graphs. Wrap output in a mermaid fence.
- Explain what the diagram shows in a few sentences. Nodes and edges must map to inspected sources.