Update to Build MCP Apps & Agents

{
  "description": "Review and improve the actual visual design, usability, accessibility and interaction states of an MCP App UI using the curated design reference library.",
  "included_files": [],
  "name": "review-mcp-design",
  "skill_md_contents": "---\nname: review-mcp-design\ndescription: Review and improve the actual visual design, usability, accessibility and interaction states of an MCP App UI using the curated design reference library.\n---\n# MCP App design review\n\nUse when users want a more polished, less generic UI, show a reference website/screenshot, or request UX criticism. UI must remain suitable for the AI host iframe and task context.\n\n1. Get the actual implementation and rendered UI or screenshot (not just component names). Capture the desired product personality and the main task.\n2. Read `../../references/design-references.md` and `../../references/design-quality.md`. Curate only sources relevant to the case; verify external licenses.\n3. Evaluate hierarchy, copy, typography, spacing, affordances, information density, contrast, keyboard use, reduced motion, narrow container, dark-mode legibility, and loading/empty/error/permission/success states.\n4. Find specifically reproducible problems, not abstract advice. For requested implementation, modify code with small, scoped changes while preserving tool contracts and actual event handlers.\n5. Inspect the rendered result again when tools permit. Do not fabricate screenshot evidence or claim accessibility certification based on appearance alone.\n6. Report substantive fixes, measured checks, and limitations; prefer an individual design direction over default purple gradients, stacked generic cards and irrelevant motion.\n"
}