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

clean

Skill0 starsChanged 2 months agoMITView on GitHub

Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

20 other projects use a version of this, 1 of them edited.

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

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 16

    Distinctive

    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 34
  4. Distinctive:

    avoid low contrast text

    line 38
  5. Distinctive:

    avoid inconsistent spacing rhythm

    line 39
  6. Distinctive:

    avoid decorative motion without purpose

    line 40
  7. Distinctive:

    Follow the foundations first, then component consistency.

    line 44
  8. Distinctive:

    When uncertain, prioritize accessibility and clarity over novelty.

    line 45
  9. Distinctive:

    Keep guidance opinionated, concise, and implementation-focused.

    line 47
  10. Distinctive:

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

    line 54
  11. Distinctive:

    When generating design-system guidance, use this structure:

    line 58
  12. Distinctive:

    No rule should depend on ambiguous adjectives alone.

    line 74
  13. Distinctive:

    Every accessibility statement must be testable in implementation.

    line 75
  14. Distinctive:

    Prefer system consistency over one-off local optimizations.

    line 76
  15. Distinctive:

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

    line 80
  16. Distinctive:

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

    line 82

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “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 -->

Clean Design System Skill (Universal)

Mission

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

Brand

Clean design style focuses on simplicity, minimalism, and high usability, using ample whitespace, legible typography, and limited color palettes to reduce visual clutter

Style Foundations

  • Visual style: minimal, clean
  • Typography scale: 12/14/16/20/24/32 | Fonts: primary=Roboto, display=Poppins, mono=Inconsolata | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
  • Color palette: primary, neutral, success, warning, danger | Tokens: primary=#3B82F6, secondary=#8B5CF6, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
  • Spacing scale: 8pt baseline grid

Accessibility

WCAG 2.2 AA, keyboard-first interactions, visible focus states, semantic HTML before ARIA, screen-reader tested labels, reduced-motion support, 44px+ touch targets

Writing Tone

clear, friendly

Rules: Do

  • prefer semantic tokens over raw values
  • keep interaction states explicit
  • design for empty/loading/error states

Rules: Don't

  • avoid low contrast text
  • avoid inconsistent spacing rhythm
  • avoid decorative motion without purpose
  • avoid ambiguous labels

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.