polish

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

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

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 hard-coded values that drift from the design system. This Skill performs a systematic final quality pass to catch those details before release. ## Core Features & Use Cases - Design System Alignment: Discovers existing design tokens, spacing scales, and shared components, then identifies where the target feature deviates from them. - Systematic Multi-Dimension Review: Works through alignment, typography, color contrast, interaction states, micro-interactions, copy, icons, forms, edge cases, responsiveness, performance, and code quality with an explicit checklist. - Use Case: Before launching a new settings page, run a polish pass to verify all buttons have hover/focus/disabled states, spacing uses design tokens, touch targets meet 44x44px, and no console.log statements remain. ## Quick Start Ask the AI to polish the settings page before launch and fix any alignment, spacing, and interaction state issues it finds.

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 review across alignment, spacing, typography, interaction states, and responsiveness after the feature is functionally complete. Verify every interactive element has hover, focus, active, disabled, loading, and error states, and confirm spacing uses design tokens rather than arbitrary values.

What should a pre-launch design review checklist include?

Cover visual alignment at all breakpoints, consistent spacing tokens, typography hierarchy, all interaction states, smooth 60fps transitions, WCAG AA contrast ratios, 44x44px touch targets, keyboard navigation, visible focus indicators, and clean code with no console logs or commented-out blocks.

When should I not run a polish pass?

Skip polish when the feature is not functionally complete, since polish is the last step before shipping. Also triage scope when time is extremely limited, and fix systemic issues at the design system level rather than patching individual instances.

Does the polish skill work without an existing design system?

Yes. If no design system documentation exists, it polishes against the conventions visible in the codebase, such as established spacing patterns, color usage, and shared component imports. When a system does exist, it aligns the feature to those tokens and components.

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

Residual issues are usually micro-details: optical misalignment of icons, inconsistent easing curves, missing focus indicators, hard-coded colors instead of tokens, or widows in text. A structured polish pass across all dimensions catches these systematically.