elegant

Standardizes UI design systems with token-based typography, color, spacing, and WCAG 2.2 AA accessibility rules.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elegant helps teams implement a consistent, refined design aesthetic while maintaining accessible typography, spacing, and interaction patterns.

Core Features & Use Cases

  • Refined visual foundations: Defines a minimal, clean style with explicit typography (Google Sans + Anonymous Pro), color tokens, and a spacing scale.
  • Accessibility-first behavior: Establishes WCAG 2.2 AA expectations including keyboard-first interactions and visible focus states.
  • Implementation-ready guidance: Provides do/don’t rules and quality gates so components stay consistent and reviewable as the UI grows.

Example use case: create a landing page UI where headings, labels, buttons, and navigation share the same hierarchy, tokens, and interaction states across desktop and mobile.

Quick Start

Use the elegant skill to generate and review UI guidelines for a new design system component set while ensuring tokenized colors, consistent spacing, and WCAG 2.2 AA focus behavior.

Frequently Asked Questions about elegant

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

FAQPage Schema
How do I build a minimal UI design system with consistent typography and spacing?

To build a minimal UI design system, define explicit typography scales, color tokens, and spacing foundations. Apply opinionated token-first rules to standardize visual hierarchy and maintain consistent interaction patterns across all components.

What's the best way to enforce WCAG 2.2 AA accessibility in a design system?

Enforce WCAG 2.2 AA accessibility by establishing keyboard-first interaction constraints and explicit visible focus states. Apply these rules as testable quality gates during code review to ensure components remain compliant as the UI grows.

How do I standardize component states and interaction patterns for responsive edge cases?

Standardize component states by applying token-first rules and explicit interaction state definitions. Use do/don't implementation guidance and testable quality gates to maintain consistent behavior across desktop and mobile responsive edge cases.

Can I use design tokens to keep interface hierarchy consistent across a landing page UI?

Yes, you can use design tokens to keep interface hierarchy consistent. Tokenized colors and defined typography scales ensure that headings, labels, buttons, and navigation share the same visual hierarchy across desktop and mobile views.

Does a token-first design system require predefined quality gates for component code review?

A token-first design system requires predefined quality gates for component code review. These testable rules verify that tokenized colors, consistent spacing, and WCAG 2.2 AA focus behavior remain standardized as the UI scales.

Why does my UI design system lose visual consistency when adding new components?

Your UI design system loses visual consistency without explicit token-first rules and do/don't component guidance. Implementing testable quality gates for typography, spacing, and interaction states prevents aesthetic drift during code review.