css-tokens
Provides foundational CSS design tokens (custom properties) for typography, spacing, colors, borders, z-index, and transitions. Use when setting up a base token system for a web project.
What this skill does
# CSS Design Tokens Skill
## Purpose
This skill provides a comprehensive set of CSS design tokens (custom properties) to establish a consistent design foundation for web projects. Use this skill when the user requests a base token system or design tokens for their CSS.
## When to Use This Skill
Use this skill when the user asks for:
- "Add design tokens to my project"
- "Set up CSS tokens"
- "Create a tokens file"
- "Add base CSS variables"
- Similar requests for foundational CSS custom properties
## When NOT to Use This Skill
- User already has an existing design token system (suggest modifications instead)
- User specifically requests a framework-specific token system (e.g., Tailwind config, CSS-in-JS tokens)
- User only needs a subset of tokens (offer to extract specific categories)
## What This Skill Provides
A complete `tokens.css` file with a comprehensive design token system:
- **Typography**: Font families, weights, and a modular size scale (xs to 4xl)
- **Spacing**: Consistent size scale from 4px to 96px, named by pixel value
- **Colors**: Using `oklch()` color space for perceptually uniform colors with light/dark mode variants for surfaces, text, brand, interactive elements, and semantic states
- **Borders**: Radius values derived from the size scale (sm to full)
- **Z-index**: Named layers for stacking context (dropdown, modal, toast, etc.)
- **Transitions**: Standard timing values (fast, base, slow)
Users can reference individual tokens using CSS custom property syntax: `var(--token-name)`
## Token Content
The complete token definitions are located in `references/tokens.css` within this skill directory. This file contains all the CSS custom property declarations organized by category.
## How to Use This Skill
### 1. Detect CSS Directory
Search the project for common CSS directory names:
- `css/`
- `styles/`
- `assets/css/`
- `stylesheets/`
- `src/css/`
- `src/styles/`
Check directories at multiple levels (root, `src/`, `public/`, `assets/`).
### 2. Confirm Location with User
**If a CSS directory is found:**
Present the discovered location and ask for confirmation:
```text
I found a CSS directory at [path]. Should I add the design tokens to this directory in a file named `tokens.css`?
If you'd like a different location or filename, please specify both.
```
**If no CSS directory is found:**
Ask the user directly:
```text
I couldn't find an existing CSS directory in your project. Please specify:
1. The directory path where you'd like the tokens file (I can create it if needed)
2. The filename (e.g., `tokens.css`, `design-tokens.css`)
```
### 3. Write the Tokens File
Once confirmed, write the complete tokens file to the specified location. Use the exact content from `references/tokens.css` in this skill directory.
### 4. Inform User About Import
After successfully writing the file, inform the user:
✓ Design tokens written to [full-path]
To use these tokens in your project, import this file in your main CSS file or HTML:
**In CSS:**
```css
@import url('path/to/tokens.css');
```
**In HTML:**
```html
<link rel="stylesheet" href="path/to/tokens.css" />
```
The tokens are now available as CSS custom properties throughout your project (e.g., `var(--color-primary)`, `var(--size-16)`).
## Customization
These tokens provide a solid foundation but are meant to be customized for your project:
- Adjust color values to match your brand
- Modify the spacing scale to fit your design system
- Add project-specific tokens as needed
- Extend categories with additional tokens (animations, shadows, etc.)
This is a **scaffolding skill** - it sets up the initial structure but doesn't handle ongoing modifications.
## Important Notes
- **Do NOT make assumptions** about directory structure or filename if the user hasn't specified
- **Always confirm** the location before writing
- **Create directories** if needed and confirmed by user
- The tokens file includes both light and dark mode color schemes using `prefers-color-scheme`
- The `oklch()` color space provides perceptually uniform colors for better accessibility and consistency
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.