Product ux flow review
Skill yangshu2087/Codex/.agents/skills/product-ux-flow-review
Meta workspace for Codex configuration, shared skills, and maintenance scripts.
npx -y skills add yangshu2087/Codex --skill product-ux-flow-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when a task involves user experience, product flow, onboarding, conversion, user journeys, friction points, or UI acceptance criteria.
SKILL.md
2.1 KB, as published. Nobody here has run it
Product UX Flow Review
Use this skill when the product outcome depends on whether a real user can understand and complete the flow.
Required inputs
- User goal, business goal, and business rules
- Primary user path and secondary/failure states
- Current screen, flow, screenshot, prototype, or acceptance artifact
- Known constraints, non-goals, edge cases, and friction points
- Design system, copy tone, accessibility expectations, and state coverage needs
Workflow
- Rewrite the request into a product contract before implementation: user goal, business rules, constraints, non-goals, assumptions, edge cases, acceptance criteria, verification method, and open questions.
- Identify the primary journey, 2-3 failure/friction paths, and the point where users can get stuck.
- Cover states when relevant: default, hover, focus-visible, active, loading, empty, error, disabled, and success.
- Check copy for orientation, action clarity, recovery guidance, and unnecessary friction.
- Keep accessibility in scope: semantic structure, keyboard reachability, visible focus, contrast, and tap targets.
- Use repository components and tokens; do not invent a new design language without a requirement.
- Verify in a real browser, screenshot, Playwright, agent-browser, accessibility/state check, or manual page check before claiming completion.
Evidence requirements
- Product contract
- UX flow / user journey
- Friction or failure paths
- State coverage
- Copy and accessibility notes
- Browser, screenshot, accessibility/state evidence, or explicit blocker
Output standard
- Product contract
- Primary and secondary flows
- State coverage
- Copy / accessibility notes
- Browser or visual verification evidence
- Remaining UX risks
Common mistakes
- Optimizing UI aesthetics while ignoring the user's next action.
- Skipping empty/error/disabled states.
- Claiming UX quality without checking a real page or screenshot.
- Hiding poor copy or unclear flow behind visual polish.