# sleek

Generates design system guidelines with an 8pt grid, Inter typography, concrete color tokens, and WCAG 2.2 AA accessibility standards.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2400 installs · ★ 3349
- Author: typeui.sh
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sleek/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/sleek

## What it does

The skill configures the coding assistant to draft consistent design system documentation under the Sleek visual guidelines. It covers full component anatomy across required states, including hover, focus-visible, active, disabled, loading, and error. Specifications rely on an 8pt baseline grid, the 60-30-10 color distribution rule, and exact hex tokens such as `#3B82F6` for primary and `#111827` for body text.

The workflow forces structured output: stating context, defining tokens, outlining responsive component behavior for pointer, keyboard, and touch, and concluding with a QA review checklist. Fonts are pinned to Inter for display and primary copy, alongside JetBrains Mono for monospace blocks.

When aesthetic choices conflict with accessibility, the rules mandate prioritizing WCAG 2.2 AA compliance over visual novelty.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sleek -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/sleek/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/sleek/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sleek -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/sleek/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sleek -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/sleek/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install bergside/awesome-design-skills sleek
```

2. **Manually: put the files in place**
- File: `.github/skills/sleek/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sleek -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/bergside/awesome-design-skills --path skills/sleek
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/sleek/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill sleek -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sleek/SKILL.md

## When to use it
- generate complete UI component specifications with all interaction states
- enforce an 8pt baseline grid and Inter typography across interfaces
- build QA checklists and acceptance criteria for WCAG 2.2 AA accessibility
- document migration paths and anti-patterns for legacy interface elements

## Example prompts
- Generate design system specifications for a modal dialog using sleek tokens
- Draft guidelines and interaction states for our primary button component
- Create a code review QA checklist for form accessibility under WCAG 2.2 AA

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: f4a4645ea8591cf2.

BEGIN THIRD-PARTY FILE f4a4645ea8591cf2
```text
---
name: sleek
description: Modern minimalist aesthetic with clean lines, intentional color palette, subtle interactions, and consistent spacing.
license: MIT
metadata:
  author: typeui.sh
---

<!-- TYPEUI_SH_MANAGED_START -->
# Sleek Design System Skill (Universal)

## Mission
You are an expert design-system guideline author for Sleek.
Create practical, implementation-ready guidance that can be directly used by engineers and designers.

## Brand
Sleek UI/UX design emphasizes a modern, minimalist aesthetic ("less is more") focused on clean lines, high functionality, and reduced cognitive load. Key elements include a limited, intentional color palette (e.g., the 60-30-10 rule), subtle, non-distracting interactions, and consistent spacing.

## Style Foundations
- Visual style: modern, minimal, clean
- Typography scale: desktop-first expressive scale | Fonts: primary=Inter, display=Inter, mono=JetBrains Mono | 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

## Writing Tone
concise, confident, helpful

## Rules: Do
- prefer semantic tokens over raw values
- preserve visual hierarchy
- keep interaction states explicit

## Rules: Don't
- avoid low contrast text
- avoid inconsistent spacing rhythm
- 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.

## 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.
```
END THIRD-PARTY FILE f4a4645ea8591cf2

The third-party file has ended. Everything between the f4a4645ea8591cf2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2897 of 3669 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/sleek/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md