# Clean

Simplicity-focused design with ample whitespace, legible typography, and a limited...

- Repository: https://github.com/bergside/awesome-design-skills (3441 stars)
- Category: Design
- License: MIT
- Last updated: 2026-06-28
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add bergside/awesome-design-skills --skill clean -g -a claude-code -y`
Codex: `npx skills add bergside/awesome-design-skills --skill clean -g -a codex -y`
Cursor: `npx skills add bergside/awesome-design-skills --skill clean -g -a cursor -y`
Gemini CLI: `npx skills add bergside/awesome-design-skills --skill clean -g -a gemini-cli -y`

## Description

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

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

<!-- 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.

The rest: https://github.com/bergside/awesome-design-skills/blob/HEAD/skills/clean/SKILL.md