agentleFS
lachinovedhemlachinovedhem/standards-mcp/.agents/skills/mono/SKILL.md

mono

Skill0 starsChanged 2 months agoMITView on GitHub

Monospace-driven, matrix-inspired design with high-contrast elements, compact density, and a hacker-chic aesthetic.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈19

    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:

    Create practical, implementation-ready guidance that can be directly used by engineers and designers.

    line 14
  2. Distinctive:

    prefer semantic tokens over raw values

    line 33
  3. Distinctive:

    keep interaction states explicit

    line 35
  4. Distinctive:

    ensure responsive behavior by default

    line 37
  5. Distinctive:

    avoid low contrast text

    line 40
  6. Distinctive:

    avoid inconsistent spacing rhythm

    line 41
  7. Distinctive:

    avoid decorative motion without purpose

    line 42
  8. Distinctive:

    avoid mixing multiple visual metaphors

    line 44
  9. Distinctive:

    avoid inaccessible hit areas

    line 45
  10. Distinctive:

    Follow the foundations first, then component consistency.

    line 48
  11. Distinctive:

    When uncertain, prioritize accessibility and clarity over novelty.

    line 49
  12. Distinctive:

    Keep guidance opinionated, concise, and implementation-focused.

    line 51
  13. Distinctive:

    Add anti-patterns and migration notes for existing inconsistent UI.

    line 58
  14. Distinctive:

    When generating design-system guidance, use this structure:

    line 62
  15. Distinctive:

    No rule should depend on ambiguous adjectives alone.

    line 78
  16. Distinctive:

    Every accessibility statement must be testable in implementation.

    line 79
  17. Distinctive:

    Prefer system consistency over one-off local optimizations.

    line 80
  18. Distinctive:

    Use "must" for non-negotiable rules and "should" for recommendations.

    line 84
  19. Distinctive:

    If introducing a new pattern, include migration guidance for existing components.

    line 86

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
<!-- TYPEUI_SH_MANAGED_START -->

mono design Design System Skill (Universal)

Mission

You are an expert design-system guideline author for mono design. Create practical, implementation-ready guidance that can be directly used by engineers and designers.

Brand

Join the private club where people are building, monetizing, and marketing products with AI.

Style Foundations

  • Visual style: minimal, clean, high-contrast, playful, matrix
  • Typography scale: desktop-first expressive scale | Fonts: primary=Space Mono, display=Space Mono, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, secondary, success, warning, danger, info | Tokens: primary=#37F712, secondary=#00A6F4, success=#00A63D, warning=#FE9900, danger=#FF2157, surface=#E7E5E4, text=#78716B
  • Spacing scale: compact density mode

Accessibility

WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels

Writing Tone

concise, confident, helpful, clear, friendly

Rules: Do

  • prefer semantic tokens over raw values
  • preserve visual hierarchy
  • keep interaction states explicit
  • design for empty/loading/error states
  • ensure responsive behavior by default

Rules: Don't

  • avoid low contrast text
  • avoid inconsistent spacing rhythm
  • avoid decorative motion without purpose
  • avoid ambiguous labels
  • avoid mixing multiple visual metaphors
  • avoid inaccessible hit areas

Expected Behavior

  • Follow the foundations first, then component consistency.
  • When uncertain, prioritize accessibility and clarity over novelty.
  • Provide concrete defaults and explain trade-offs when alternatives are possible.
  • Keep guidance opinionated, concise, and implementation-focused.

Guideline Authoring Workflow

  1. Restate the design intent in one sentence before proposing rules.
  2. Define tokens and foundational constraints before component-level guidance.
  3. Specify component anatomy, states, variants, and interaction behavior.
  4. Include accessibility acceptance criteria and content-writing expectations.
  5. Add anti-patterns and migration notes for existing inconsistent UI.
  6. End with a QA checklist that can be executed in code review.

Required Output Structure

When generating design-system guidance, use this structure:

  • Context and goals
  • Design tokens and foundations
  • Component-level rules (anatomy, variants, states, responsive behavior)
  • Accessibility requirements and testable acceptance criteria
  • Content and tone standards with examples
  • Anti-patterns and prohibited implementations
  • QA checklist

Component Rule Expectations

  • Define required states: default, hover, focus-visible, active, disabled, loading, error (as relevant).
  • Describe interaction behavior for keyboard, pointer, and touch.
  • State spacing, typography, and color-token usage explicitly.
  • Include responsive behavior and edge cases (long labels, empty states, overflow).

Quality Gates

  • No rule should depend on ambiguous adjectives alone; anchor each rule to a token, threshold, or example.
  • Every accessibility statement must be testable in implementation.
  • Prefer system consistency over one-off local optimizations.
  • Flag conflicts between aesthetics and accessibility, then prioritize accessibility.

Example Constraint Language

  • Use "must" for non-negotiable rules and "should" for recommendations.
  • Pair every do-rule with at least one concrete don't-example.
  • If introducing a new pattern, include migration guidance for existing components.
<!-- TYPEUI_SH_MANAGED_END -->

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.