design-prototyping
The craft of building design exploration prototypes. Covers file structure, control wiring, styling conventions, and output validation. Preloaded into the html-prototyper agent. Not intended for direct invocation.
What this skill does
# Design Prototyping
How to build a single self-contained design exploration variation file.
## File Format
Every variation is a single HTML file with embedded metadata. The file is a complete page rendered inside an iframe in the gallery shell.
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<script src="https://cdn.tailwindcss.com"></script>
<link rel="preconnect" href="https://fonts.googleapis.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
<!-- Google Fonts <link> for specified fonts -->
<script type="application/json" id="variation-meta">
{
"id": "A1",
"family": "A",
"familyName": "...",
"name": "...",
"layoutType": "...",
"aesthetic": "...",
"description": "...",
"controls": [ /* control objects — see Control Schema below */ ]
}
</script>
<style>
:root {
/* All theme values as CSS custom properties */
}
:root * {
transition: color 0.3s ease, background-color 0.3s ease,
border-color 0.3s ease, padding 0.3s ease,
gap 0.3s ease, font-size 0.3s ease,
border-radius 0.3s ease, box-shadow 0.3s ease,
max-width 0.3s ease, width 0.3s ease;
}
</style>
</head>
<body>
<!-- Variation content -->
</body>
</html>
```
### Metadata Block
The `<script type="application/json" id="variation-meta">` block in `<head>` contains valid JSON with:
| Field | Type | Description |
|---|---|---|
| `id` | string | Variation code, e.g. `"A1"`, `"B2"` |
| `family` | string | Family letter, e.g. `"A"` |
| `familyName` | string | Human-readable family name |
| `name` | string | Memorable variation name |
| `layoutType` | string | Layout description, e.g. `"Sidebar + Cards"` |
| `aesthetic` | string | Aesthetic description, e.g. `"Clean Light"` |
| `description` | string | One-line description of the variation |
| `controls` | array | 4-6 control objects (see schema below) |
Populate all fields from the variation brief provided in the prompt.
## Styling Rules
- **Tailwind-first.** Utility classes for layout, spacing, colors, typography, borders, shadows. Custom CSS in `<style>` only for: `:root` property definitions, `@keyframes`, transitions, scrollbar styling.
- **CSS custom properties on `:root`.** All theme values: colors, fonts, spacing, radii. Unprefixed names: `--bg`, `--text`, `--accent`. Never `--shell-*`. Reference via Tailwind arbitrary values: `bg-[var(--bg)]`, `text-[var(--text)]`, `rounded-[var(--radius)]`.
- **Self-contained.** No external images. Use CSS gradients, inline SVG, Unicode.
- **Realistic content only.** Never lorem ipsum. Use the data from the prompt.
- **Motion.** Hover transitions on interactive elements. At least one entrance animation with staggered delays. JavaScript is allowed for interactive demonstrations (accordions, toggles, wizards).
- **Component scope.** For components (not full pages), center content in the viewport: `min-h-screen flex items-center justify-center p-8` on `<body>`.
- **Viewport containment.** The outermost container element must use `overflow-hidden` (or `overflow-auto` if scrolling is intentional). This prevents content from breaking out of the iframe bounds. Apply to the root layout wrapper, not `<body>`.
- **Transition CSS required.** The `:root * { transition: ... }` rule (shown in file format above) must be included for smooth control changes.
## Control Schema
Controls are **JSON metadata only**. Define them in the `controls` array inside the variation-meta block. A separate gallery shell reads this JSON and renders the control UI (sliders, dropdowns, toggles) outside the iframe.
**Do NOT build any control panel, settings panel, or configuration UI into the variation HTML.** The variation contains only the design content. All control rendering and interaction is handled by the shell.
Include 4-6 controls in the `controls` array.
### Two types of controls
**CSS controls** (default) — The shell sets a CSS custom property on `:root` via `style.setProperty()`. The HTML references it via `var()`. This is automatic — no JS needed in the variation. Use for visual parameters: colors, spacing, radii, opacity, font sizes, layout widths.
**Event controls** — For behavioral parameters that CSS can't express (sort order, filter thresholds, data grouping, expansion mode). The shell sets the CSS var AND dispatches a `CustomEvent` on the iframe's `document`. The variation includes a JS listener that reads the value and updates the DOM.
To make a control an event control, add `"event": true` to the control JSON. The shell dispatches `control-change` events with `{ detail: { id, value } }` for all controls, but only event controls need a listener.
Event controls still need a `cssVar` (it can be a dummy like `"--sort-order"`) so the shell has something to set. The actual work happens in your listener.
### Range
Value + unit are set directly on the CSS var.
```json
{
"id": "sidebar-width",
"label": "Sidebar Width",
"type": "range",
"min": 180, "max": 320, "step": 10,
"options": null,
"value": 240,
"defaultValue": 240,
"unit": "px",
"cssVar": "--sidebar-width"
}
```
### Select (single CSS var)
Maps option labels to CSS values via `cssValues`.
```json
{
"id": "accent",
"label": "Accent Color",
"type": "select",
"min": null, "max": null, "step": null,
"options": ["coral", "teal", "indigo", "amber"],
"cssValues": { "coral": "#e07a5f", "teal": "#4a9e8f", "indigo": "#5c6bc0", "amber": "#d4a853" },
"value": "teal",
"defaultValue": "teal",
"unit": "",
"cssVar": "--accent"
}
```
### Select (multi-var)
When one control changes multiple CSS properties, use an object as the `cssValues` value and set `cssVar: null`.
```json
{
"id": "mood",
"label": "Mood",
"type": "select",
"min": null, "max": null, "step": null,
"options": ["light", "dark", "midnight"],
"cssValues": {
"light": { "--bg": "#faf9f7", "--text": "#2d2a26", "--text-dim": "#8a8580", "--border": "#e5e0d8" },
"dark": { "--bg": "#1e1e2a", "--text": "#e0ddd8", "--text-dim": "#8a8580", "--border": "#333340" },
"midnight": { "--bg": "#0d0d14", "--text": "#c8c4be", "--text-dim": "#6a6660", "--border": "#1e1e2a" }
},
"value": "light",
"defaultValue": "light",
"unit": "",
"cssVar": null
}
```
### Toggle
Maps `true`/`false` to CSS values. Without `cssValues`, defaults to `"1"`/`"0"`.
```json
{
"id": "show-dividers",
"label": "Show Dividers",
"type": "toggle",
"min": null, "max": null, "step": null,
"options": null,
"cssValues": { "true": "1px", "false": "0px" },
"value": true,
"defaultValue": true,
"unit": "",
"cssVar": "--divider-width"
}
```
### Event Control Pattern
When a control needs to drive behavior (not just CSS), mark it with `"event": true` and add a listener in the variation's `<script>`:
```json
{
"id": "sort-order",
"label": "Sort By",
"type": "select",
"options": ["status", "last-active", "name"],
"cssValues": { "status": "status", "last-active": "last-active", "name": "name" },
"value": "status",
"defaultValue": "status",
"unit": "",
"cssVar": "--sort-order",
"event": true
}
```
```html
<script>
document.addEventListener('control-change', (e) => {
const { id, value } = e.detail;
if (id === 'sort-order') {
sortAgents(value); // your function that re-sorts the DOM
}
});
// Also handle initial state — controls-ready fires once after all
// CSS vars are set on first iframe load
document.addEventListener('controls-ready', () => {
const sort = getComputedStyle(document.documentElement)
.getPropertyValue('--sort-order').trim();
if (sort) sortAgents(sort);
});
</script>
```
The `controls-ready` event fires once after all controls are applied on iframe load. Use it to read initial CSS var values and set up initial statRelated 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.