clean

Generate accessibility-first UI component guidance using Clean tokens and WCAG 2.2 AA rules.

Updated May 13, 2026
One-click install
npx skills add https://github.com/superpollo02/awesome-design-skill --skill clean-superpollo02
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean
Source: https://github.com/superpollo02/awesome-design-skill/tree/main/skills/clean
Command: npx skills add https://github.com/superpollo02/awesome-design-skill --skill clean-superpollo02

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Clean skill eliminates inconsistent visual decisions by providing a simple, accessibility-first design system that reduces clutter and improves legibility.

Core Features & Use Cases

  • Typography + spacing foundations: enforces the 12/14/16/20/24/32 scale and an 8pt baseline grid for consistent rhythm across screens.
  • Tokenized color system: standardizes primary, secondary, success, warning, danger, surface, and text (with neutral derived from surface) to keep UI predictable.
  • Accessibility and quality gates: requires WCAG 2.2 AA practices like visible focus states, semantic-first markup, reduced-motion support, and testable acceptance criteria.

Quick Start

Tell your AI agent to apply the Clean skill tokens and accessibility rules when generating a set of UI components for a new product page.

Frequently Asked Questions about clean

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize UI components for WCAG 2.2 AA compliance?

Standardize UI components for WCAG 2.2 AA compliance by applying tokenized color systems, semantic-first markup, visible focus states, and keyboard-first behavior rules. This ensures accessibility quality gates are met across common product interfaces like buttons and inputs.

What is the best way to build a minimal design system with consistent spacing?

Build a minimal design system using a 12/14/16/20/24/32 typography scale and an 8pt baseline grid for spacing rhythm. This eliminates inconsistent visual decisions by enforcing predictable layout proportions across screens.

How do I generate accessible error and loading states for UI components?

Generate accessible error and loading states by applying standardized interaction rules, reduced-motion support, and touch target sizing. This approach enforces legibility and predictable user experiences during interface state changes.

Can I use tokenization to manage color and typography in an accessibility-first design system?

Yes, tokenization manages color and typography in an accessibility-first design system by standardizing primary, secondary, surface, and text values. This keeps UI predictable and ensures derived neutral colors maintain contrast ratios.

Does semantic-first markup work with keyboard-first behavior for UI accessibility?

Semantic-first markup works natively with keyboard-first behavior by ensuring visible focus states and testable acceptance criteria. This combination fulfills WCAG 2.2 AA requirements without relying solely on ARIA attributes.

Why does my UI design system fail accessibility quality gates for modals and navigation?

UI design systems fail accessibility quality gates when they lack token-anchored testable acceptance criteria, proper touch target sizing, or reduced-motion support. Enforcing strict state rules for modals and navigation resolves these compliance gaps.