polish

Reviews and fixes alignment, spacing, typography, and interaction-state issues in UI work before shipping.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/metang/imganalyzer --skill polish-metang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/metang/imganalyzer/tree/main/.agents/skills/polish
Command: npx skills add https://github.com/metang/imganalyzer --skill polish-metang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finished features often ship with small visual and interaction defects—misaligned elements, inconsistent spacing, missing hover or focus states, and copy inconsistencies—that separate good work from great work. This Skill performs a systematic final quality pass to catch and fix those micro-detail issues before release. ## Core Features & Use Cases - Systematic polish dimensions: Works through alignment, spacing, typography, color contrast, interaction states, transitions, copy, icons, forms, edge cases, responsiveness, performance, and code quality. - Design system alignment: Discovers existing design tokens, component libraries, and conventions, then fixes drift such as hard-coded values or duplicated one-off components. - Structured checklist: Provides a concrete verification checklist covering WCAG contrast, 44px touch targets, keyboard navigation, reduced-motion support, and clean code. - Use Case: Before launching a new settings page, run a polish pass to fix a 13px off-scale gap, add missing focus indicators, replace hard-coded hex colors with design tokens, and remove leftover console.log statements. ## Quick Start Ask the AI to polish the target feature or page, for example by saying: run a final polish pass on the checkout flow before we ship it.

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 before shipping?▼

Run a systematic final pass covering alignment, spacing scale adherence, typography hierarchy, all interaction states, transitions, copy consistency, and edge cases. Verify against a checklist including WCAG contrast, keyboard navigation, and touch target sizes before marking the work done.

What should a pre-launch design review checklist include?▼

Include pixel-perfect alignment at all breakpoints, consistent design token usage, complete interaction states (hover, focus, active, disabled, loading, error), smooth 150-300ms transitions, 44x44px touch targets, WCAG AA contrast, visible focus indicators, and no console errors or layout shift.

When should I not polish a feature?▼

Do not polish work that is not functionally complete, since polish is the last step before shipping. Also triage effort against the deadline—if it ships in 30 minutes, prioritize critical issues rather than spending hours on micro-details.

How does polish work with an existing design system?▼

First discover the design system's tokens, spacing scale, and shared components, then identify drift such as hard-coded colors or one-off components duplicating shared ones. Polish aligns the feature back to the system rather than introducing new conventions.

Why does my UI feel off even though everything works?▼

Functional but unpolished UI usually has inconsistent spacing values, missing interaction states, misaligned elements, or mixed typography styles. A systematic pass checking each dimension against the design system conventions typically reveals the specific issues.