polish

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

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

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 rough copy—that erode perceived quality. This Skill performs a systematic final quality pass to catch and fix those details before release. ## Core Features & Use Cases - Systematic UI Audit: Works through alignment, spacing, typography, color contrast, interaction states, transitions, forms, and responsiveness using a structured checklist. - Edge Case & State Coverage: Verifies loading, empty, error, and success states, plus keyboard navigation, focus indicators, and WCAG contrast compliance. - Code Hygiene Pass: Removes console logs, dead code, unused imports, and TypeScript any types before shipping. - Use Case: Before releasing a new order dashboard, run a polish pass to fix inconsistent spacing, add missing button hover states, and verify the layout holds at mobile breakpoints. ## Quick Start Ask the AI to run a polish pass on the checkout page before it ships.

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 pass over alignment, spacing, typography, color contrast, and interaction states using a checklist. Verify all breakpoints, test keyboard navigation, and confirm loading, empty, and error states exist before release.

What should a frontend polish checklist include?▼

Cover visual alignment, consistent spacing tokens, typography hierarchy, all interaction states (hover, focus, active, disabled, loading), smooth 60fps transitions, WCAG contrast ratios, 44px touch targets, and clean code with no console logs or unused imports.

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

Polish only after the feature is functionally complete, since it is the last step before shipping. Triage based on time available—if it ships in 30 minutes, prioritize critical issues rather than perfecting every detail.

Does this polish process check accessibility?▼

Yes, it verifies WCAG contrast ratios, visible focus indicators, keyboard navigation and tab order, ARIA labels, semantic HTML, alt text on images, and respect for the prefers-reduced-motion setting.

What are common mistakes when polishing UI?▼

Common mistakes include polishing incomplete work, introducing bugs while tweaking, fixing one-off spacing instead of the underlying system, and perfecting one area while leaving others rough. Always test thoroughly after changes.