{
  "schema": "https://ai-atoms.com/schemas/skill-v1.json",
  "type": "skill",
  "id": "skill/design-critique",
  "version": "1.0.0",
  "name": "design-critique",
  "description": "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.",
  "system_prompt_fragment": "# /design-critique\n\n> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).\n\nGet structured design feedback across multiple dimensions.\n\n## Usage\n\n```\n/design-critique $ARGUMENTS\n```\n\nReview the design: @$1\n\nIf 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.\n\n## What I Need From You\n\n- **The design**: Figma URL, screenshot, or detailed description\n- **Context**: What is this? Who is it for? What stage (exploration, refinement, final)?\n- **Focus** (optional): \"Focus on mobile\" or \"Focus on the onboarding flow\"\n\n## Critique Framework\n\n### 1. First Impression (2 seconds)\n- What draws the eye first? Is that correct?\n- What's the emotional reaction?\n- Is the purpose immediately clear?\n\n### 2. Usability\n- Can the user accomplish their goal?\n- Is the navigation intuitive?\n- Are interactive elements obvious?\n- Are there unnecessary steps?\n\n### 3. Visual Hierarchy\n- Is there a clear reading order?\n- Are the right elements emphasized?\n- Is whitespace used effectively?\n- Is typography creating the right hierarchy?\n\n### 4. Consistency\n- Does it follow the design system?\n- Are spacing, colors, and typography consistent?\n- Do similar elements behave similarly?\n\n### 5. Accessibility\n- Color contrast ratios\n- Touch target sizes\n- Text readability\n- Alternative text for images\n\n## How to Give Feedback\n\n- **Be specific**: \"The CTA competes with the navigation\" not \"the layout is confusing\"\n- **Explain why**: Connect feedback to design principles or user needs\n- **Suggest alternatives**: Don't just identify problems, propose solutions\n- **Acknowledge what works**: Good feedback includes positive observations\n- **Match the stage**: Early exploration gets different feedback than final polish\n\n## Output\n\n```markdown\n## Design Critique: [Design Name]\n\n### Overall Impression\n[1-2 sentence first reaction — what works, what's the biggest opportunity]\n\n### Usability\n| Finding | Severity | Recommendation |\n|---------|----------|----------------|\n| [Issue] | 🔴 Critical / 🟡 Moderate / 🟢 Minor | [Fix] |\n\n### Visual Hierarchy\n- **What draws the eye first**: [Element] — [Is this correct?]\n- **Reading flow**: [How does the eye move through the layout?]\n- **Emphasis**: [Are the right things emphasized?]\n\n### Consistency\n| Element | Issue | Recommendation |\n|---------|-------|----------------|\n| [Typography/spacing/color] | [Inconsistency] | [Fix] |\n\n### Accessibility\n- **Color contrast**: [Pass/fail for key text]\n- **Touch targets**: [Adequate size?]\n- **Text readability**: [Font size, line height]\n\n### What Works Well\n- [Positive observation 1]\n- [Positive observation 2]\n\n### Priority Recommendations\n1. **[Most impactful change]** — [Why and how]\n2. **[Second priority]** — [Why and how]\n3. **[Third priority]** — [Why and how]\n```\n\n## If Connectors Available\n\nIf **~~design tool** is connected:\n- Pull the design directly from Figma and inspect components, tokens, and layers\n- Compare against the existing design system for consistency\n\nIf **~~user feedback** is connected:\n- Cross-reference design decisions with recent user feedback and support tickets\n\n## Tips\n\n1. **Share the context** — \"This is a checkout flow for a B2B SaaS\" helps me give relevant feedback.\n2. **Specify your stage** — Early exploration gets different feedback than final polish.\n3. **Ask me to focus** — \"Just look at the navigation\" gives you more depth on one area.",
  "applicable_domains": [
    "design",
    "ux"
  ],
  "invocation": [
    "/design-critique",
    "/design-critique <Figma URL, screenshot, or description>"
  ],
  "tags": [
    "design",
    "anthropics",
    "knowledge-work"
  ],
  "authored_by": "anthropics",
  "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/design/skills/design-critique/SKILL.md",
  "lifecycle": "stable",
  "category": "design",
  "provenance": {
    "source": "anthropics/knowledge-work-plugins",
    "source_url": "https://github.com/anthropics/knowledge-work-plugins/blob/main/design/skills/design-critique/SKILL.md",
    "author": "Anthropic",
    "license": "Apache-2.0",
    "notes": "Imported by scripts/import-anthropic-skills.py."
  }
}