Review product design plans for missing UX decisions and interaction states.
npx skills add https://github.com/MFS-code/gstack --skill plan-design-review-mfs-code
Please help me install this Agent Skill. Skill: plan-design-review Source: https://github.com/MFS-code/gstack/tree/main/plan-design-review Command: npx skills add https://github.com/MFS-code/gstack --skill plan-design-review-mfs-code
It helps you catch missing or ambiguous design decisions in a product plan before any UI is built, so the implementation doesn’t ship as accidental, inconsistent, or incomplete user experience.
Invoke this skill when you want a rigorous design critique of your PLAN: ask the AI to “review my design plan with /plan-design-review and improve the plan’s missing UX decisions.”
High-intent search queries and answers about installing and using this skill.
Review a product design plan by applying designer-level rigor to identify missing UX decisions and user experience gaps. Catching incomplete interaction states, accessibility issues, and edge cases before UI implementation prevents shipping accidental or inconsistent user experiences.
A UX audit for a design plan evaluates information hierarchy to ensure users see content in the intended order. It identifies gaps in visual priority and flags missing empty, loading, error, success, and partial interaction states to produce a more complete, specific plan.
Check a design plan for edge case coverage and accessibility by enforcing specific requirements during a structured review. Treating edge cases as core UX and pushing for concrete, non-generic UI decisions ensures the final plan handles all user scenarios without relying on generic AI-slop.
Yes, you can use a guided question-and-fix workflow to improve a product design plan. This interactive clarification process applies prioritized design rules to systematically identify and resolve ambiguous UX decisions, ensuring the output is specific enough to implement.
You need a design plan critique when you want to catch missing or ambiguous design decisions before any UI is built. Reviewing the PLAN rather than a live page ensures the user experience is intentional, complete, and specific enough for developers to implement without accidental gaps.
SHUAXINDIARYAnalyze UI designs and produce simplified outlines preserving core actions.
nand1234Generate a structured ticket plan with dependencies from requirements documents.
eboodyAudit UI designs for visual hierarchy, spacing, typography, and design-system consistency.
dachentValidate frontend UI components through browser rendering and screenshot analysis.
