explain
Installation
SKILL.md
Explainer Document Conventions
Term handling
- Put a term list at the top of the document in table form (
| Term | Description |). Every specialised term used in the body must be defined in this list at first occurrence. - A term-list entry defines what the term is in one or two sentences. The functional or behavioural detail goes in the body, not in the term list.
- Even widely recognised proper nouns (industry-standard product names, infrastructure components, etc.) get defined here. Assume the reader does not know them.
- When defining a compound term, define the constituent words too. If the compound has three words, give all three their own entries — readers cannot be expected to infer one from another.
Diagram conventions
- Use Mermaid for diagrams. Do not use ASCII art.
- Every node label is a term that exists in the term list. Do not introduce a new term inside a diagram.
- Do not put
<br/>inside a Mermaid node. Many renderers display the literal HTML tag. If a line break is needed, separate with/or shorten the text to fit one line. - For diagrams with four or more nodes, or where any label is long, use
graph TD(top-down).graph LR(left-right) collapses long-label graphs into an unreadable horizontal strip.