polish

Reviews and fixes alignment, spacing, interaction states, and consistency issues before shipping UI work.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/po4yka/blog --skill polish-po4yka
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/po4yka/blog/tree/main/.agents/skills/polish
Command: npx skills add https://github.com/po4yka/blog --skill polish-po4yka

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 uneven copy—that make work feel unrefined. This Skill provides a systematic final quality pass to catch and fix those details before release. ## Core Features & Use Cases - Systematic Visual Review: Checks alignment, spacing tokens, typography hierarchy, color contrast, and theme consistency across breakpoints. - Interaction State Coverage: Verifies every interactive element has default, hover, focus, active, disabled, loading, error, and success states with smooth 60fps transitions. - Edge Case & Code Hygiene Audit: Confirms loading, empty, and error states exist, touch targets meet 44x44px, and code is free of console logs, dead code, and type errors. - Use Case: Before launching a new settings page, run a polish pass to catch a missing focus indicator, a 13px off-grid gap, and an unhandled empty state in one structured review. ## Quick Start Ask the AI to run a polish pass on the current feature or page before shipping it.

Frequently Asked Questions about polish

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

FAQPage Schema
How do I do a final UI quality review before shipping?

Run a structured polish pass covering alignment, spacing tokens, typography, interaction states, and edge cases. Work through each dimension systematically, test at multiple breakpoints, and verify all states including loading, empty, and error before marking the work done.

What should a pre-launch design QA checklist include?

Include visual alignment at all breakpoints, consistent spacing tokens, complete interaction states (hover, focus, active, disabled, loading, error), WCAG contrast ratios, 44x44px touch targets, keyboard navigation, and clean code with no console logs or dead code.

When should I polish a feature versus ship it as-is?

Polish only after the feature is functionally complete, and triage based on time available. If shipping in 30 minutes, skip deep polish; if spacing is off everywhere, fix the underlying system rather than individual instances.

Why does my UI feel off even though everything works?

Functional but unpolished UI usually has inconsistent spacing values, missing interaction states, mixed typography scales, or hard-coded colors instead of design tokens. A systematic pass comparing elements against the design system typically reveals the source.

What are the limitations of a final polish pass?

Polish cannot fix incomplete functionality or systemic design flaws, and over-polishing one area while others stay rough creates inconsistent quality. It also risks introducing bugs, so thorough testing after changes is required.