visual-iteration
UI feedback loop using screenshots. Provide design mock, implement, screenshot result, iterate until matching. Use for visual work.
What this skill does
# Visual Iteration Skill ## Trigger Use when implementing UI components, layouts, or any visual work where "looks right" matters. ## The Insight From Anthropic's Claude Code best practices: "Provide design mocks or screenshots. Have Claude implement, screenshot results, and iterate until matching the target. This gives Claude concrete feedback for refinement." ## Why This Works - Visual feedback is unambiguous - it either matches or it doesn't - Faster iteration than describing visual problems in words - Claude can see exactly what needs adjustment - Creates tight feedback loop for rapid convergence ## The Workflow ### Step 1: Provide the Target Give Claude a clear visual reference: ``` Here's the design mock for the new dashboard header: [drag and drop image or provide path] Implement this in React with Tailwind CSS. ``` Ways to provide visual targets: - Drag and drop images into the chat - Provide file paths to images - Share Figma export screenshots - Use URLs to design references ### Step 2: Initial Implementation Claude implements based on the visual reference. ### Step 3: Screenshot the Result Capture what Claude built: ```bash # Take screenshot of the running app # On macOS: Cmd+Shift+4 to select area # Or use browser DevTools device mode ``` ### Step 4: Compare and Iterate Share the screenshot back with Claude: ``` Here's what it looks like now: [screenshot of current implementation] Compare to the original design. The spacing between cards is too tight and the shadow is too harsh. Adjust to match the design more closely. ``` ### Step 5: Repeat Until Matching Continue the loop: 1. Claude adjusts 2. You screenshot 3. You compare 4. You provide feedback 5. Repeat until satisfied ## Effective Feedback Examples **Vague (less effective):** > "It doesn't look right" **Specific (more effective):** > "The button is 20px too far from the edge. The font weight should be semibold not bold. The border radius should match the card above it." **With visual reference:** > "See how in the design the cards have subtle shadows? Current implementation has no shadow. Add `shadow-sm` to match." ## Template for Visual Tasks ```markdown ## Visual Implementation Task ### Target Design [Image: design mock or reference screenshot] ### Technical Requirements - Framework: [React/Vue/etc] - Styling: [Tailwind/CSS modules/etc] - Responsive: [breakpoints to support] ### Key Visual Elements - [ ] [Element 1 - specific requirements] - [ ] [Element 2 - specific requirements] - [ ] [Color/spacing tokens to use] ### Iteration Process 1. Implement initial version 2. I'll screenshot and provide feedback 3. Iterate until matching design ``` ## Tips for Better Visual Iteration ### Provide Context - Include surrounding UI elements in screenshots - Show both light and dark mode if applicable - Include different viewport sizes ### Be Specific About Differences - "Too much padding" → "Reduce padding from 24px to 16px" - "Wrong color" → "Use gray-600 instead of gray-500" - "Alignment off" → "Left edge should align with the header above" ### Use Browser DevTools - Inspect computed styles to give exact values - Use device mode for responsive testing - Screenshot specific breakpoints ## When to Use This Skill - Implementing designs from Figma/Sketch - Matching existing UI patterns - Fixing visual bugs - Building responsive layouts - Polishing UI details before release
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.