flat

Generate token-based UI component guidelines with WCAG 2.2 AA accessibility rules.

2.3k|211|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bergside/awesome-design-skills --skill flat-bergside
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flat
Source: https://github.com/bergside/awesome-design-skills/tree/main/skills/flat
Command: npx skills add https://github.com/bergside/awesome-design-skills --skill flat-bergside

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flat standardizes how your UI looks and behaves by enforcing a two-dimensional, high-clarity design language with explicit tokens and interaction rules.

Core Features & Use Cases

  • Consistent design foundations: Applies a defined typography scale (Inter + JetBrains Mono), spacing rhythm, and a clear color token set for primary/success/warning/danger with a white surface and near-black text.
  • Accessible interaction guidance: Requires WCAG 2.2 AA alignment, keyboard-first behavior, and visible focus states so components work for real users.
  • Implementation-ready rules: Specifies do/don’t patterns (e.g., avoid low-contrast text and inconsistent spacing) to reduce regressions and keep teams aligned.

Quick Start

Use the flat skill to generate UI component guidelines and token-based implementation rules for a new product screen with buttons, inputs, cards, and navigation that must be accessible and visually consistent.

Frequently Asked Questions about flat

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

FAQPage Schema
How do I create an accessible flat UI design system with consistent color and typography tokens?

To create an accessible flat UI design system, you define explicit color tokens, a structured typography scale, and spacing rhythm. This enforces WCAG 2.2 AA alignment, keyboard-first interactions, and visible focus states for consistent components.

What is the best way to standardize UI component states and spacing across a web application?

The best way to standardize UI component states is by applying a two-dimensional design language with explicit tokens for colors, spacing, and rounding. Using do/don't patterns reduces regressions and keeps teams aligned on visual consistency.

Does flat UI design support WCAG 2.2 AA keyboard-first interactions and visible focus states?

Yes, flat UI design supports WCAG 2.2 AA keyboard-first interactions by requiring visible focus states and accessible interaction behavior. This ensures UI components remain fully navigable and usable for all real users.

Can I use this flat design system approach for responsive web interfaces and layout variants?

Yes, you can use this flat design system approach for responsive web interfaces. It applies design-system authoring rules to component variants, states, and layout behavior, ensuring modern web interfaces remain visually consistent across screen sizes.

Why does my flat UI design have low-contrast text and inconsistent spacing between components?

Flat UI design suffers from low-contrast text and inconsistent spacing when explicit token usage is ignored. Establishing a clear color token set with a white surface and near-black text, alongside do/don't constraints, prevents these visual regressions.