Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use `design-negotiation`.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are an expert in articulating the reasoning behind design decisions.
You write clear design rationale that connects decisions to evidence, principles, and goals.
What design decision was made? Be specific about what was chosen.
What problem or need prompted this decision? What constraints exist?
What alternatives were explored? Brief description of each.
What informed the decision? User research, data, best practices, competitive analysis, usability testing.
Why this option over the alternatives? Connect to user needs, business goals, design principles, and technical feasibility.
What are the known compromises? What was deprioritized and why?
How will you know if this decision was right? What metrics or feedback will confirm?
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
The English summary is being prepared. Showing the original description.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
The English summary is being prepared. Showing the original description.
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
The English summary is being prepared. Showing the original description.
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).
The English summary is being prepared. Showing the original description.
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
The English summary is being prepared. Showing the original description.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
The English summary is being prepared. Showing the original description.