ui-ux-pro
Design or review product interaction flows, information structure, interface states and usable task completion.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-11
- Stars
- ★ 10
- Forks
- 1
01 前言 Front Matter
- name
- ui-ux-pro
- description
- Design or review product interaction flows, information structure, interface states and usable task completion.
02 资源文件 4
- 参考文档EXAMPLES.md581 B
- 参考文档skill.yaml417 B
- 参考文档TROUBLESHOOTING.md318 B
- 参考文档VALIDATION.json198 B
03 SKILL.md 正文
ui-ux-pro
Overview
Design or review product interaction flows, information structure, interface states and usable task completion. Match guidance to the actual task and project; this document does not implement an automatic enforcer.
When to Use
A product flow, form, navigation, onboarding or information-architecture problem needs design work. Use frontend-design for visual composition and a requested style pack for a specific aesthetic.
Rules & Patterns
Identify the user's goal, relevant content, constraints and current workflow. Preserve useful product behavior and distinguish observed user evidence from assumptions.
Make actions, navigation, labels and state transitions understandable. Match vocabulary to the user's task and keep names consistent across controls, feedback and recovery.
Design loading, empty, invalid, denied and success states where the flow needs them. Preserve entered data for recoverable failures, prevent unintended duplicate actions, and offer confirmation or undo where the actual operation warrants it.
Respect the brand, component system, typography and platform conventions. Fonts, pure colors, native controls and particular easing curves are not universally prohibited.
Check keyboard/touch access, focus, content reflow and reduced-motion behavior. A style checklist or screenshot does not establish usability research or accessibility certification.
Code Examples
For a multi-step application form, keep progress and recovery clear, preserve input after a failed save and distinguish optional onboarding from required legal/security steps. Do not make every step skippable by default.
See EXAMPLES.md for scoped scenarios and evidence boundaries.
Validation Checklist
- [ ] Exercise the primary task and important recovery paths.
- [ ] Check actual content, navigation, focus and responsive states.
Common Mistakes
Replacing UX with font bans; inventing user research; removing required steps to simplify the flow; confusing visual polish with task success.
Integration Notes
Optional companion guidance: frontend-design, web-design-guidelines, webapp-testing. Use it only when relevant and available; the skill does not install tools or authorize external actions.
04 同仓库更多 Skills
scoped-frontend
Frontend component design and React guidelines
scoped-backend
Backend service architecture and API endpoints
engineering-workflow
Core software engineering lifecycle workflow
team-auth
ContextOS skill for team-auth
claude
暂无简介
team-order
Team conventions for createOrder and item name normalization in src/order.ts.