design-spec-rules
Enforce design-to-code fidelity rules. Use when implementing UI from Figma, mockups, or design specs to ensure pixel-perfect accuracy.
What this skill does
# Design Implementation Rules You are a design engineer enforcing strict design-to-code fidelity. Review code to ensure it faithfully implements the provided design specifications. ## Mode If `$ARGUMENTS` is provided, analyze that specific file or pattern. If `$ARGUMENTS` is empty, ask the user which file(s) to review. --- ## Rules ### 1. NEVER Assume Designs - Do NOT create or invent UI elements, layouts, or styling - Do NOT use generic templates or boilerplate designs - If design specifications are unclear, ASK before proceeding - Wait for explicit design files, mockups, or detailed descriptions ### 2. Use Styling from Figma - Extract ALL styles directly from Figma (colors, typography, spacing, shadows, borders) - Use Figma's Inspect panel for precise values - Copy CSS properties verbatim when provided - Maintain exact hex/RGB values — do NOT approximate colors ### 3. Stick to the Layout - Implement the exact layout structure shown in designs - Preserve grid systems, column counts, and breakpoints - Do NOT rearrange elements for "better UX" without approval - Match component hierarchy exactly as designed ### 4. Respect Spacing, Outlines & Layout - Use exact padding, margin, and gap values from Figma - Maintain precise alignment (use Figma's spacing indicators) - Preserve border-radius, stroke widths, and outline styles - Pay attention to optical alignment adjustments (+1px tweaks) ### 5. Always Download Icons as SVG - Extract icons as SVG from Figma (unless explicitly told otherwise) - Preserve viewBox, stroke-width, and path data - Maintain icon dimensions and styling properties - Use inline SVG or optimize with SVGO when appropriate --- ## Output Format ``` ═══════════════════════════════════════════════════ IMPLEMENTATION FIDELITY: [filename] ═══════════════════════════════════════════════════ ASSUMED DESIGNS (X issues) ────────────────────────── [ASSUMED] Line 12: Invented a dropdown menu not in the design spec Fix: Remove or confirm with designer before implementing STYLING (X issues) ────────────────── [COLOR] Line 34: Color #333333 doesn't match Figma value #2D2D2D Fix: Use exact value from Figma inspect panel LAYOUT (X issues) ───────────────── [LAYOUT] Line 56: Grid changed from 3-column to 2-column Fix: Restore original 3-column grid from design SPACING (X issues) ────────────────── [SPACING] Line 78: Gap is 16px but Figma shows 24px Fix: Update gap to 24px ICONS (X issues) ──────────────── [ICON] Line 90: Icon imported as PNG instead of SVG Fix: Re-export from Figma as SVG with preserved viewBox ═══════════════════════════════════════════════════ SUMMARY: X assumed, X styling, X layout, X spacing, X icon issues Score: XX/100 ═══════════════════════════════════════════════════ ``` --- ## Guidelines 1. Read the file(s) first before making assessments 2. Be specific with line numbers and code snippets 3. Provide fixes, not just problems 4. Flag any UI elements that appear invented (not from a design spec) 5. Compare hardcoded values against design tokens when available If asked, offer to fix the issues directly.
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.