agentleFS
Sign inStart free
HashLipsHashLips/agent-skills/skills/md-design-system/SKILL.md

md-design-system

Skill29 starsChanged 7 months agoMITView on GitHub

Lightweight Markdown formatter contract for consistent structure across docs, skills, and agents. Use when you need format normalization (headings, sections, lists, syntax) without changing facts or template-required content.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this as a lightweight formatter contract.

    line 8
  2. Distinctive:

    Keep template-required sections and field placement intact.

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MD Design System

Use this as a lightweight formatter contract.

Core Rules

  1. Format only — never change facts, decisions, constraints, or values.
  2. Template first — if another skill defines required sections/fields, keep them.
  3. One H1 + no heading skips — # then ## then ### then ####.
  4. Lists over prose — prefer bullets and steps for scanability.
  5. Named items over tables — use - **name** — value for fields/interfaces.
  6. Canonical syntax — - bullets, 1. ordered lists, fenced code, [label](url).
  7. Lean output — remove decorative noise and repetition.
  8. Canonical filenames — enforce kebab-case, -agent.md for agents, and SKILL.md as skill entry file.

Workflow

  1. Choose scope:
    • Single-file edit -> follow lightweight flow.
    • Package refactor -> use package mode from references/context-budget.md.
  2. Pick document profile from references/canonical-profiles.md.
  3. Keep template-required sections and field placement intact.
  4. Normalize headings, lists, variables/interfaces, and code formatting.
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free