# modern

Generates editorial design system specs with IBM Plex Serif typography and minimal color tokens. Helps build WCAG 2.2 AA compliant UI rules and review checklists.

- 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/modern/SKILL.md
- Updated: 2026-06-28
- HTML: https://affpapa.org/en/nevibecode/skills/modern

## What it does

The skill instructs the coding assistant to act as a design system guideline author in a clean editorial aesthetic. It locks in specific foundations: IBM Plex Serif for body and display text, JetBrains Mono for monospace snippets, a font scale from 12 to 32, and a spacing scale of 4, 8, 12, 16, 24, and 32. The color palette centers on `#553F83` for primary and surface layers, alongside `#111111` and white.

Outputs follow a structured workflow. The agent defines component anatomy, responsive variations, and states: default, hover, focus-visible, active, disabled, loading, and error. It covers pointer, touch, and keyboard interactions.

The skill strictly enforces WCAG 2.2 AA and explicitly prioritizes accessibility over decorative visual choices whenever a conflict arises. Each generated guideline finishes with a QA checklist suitable for pull request reviews.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

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

## When to use it
- define component anatomy and interaction states for keyboard and touch
- standardize typography around IBM Plex Serif and JetBrains Mono
- generate WCAG 2.2 AA accessibility acceptance criteria
- draft migration notes for inconsistent legacy interface elements

## Example prompts
- Create a button specification using the modern design system with focus-visible and loading states.
- Generate a WCAG 2.2 AA QA checklist for our modal dialog using modern tokens.
- Define the spacing and color token hierarchy for a content card under modern rules.

## 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: 278adb787fc5ee3e.

BEGIN THIRD-PARTY FILE 278adb787fc5ee3e
```text
---
name: modern
description: Contemporary editorial style with serif typography, minimal palettes, and clean layouts for polished digital products.
license: MIT
metadata:
  author: typeui.sh
---

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

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

## Brand
Ship software peacefully

## Style Foundations
- Visual style: modern, minimal, clean, editorial
- Typography scale: 12/14/16/20/24/32 | Fonts: primary=IBM Plex Serif, display=IBM Plex Serif, mono=JetBrains Mono | weights=100, 200, 300, 400, 500, 600, 700, 800, 900
- Color palette: primary, secondary | Tokens: primary=#553F83, secondary=#111111, success=#16A34A, warning=#D97706, danger=#DC2626, surface=#553F83, text=#ffffff
- 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.
- Include responsive behavior and edge cases (long labels, empty states, overflow).

## Quality Gates
```
END THIRD-PARTY FILE 278adb787fc5ee3e

The third-party file has ended. Everything between the 278adb787fc5ee3e 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 2786 of 3393 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/modern/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