design-critique
Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.
What this skill does
# /design-critique > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Get structured design feedback across multiple dimensions. ## Usage ``` /design-critique $ARGUMENTS ``` Review the design: @$1 If a Figma URL is provided, pull the design from Figma. If a file is referenced, read it. Otherwise, ask the user to describe or share their design. ## What I Need From You - **The design**: Figma URL, screenshot, or detailed description - **Context**: What is this? Who is it for? What stage (exploration, refinement, final)? - **Focus** (optional): "Focus on mobile" or "Focus on the onboarding flow" ## Critique Framework ### 1. First Impression (2 seconds) - What draws the eye first? Is that correct? - What's the emotional reaction? - Is the purpose immediately clear? ### 2. Usability - Can the user accomplish their goal? - Is the navigation intuitive? - Are interactive elements obvious? - Are there unnecessary steps? ### 3. Visual Hierarchy - Is there a clear reading order? - Are the right elements emphasized? - Is whitespace used effectively? - Is typography creating the right hierarchy? ### 4. Consistency - Does it follow the design system? - Are spacing, colors, and typography consistent? - Do similar elements behave similarly? ### 5. Accessibility - Color contrast ratios - Touch target sizes - Text readability - Alternative text for images ## How to Give Feedback - **Be specific**: "The CTA competes with the navigation" not "the layout is confusing" - **Explain why**: Connect feedback to design principles or user needs - **Suggest alternatives**: Don't just identify problems, propose solutions - **Acknowledge what works**: Good feedback includes positive observations - **Match the stage**: Early exploration gets different feedback than final polish ## Output ```markdown ## Design Critique: [Design Name] ### Overall Impression [1-2 sentence first reaction — what works, what's the biggest opportunity] ### Usability | Finding | Severity | Recommendation | |---------|----------|----------------| | [Issue] | 🔴 Critical / 🟡 Moderate / 🟢 Minor | [Fix] | ### Visual Hierarchy - **What draws the eye first**: [Element] — [Is this correct?] - **Reading flow**: [How does the eye move through the layout?] - **Emphasis**: [Are the right things emphasized?] ### Consistency | Element | Issue | Recommendation | |---------|-------|----------------| | [Typography/spacing/color] | [Inconsistency] | [Fix] | ### Accessibility - **Color contrast**: [Pass/fail for key text] - **Touch targets**: [Adequate size?] - **Text readability**: [Font size, line height] ### What Works Well - [Positive observation 1] - [Positive observation 2] ### Priority Recommendations 1. **[Most impactful change]** — [Why and how] 2. **[Second priority]** — [Why and how] 3. **[Third priority]** — [Why and how] ``` ## If Connectors Available If **~~design tool** is connected: - Pull the design directly from Figma and inspect components, tokens, and layers - Compare against the existing design system for consistency If **~~user feedback** is connected: - Cross-reference design decisions with recent user feedback and support tickets ## Tips 1. **Share the context** — "This is a checkout flow for a B2B SaaS" helps me give relevant feedback. 2. **Specify your stage** — Early exploration gets different feedback than final polish. 3. **Ask me to focus** — "Just look at the navigation" gives you more depth on one area.
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.