polish

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

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

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 provides a systematic final quality pass to catch those details before launch. ## Core Features & Use Cases - Systematic Polish Dimensions: Works through alignment, typography, color contrast, interaction states, micro-interactions, copy, icons, forms, edge cases, responsiveness, performance, and code quality. - Design System Alignment: Discovers existing design tokens, spacing scales, and shared components, then fixes drift such as hard-coded values or duplicated components. - Comprehensive Checklist: Provides a concrete pre-ship checklist covering WCAG contrast, 44px touch targets, keyboard navigation, reduced motion, and clean code. - Use Case: Before launching a new settings page, run a polish pass to verify every button has hover/focus/disabled states, spacing matches the design token scale, and no console logs remain in the code. ## Quick Start Ask the AI to polish the settings page before launch, checking alignment, spacing, interaction states, and accessibility against the design system.

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 launch?

Run a systematic pass over alignment, spacing, typography, interaction states, and copy, verifying each against your design system tokens. Test at multiple breakpoints, check keyboard navigation and focus indicators, and confirm all async actions have loading and error states.

What should a pre-launch design review checklist include?

Include pixel-perfect alignment at all breakpoints, consistent spacing tokens, complete interaction states (hover, focus, active, disabled, loading, error), WCAG AA contrast, 44px touch targets, smooth 60fps transitions, and clean code with no console logs or dead code.

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 deadlines—if something ships in 30 minutes, prioritize critical issues over exhaustive refinement.

How do I fix inconsistent spacing in a web app?

Identify the design system's spacing scale and replace hard-coded pixel values with the corresponding tokens. Look for drift where features deviate from shared components, and fix systematic issues at the system level rather than one element at a time.

Why do missing interaction states cause problems?

Missing hover, focus, loading, or error states leave users without feedback, creating confusion and broken experiences. Every interactive element needs all states implemented, including visible keyboard focus indicators and async loading feedback.