New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Clean

by bergside in bergside/awesome-design-skills

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

MITAuto-check passedFrontend & Design

Install Clean

skills CLI
$ npx skills add bergside/awesome-design-skills --skill clean -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bergside/awesome-design-skills clean --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bergside/awesome-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/clean .claude/skills/clean && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
clean
GitHub stars
3.1k
Used in
1 other repo
Token cost
~918 tokens
SKILL.md length
407 words
Files
2
Skills in repo
67
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 6 steps: Restate the design intent in one… → Define tokens and foundational… → Specify component anatomy, states,… → …
  • Tasks that involve Theming and dark mode
  • SKILL.md covers Mission, Brand, Style Foundations and Accessibility, plus 9 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Clean is an agent skill from bergside/awesome-design-skills. Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

Its SKILL.md is about 920 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `DESIGN.md`).

It sits in Frontend & Design, covering Theming and dark mode, Typography and Accessibility. The repository describes itself as: List of 67 awesome DESIGN.md and SKILL.md design skill files for agentic tools like Claude Design, Google Stitch, Codex, Cursor, and other AI tools. The licence is MIT.

When your agent uses it

  • Tasks that involve Theming and dark mode
  • Tasks that involve Typography
  • Tasks that involve Accessibility

Example prompts

  • “/clean”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  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.

What it can do on your machine

Read from SKILL.md and the folder at commit f631a09. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Clean loads about 918 tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 407 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~32
When it runs · the whole SKILL.md, loaded when a task matches
~918

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bergside/awesome-design-skills at commit f631a09, republished under its MIT licence (© bergside). 407 words, ~918 tokens.

Download SKILL.mdSave it as .claude/skills/clean/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
clean
description
Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.
license
MIT
metadata.author
typeui.sh
<!-- 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.
Show full SKILL.md (159 more words)Show less

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

© bergside, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/clean of bergside/awesome-design-skills.

  • SKILL.md
  • DESIGN.md

Open the folder on GitHubat commit f631a09

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in bergside/awesome-design-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Clean next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Clean compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Clean this skillbergside/awesome-design-skills3.1k1 repos~918Automated safety check: PassMIT
UI UX Pro MaxOhh-889/skyroc79527 repos~3.6kAutomated safety check: NotesMIT
iOS Design GuidelinesMacMagazine/app-iOS171—~767Automated safety check: PassNone
Frontend Designjwynia/agent-skills166—~3.2kAutomated safety check: PassMIT
Design Token Generatordylanfeltus/skills179—~2.9kAutomated safety check: PassMIT
UI UX Pro Maxselmakcby/claude-agents-skills136—~777Automated safety check: PassMIT

Similar skills

  • UI UX Pro Max

    Ohh-889/skyroc

    UI/UX design intelligence. An agent skill from Ohh-889/skyroc.

    795 GitHub starsUsed in 27 repos~3.6k tokens
    Frontend & DesignAuto-check: notes

  • iOS Design Guidelines

    MacMagazine/app-iOS

    MacMagazine design reference — theme tokens, card selection, typography, touch targets, accessibility, dark mode.

    171 GitHub stars~767 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Frontend Design

    jwynia/agent-skills

    Create distinctive, production-grade frontend interfaces with high design quality.

    166 GitHub stars~3.2k tokensUpdated 7 mo ago
    Frontend & DesignAuto-check passed

  • Design Token Generator

    dylanfeltus/skills

    Generates type scales, color palettes, spacing systems, WCAG contrast checks and dark mode palettes from formulas, as CSS custom properties, a Tailwind config or JSON tokens.

    179 GitHub stars~2.9k tokensUpdated 20 days ago
    Frontend & DesignAuto-check passed

  • UI UX Pro Max

    selmakcby/claude-agents-skills

    UI/UX design intelligence for web and mobile. An agent skill from selmakcby/claude-agents-skills.

    136 GitHub stars~777 tokensUpdated 5 mo ago
    Frontend & DesignAuto-check passed

  • Theming Components

    ancoleman/ai-design-components

    Provides design token system and theming framework for consistent, customizable UI styling across all components.

    526 GitHub stars~2.3k tokensUpdated 10 mo ago
    Frontend & DesignAuto-check passed

More from bergside/awesome-design-skills

All 67 skills in this repo

  • Agentic

    bergside/awesome-design-skills

    Conversational AI-first interface with minimal controls, clear outcomes, and delegated task flows for agentic workflows.

    3.1k GitHub starsUsed in 1 repo~991 tokens
    Auto-check passed

  • Ant

    bergside/awesome-design-skills

    Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

    3.1k GitHub starsUsed in 1 repo~956 tokens
    Auto-check passed

  • Artistic

    bergside/awesome-design-skills

    High-contrast, expressive style with creative typography and bold color choices for visually striking interfaces.

    3.1k GitHub starsUsed in 1 repo~938 tokens
    Auto-check passed

  • Basic

    bergside/awesome-design-skills

    Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

    3.1k GitHub starsUsed in 1 repo~969 tokens
    Auto-check passed

  • Bento

    bergside/awesome-design-skills

    Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.

    3.1k GitHub starsUsed in 1 repo~878 tokens
    Auto-check passed

  • Bold

    bergside/awesome-design-skills

    Strong visual presence with heavyweight typography, high-contrast colors, and commanding layouts.

    3.1k GitHub starsUsed in 1 repo~854 tokens
    Auto-check passed

Categories

Questions about Clean

What does Clean do?

Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter. Clean is an agent skill from bergside/awesome-design-skills. Simplicity-focused design with ample whitespace, legible typography, and a limited color palette to reduce visual clutter.

When should I use Clean?

Clean fits situations like: tasks that involve Theming and dark mode; tasks that involve Typography; tasks that involve Accessibility.

How do I install Clean in Claude Code?

Run `npx skills add bergside/awesome-design-skills --skill clean -a claude-code`. Or copy the skill folder (skills/clean in bergside/awesome-design-skills) into .claude/skills/clean in your project. Claude Code loads it when a task matches its description.

How do I install Clean in Codex?

Run `npx skills add bergside/awesome-design-skills --skill clean -a codex`. Or copy the skill folder (skills/clean in bergside/awesome-design-skills) into .agents/skills/clean in your project. Codex loads it when a task matches its description.

Can I use Clean in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bergside/awesome-design-skills --skill clean -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/clean, .gemini/skills/clean, .github/skills/clean and .opencode/skills/clean in your project.

What does Clean need to run?

SKILL.md names no scripts, command-line tools or credentials: Clean is instructions for the agent only.

Does Clean access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Clean safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Clean use?

Clean is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Clean use?

About 918 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Clean?

Skills that share tags, products or a category with Clean: UI UX Pro Max (Ohh-889/skyroc, 795 stars), iOS Design Guidelines (MacMagazine/app-iOS, 171 stars), Frontend Design (jwynia/agent-skills, 166 stars) and Design Token Generator (dylanfeltus/skills, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Clean?

bergside (a GitHub organization) maintains it in bergside/awesome-design-skills, which has 3,081 GitHub stars. The repository holds 67 skills in this directory. The repository was last updated on June 28, 2026.

Source: bergside/awesome-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.