# expressive

Guides AI agents to author design system rules with bold colors and IBM Plex Mono typography. Keeps interfaces aligned with WCAG 2.2 AA standards.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 2300 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/expressive/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/expressive

## What it does

The skill configures the agent to draft guidelines for the Expressive design system. It enforces a typography scale from 14 to 40 using only IBM Plex Mono across all text styles. The palette relies on `#db2777` as primary, `#2563eb` as secondary, and `#FFFFFF` for surfaces. Spacing strictly adheres to steps 4, 8, 12, 16, 24, and 32.

When describing components, the agent must define states like hover, active, focus-visible, disabled, loading, and error. Rules require concrete thresholds or tokens instead of vague adjectives. Accessibility always takes precedence. If visual flair clashes with WCAG 2.2 AA contrast, accessibility wins.

The entire type system is locked to a monospace font. This creates an immediate mismatch for projects that rely on standard sans-serif layouts.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add bergside/awesome-design-skills --skill expressive -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/expressive/SKILL.md

## When to use it
- generate component specifications with WCAG 2.2 AA compliance criteria
- document interaction states for pointer, keyboard, and touch
- enforce strict spacing and typography tokens in design guidelines
- create actionable QA checklists for interface code reviews

## Example prompts
- Write a design system guideline for a modal dialog using expressive tokens
- Create a WCAG 2.2 AA compliance checklist for an interactive button component
- Define states and spacing rules for an alert banner in the expressive style

## 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: 63c7af85e8cb1308.

BEGIN THIRD-PARTY FILE 63c7af85e8cb1308
```text
---
name: expressive
description: Vibrant, personality-driven design with bold colors, playful graphics, and dynamic layouts that balance creativity with structure.
license: MIT
metadata:
  author: typeui.sh
---

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

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

## Brand
A vibrant and visually engaging design style that uses bold colors, playful graphics, and dynamic layouts to create a strong personality. It emphasizes creativity and energy while maintaining clear structure and modern UI patterns.

## Style Foundations
- Visual style: modern, playful
- Typography scale: 14/16/18/24/32/40 | Fonts: primary=IBM Plex Mono, display=IBM Plex Mono, mono=IBM Plex Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary, neutral, success, warning, danger | Tokens: primary=#db2777, secondary=#2563eb, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#FFFFFF, text=#111827
- Spacing scale: 4/8/12/16/24/32


## 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.
- State spacing, typography, and color-token usage explicitly.
```
END THIRD-PARTY FILE 63c7af85e8cb1308

The third-party file has ended. Everything between the 63c7af85e8cb1308 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 2927 of 3636 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/expressive/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