ui-ux-pro-max
ui-ux-pro-max
Use the design system as the shared rules for tokens, components, and interactions. Reuse the project's system for maintenance and review. Generate recommendations only when a system is missing or the user requests a new direction.
Under design-gate, use the caller's canonical gate result. This replaces standalone output and edit mechanics. Carry lens-specific conclusions in findings or review_focus, with stable finding IDs. In an interview, contribute decision fields to the existing decision record.
Select the work
- Review an existing interface: Compare the affected screens and interactions with the selected system. Return findings without editing unless the user requests fixes. A database search is optional.
- Implement within a chosen system: Apply its tokens, components, and interaction rules to the requested change. Reuse settled decisions. Search only for details that could change the implementation.
- Create or save a new system: Read references/search-reference.md for generation and persistence commands. Use the product, industry, style, and user requirements as search inputs.
- Resolve a specific design question: Read references/search-reference.md for domain or stack searches. Load it only when a lookup or its visual examples can help the task.
Use the existing project stack or the user's selection. Use html-tailwind only for a new artifact with no selected stack.
Use frontend-design for bespoke visual implementation. Use advanced-react to review component rendering, memoization, context updates, stale closures, or fetch races. This skill's react domain supplies reference data for that review.