polish

Reviews and fixes alignment, spacing, consistency, and interaction details in UI features before release.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill polish-ivaylo91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/ivaylo91/Shopping-Mobile-App/tree/main/.agents/skills/polish
Command: npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill polish-ivaylo91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished features often ship with small visual and interaction defects—misaligned elements, inconsistent spacing, missing hover states, hard-coded colors—that erode perceived quality. This Skill performs a systematic final quality pass to catch and fix those micro-detail issues before launch. ## Core Features & Use Cases - Systematic UI Review: Works through alignment, typography, color tokens, interaction states, transitions, copy, icons, forms, and responsiveness using a structured checklist. - Design System Alignment: Detects drift from the project's design system, replacing hard-coded values with tokens and custom components with shared ones. - Accessibility & Edge Cases: Verifies WCAG contrast ratios, keyboard navigation, focus indicators, loading/empty/error states, and reduced-motion support. - Use Case: Before shipping a new settings page, run a polish pass to fix inconsistent spacing, add missing focus states, align colors to design tokens, and clean up leftover console logs. ## Quick Start Ask the assistant to polish the target feature or page, for example by saying: run a final polish pass on the checkout flow before release.

Frequently Asked Questions about polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I polish a UI feature before launch?

Run a systematic final pass covering alignment, spacing scale adherence, typography hierarchy, interaction states, and responsive behavior. Verify contrast ratios meet WCAG standards, test keyboard navigation, and remove debug code before shipping.

What should a pre-launch design review checklist include?

Include visual alignment at all breakpoints, consistent design token usage, all interactive states (hover, focus, active, disabled, loading, error), smooth 60fps transitions, 44x44px touch targets, and clean code without console logs or commented-out blocks.

When should I not run a polish pass on a feature?

Do not polish work that is not functionally complete, since polish is the last step. Also triage scope when shipping imminently, and fix systematic issues at the design system level rather than patching individual instances.

How does polish work with an existing design system?

The pass first discovers the design system's tokens, spacing scale, and shared components, then identifies drift such as hard-coded colors or duplicated components. Fixes align the feature to the system rather than introducing one-off values.

Why does my UI still look off after fixing obvious bugs?

Residual issues are usually micro-details: spacing values outside the scale, missing optical alignment for icons, inconsistent easing curves, or gray text on colored backgrounds. A structured checklist across typography, color, and motion catches these systematically.