reference-design-contract
Turn vague taste, screenshots, URLs, product notes, or "make it feel like this" references into a grounded DESIGN.md plus an implementation handoff. Use it before prototypes, decks, redesigns, or image remix work when the user needs a reusable visual direction rather than a one-off prompt.
What this skill does
# Reference Design Contract
Use this skill when the user has taste signals, references, or a rough "like
this" request and needs a reusable design contract before generation. The goal
is not to write a longer prompt. The goal is to make design decisions explicit
enough that a later prototype, deck, redesign, or image-remix run can execute
without guessing.
## What this skill produces
Create three files:
1. `DESIGN.md` — the reusable visual direction, following Open Design's
standard nine-section design-system shape.
2. `design-contract.md` — the decision record: evidence used, keep/change
boundaries, rationale, risks, and quality gate.
3. `implementation-handoff.md` — concise build instructions for the next
artifact-producing skill or coding agent.
If a preview is useful, also create `example.html` as a small hand-built
contract preview. Do not make it the main deliverable.
## Workflow
1. **Lock the job.** Identify target artifact type, audience, brand/product
context, references, and constraints. Ask at most two questions only when a
missing answer would change the direction. Otherwise choose a sensible
default and label it as inferred.
2. **Read evidence.** Use provided screenshots, URLs, existing `DESIGN.md`,
brand docs, image artifacts, or user notes. If evidence is missing, say so
and base the contract on the brief only; do not invent brand facts.
3. **Separate reference semantics.** For every reference, split it into:
- `Keep`: qualities to preserve, such as density, composition, material,
typography rhythm, color temperature, or motion attitude.
- `Change`: subject matter, copy, brand marks, exact layout, protected
assets, and anything the user wants adapted.
- `Do not copy`: literal screenshots, logos, claims, pricing, proprietary
UI, or exact prompt wording from examples.
4. **Freeze the direction.** Choose one coherent visual stance. Do not provide
five unrelated moodboards. If there are genuinely competing directions,
name them briefly, pick the recommended one, and continue.
5. **Write `DESIGN.md`.** Use these nine headings exactly:
- `## 1. Visual Theme & Atmosphere`
- `## 2. Color`
- `## 3. Typography`
- `## 4. Spacing & Grid`
- `## 5. Layout & Composition`
- `## 6. Components`
- `## 7. Motion & Interaction`
- `## 8. Voice & Brand`
- `## 9. Anti-patterns`
6. **Write `design-contract.md`.** Include:
- goal and target artifact
- evidence table with confidence (`observed`, `provided`, `inferred`)
- keep/change/do-not-copy table
- final design stance in one paragraph
- risks and explicit unknowns
- quality gate checklist
7. **Write `implementation-handoff.md`.** Keep it short and operational:
- files to read
- token/palette/type/layout constraints
- asset rules
- responsive requirements
- "first artifact should prove..." acceptance notes
8. **Validate.** Read `references/checklist.md` and satisfy every P0 gate
before final handoff.
## Output rules
- Make every claim traceable to user input, observed reference evidence, or an
explicitly labeled inference.
- Prefer concrete constraints over adjectives: "one warm accent, no purple or
blue glow" beats "premium".
- Treat "do the same style" as "borrow controllable qualities", not "clone the
original subject or prompt".
- If the user asks for immediate UI generation too, finish these contract files
first, then hand off to the appropriate artifact skill in the next step.
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.