# Pulse

> Dynamic, vibrant style with thick borders, geometric shapes, high-contrast colors, and expressive typography conveying motion and vitality.

- Skill: `ridelink0/pulse` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ridelink0/pulse`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ridelink0/pulse/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- License: MIT
- Author: ridelink0 (https://skillmd.com/u/ridelink0)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/ridelink0/pulse

---


<!-- 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=Limelight 400; JetBrains Mono 100/200/300/400/500/600/700/800 (as shipped on Google Fonts, checked 2026-09-20)
- 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
- Font source: https://fonts.google.com/specimen/Limelight, https://fonts.google.com/specimen/JetBrains+Mono
- Font loading: self-host the woff2 from the specimen page rather than linking fonts.googleapis.com (a visitor's IP reaches Google before the page paints). One @font-face per weight actually used, for example:

  ```css
  @font-face { font-family: "Limelight"; font-weight: 400; font-style: normal; font-display: swap; src: url("/fonts/limelight.woff2") format("woff2"); }
  ```

  The stylesheet Google would serve, if linking it is acceptable for the project: https://fonts.googleapis.com/css2?family=Limelight:wght@400&family=JetBrains+Mono:wght@100;200;300;400;500;600;700;800&display=swap
- 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
- 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 -->