Keep SKILL_KR.md synchronized whenever the substantive instructions in this file change.
Use This Skill For
Apply this skill when using flowcharts, Mermaid, or other diagram-like structures in Markdown.
This skill is for diagram structure and Mermaid authoring only.
Common Diagram Contract
- Within one diagram, arrows should carry only one meaning.
Example: in the overall picture of a math-heavy THEORY note, the arrows should be either inclusion maps or forgetful maps, not a mixture of both.
- If no separate rule already fixes the arrow meaning, choose one meaning first and state below the diagram what the arrows mean; if more than one arrow meaning is needed, draw separate diagrams instead of mixing those meanings in one diagram.
- Do not draw both a transitive chain such as
A -> B -> C and a direct A -> C arrow in the same diagram without the user's approval.
- If both a transitive chain and a direct edge seem necessary, stop and check whether the real problem is the relation design between the underlying targets or just the diagrammatic expression.
- Even when the user approves it, prefer separating the transitive-chain view and the direct-relation view into different diagram blocks.