MD Design System
Use this as a lightweight formatter contract.
Core Rules
- Format only — never change facts, decisions, constraints, or values.
- Template first — if another skill defines required sections/fields, keep them.
- One H1 + no heading skips —
#then##then###then####. - Lists over prose — prefer bullets and steps for scanability.
- Named items over tables — use
- **name** — valuefor fields/interfaces. - Canonical syntax —
-bullets,1.ordered lists, fenced code,[label](url). - Lean output — remove decorative noise and repetition.
- Canonical filenames — enforce kebab-case,
-agent.mdfor agents, andSKILL.mdas skill entry file.
Workflow
- Choose scope:
- Single-file edit -> follow lightweight flow.
- Package refactor -> use package mode from references/context-budget.md.
- Pick document profile from references/canonical-profiles.md.
- Keep template-required sections and field placement intact.
- Normalize headings, lists, variables/interfaces, and code formatting.
- Run references/normalization-checklist.md.
Reference Index
- Profiles (section order): references/canonical-profiles.md
- Molecules (section shapes): references/molecules.md
- Syntax rules: references/canonical-syntax.md
- QA and fact-preservation checks: references/normalization-checklist.md
- Context policy: references/context-budget.md
When To Use This Skill
- Formatting/refactoring Markdown for consistent structure.
- Applying style contracts without changing meaning.
- Enforcing predictable, lean outputs across skills and agents.