agent init
This commit is contained in:
45
skills/ui-ux/ux-review.md
Normal file
45
skills/ui-ux/ux-review.md
Normal file
@@ -0,0 +1,45 @@
|
||||
# UX Review
|
||||
|
||||
## Purpose
|
||||
|
||||
Evaluate an interface or flow for clarity, usability, friction, trust, and task completion quality, then turn those observations into actionable improvements.
|
||||
|
||||
## When to use
|
||||
|
||||
- Reviewing a screen or flow before or after implementation
|
||||
- Looking for usability issues in forms, navigation, settings, or onboarding
|
||||
- Improving hierarchy, copy clarity, state handling, or feedback
|
||||
- Assessing whether an interface supports the intended user goal well
|
||||
|
||||
## Inputs to gather
|
||||
|
||||
- Screens, flows, components, or descriptions of the experience
|
||||
- Target user goal and success criteria
|
||||
- Existing design system or product patterns
|
||||
- Constraints such as device, context, accessibility, or content requirements
|
||||
|
||||
## How to work
|
||||
|
||||
- Review from the user's task perspective rather than from the component tree outward.
|
||||
- Check whether the next action is obvious at each step.
|
||||
- Evaluate hierarchy, wording, spacing, feedback, and state transitions together.
|
||||
- Prioritize issues by how much they block comprehension, confidence, or completion.
|
||||
- Suggest improvements that fit the current product language unless redesign is requested.
|
||||
|
||||
## Output expectations
|
||||
|
||||
- Clear list of UX issues or strengths
|
||||
- Prioritized recommendations with rationale
|
||||
- Notes on where UI changes, copy changes, or research would help most
|
||||
|
||||
## Quality checklist
|
||||
|
||||
- Feedback is tied to user outcomes, not vague aesthetic preference.
|
||||
- Important states such as empty, loading, error, and success are considered.
|
||||
- Recommendations are specific enough to act on.
|
||||
- Suggestions fit the product's current level of complexity and style.
|
||||
|
||||
## Handoff notes
|
||||
|
||||
- Distinguish between usability issues, visual polish issues, and copy issues.
|
||||
- Pair with frontend implementation or product copy when turning review into shipped changes.
|
||||
Reference in New Issue
Block a user