UI polish
Apply the user's requested changes in the project's existing component and styling system. Preserve established tokens, density, icon language, and intentional design choices. Treat the examples in this skill as defaults, not mandatory exact values.
Focused principles
- Use optical alignment where geometric centering visibly fails. Coordinate nested radii with padding and the existing shape system.
- Use borders for structure or state and shadows for elevation when that matches the project. Image outlines are optional, theme-aware treatments rather than a universal requirement.
- Match icon weight and state treatment to the existing set. Reuse assets and
currentColor where appropriate; distinct icons can express genuinely different states.
- Give actions clear, timely feedback without adding distracting motion. Preserve state cues when animation is disabled.
For motion, use motion.md as the shared source for authoring and review. Read a recipe only for the interaction being changed; it does not override project conventions.
Domain ownership
Consult only the owners relevant to the task:
- Typography: wrapping, type scale, font rendering, numeric alignment.
- Accessibility: names, keyboard/focus, hit areas, semantic behavior.
- Layout: grouping, spatial relationships, responsive layout.
- Colors: tokens and contrast.
- Writing: product copy; consult when building marketing or landing pages.
Do not load every owner for a focused polish change.
Complete the requested work
For implementation, edit the relevant surface, inspect affected states when available, run appropriate checks, and fix failures caused by the change. For review, remain read-only and report supported problems by impact with source evidence and the smallest correction. Optional style preferences are suggestions, not blockers. State actual coverage and unverified checks; no findings is a valid result.
1---2name: better-ui3description: "Implement or review focused UI polish using the project’s design system. Use for alignment, surfaces, icons, or interaction detail."4metadata:5 source: https://skillmd.com/skills/transitive-bullshit/better-ui6---78# UI polish910Apply the user's requested changes in the project's existing component and styling system. Preserve established tokens, density, icon language, and intentional design choices. Treat the examples in this skill as defaults, not mandatory exact values.1112## Focused principles1314- Use optical alignment where geometric centering visibly fails. Coordinate nested radii with padding and the existing shape system.15- Use borders for structure or state and shadows for elevation when that matches the project. Image outlines are optional, theme-aware treatments rather than a universal requirement.16- Match icon weight and state treatment to the existing set. Reuse assets and `currentColor` where appropriate; distinct icons can express genuinely different states.17- Give actions clear, timely feedback without adding distracting motion. Preserve state cues when animation is disabled.1819For motion, use [motion.md](motion.md) as the shared source for authoring and review. Read a recipe only for the interaction being changed; it does not override project conventions.2021## Domain ownership2223Consult only the owners relevant to the task:2425- [Typography](../better-typography/SKILL.md): wrapping, type scale, font rendering, numeric alignment.26- [Accessibility](../better-accessibility/SKILL.md): names, keyboard/focus, hit areas, semantic behavior.27- [Layout](../better-layout/SKILL.md): grouping, spatial relationships, responsive layout.28- [Colors](../better-colors/SKILL.md): tokens and contrast.29- [Writing](../better-writing/SKILL.md): product copy; consult when building marketing or landing pages.3031Do not load every owner for a focused polish change.3233## Complete the requested work3435For implementation, edit the relevant surface, inspect affected states when available, run appropriate checks, and fix failures caused by the change. For review, remain read-only and report supported problems by impact with source evidence and the smallest correction. Optional style preferences are suggestions, not blockers. State actual coverage and unverified checks; no findings is a valid result.