# pulse

Provides rules for the vibrant Pulse design system with 4px borders, orange color tokens, and Limelight typography. Generates component specs and checks WCAG 2.2 AA criteria.

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

## What it does

The skill configures the model as a guideline author for the Pulse design system. Pulse pairs high-contrast orange tokens (`#EA580B`, `#F59E0B`, `#FFEDD5`, `#FDBA74`, `#EA580C`) with signature 4px borders. Typography relies on Limelight with 400 weight for primary and display text, while code blocks use JetBrains Mono.

The workflow mandates strict outputs for every UI component. The model defines states from default to focus-visible, sets responsive rules, and writes a QA checklist for code reviews. Delicate borders are prohibited. Interactions favor snappy spring-based motion.

If visual choices clash with readability, the rules force a fallback to accessibility. Delicate borders are completely banned here, so quiet minimalist layouts are impossible under this system.

## Install

### Claude Code (native platform)

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

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

### Codex

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

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

### Cursor

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

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

### GitHub Copilot

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

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

### Gemini CLI

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

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

### Windsurf (Devin Desktop)

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

### OpenCode

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

## When to use it
- generate component specifications under the Pulse design system
- verify contrast and keyboard navigation against WCAG 2.2 AA
- build front-end QA checklists for code review
- define design tokens for 4px borders and spacing

## Example prompts
- Generate a Button component specification following Pulse design system rules
- Create a QA checklist for accessible form controls under WCAG 2.2 AA
- Define token values and states for an alert banner in Pulse 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: 974f1adecdc21524.

BEGIN THIRD-PARTY FILE 974f1adecdc21524
```text
---
name: pulse
description: Dynamic, vibrant style with thick borders, geometric shapes, high-contrast colors, and expressive typography conveying motion and vitality.
license: MIT
metadata:
  author: typeui.sh
---

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

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

## Brand
Pulse design style embodies vibrant, dynamic, and bold aesthetics. It uses thick borders, striking geometric shapes, high-contrast colors (like vibrant oranges), and expressive typography to convey motion, vitality, and power.

## Style Foundations
- Visual style: bold, geometric, vibrant, thick-bordered
- Typography scale: 12/14/16/20/24/32/48 | Fonts: primary=Limelight, display=Limelight, mono=JetBrains Mono | weights=400
- Color palette: primary, secondary, neutral | Tokens: primary=#EA580B, secondary=#F59E0B, background=#FFEDD5, surface=#FDBA74, text=#EA580C
- Spacing scale: 4/8/12/16/24/32/48/64
- Borders: Thick 4px borders are a signature element.


## Accessibility
WCAG 2.2 AA, keyboard-first interactions, visible focus states. High contrast is naturally achieved through bold colors and thick borders.

## Writing Tone
punchy, dynamic, motivating, bold

## Rules: Do
- prefer semantic tokens over raw values
- use thick (4px) borders for structural elements and containers
- preserve visual hierarchy with bold typography and scale
- keep interaction states explicit with scale/transform animations

## Rules: Don't
- avoid thin or delicate borders
- avoid low contrast text
- avoid inconsistent spacing rhythm
- avoid subtle or slow animations; prefer snappy, spring-based motion

## 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
```
END THIRD-PARTY FILE 974f1adecdc21524

The third-party file has ended. Everything between the 974f1adecdc21524 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 2955 of 3898 bytes. © typeui.sh · MIT · https://github.com/bergside/awesome-design-skills/tree/HEAD/skills/pulse/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