UX Polish Skill
WorkflowSkills Project Context
Before acting, resolve project documentation roots:
- Look for a
[DOC]-*directory at project root. - If found, set
DOC_ROOTto that directory andUX_DOCS_ROOTto[DOC]-*/11-UX-DesignOps. - If
[DOC]-*is absent, stop and ask to initialize project documentation first; never write persistent UX documentation todocs/obsidian. - Read
DESIGN.md, related UX docs, and current code.
Goal
Improve visual quality, clarity, interaction feedback, and consistency without changing business behavior.
Process
- Identify the target surface and current issue.
- Read components, tokens, CSS variables, Tailwind config, theme files, and Storybook if present.
- Make focused changes to spacing, hierarchy, alignment, states, typography, contrast, and motion.
- Preserve behavior, data flow, APIs, validation, and routing.
- Update
UX_DOCS_ROOT/09-Debt/Visual_Debt.mdand related screen/component docs. - Run or trigger
ux-visual-verification.
Rules
- Keep changes small and reviewable.
- Use existing tokens and components.
- Do not create one-off styling unless documented as a deliberate exception.
- Do not use generic AI visual patterns without product rationale.
- Visual verification is mandatory for UI changes.