polish

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

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ssrrb/cerramos-codebase --skill polish-ssrrb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/Ssrrb/cerramos-codebase/tree/main/.codex/skills/polish
Command: npx skills add https://github.com/Ssrrb/cerramos-codebase --skill polish-ssrrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Frontend work often ships with small visual and interaction defects—misaligned elements, inconsistent spacing, missing hover or focus states, and uneven copy—that degrade perceived quality. This Skill provides a systematic final-pass checklist 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. - Edge Case & Code Hygiene Audit: Covers empty states, long content, touch targets, reduced motion, console logs, dead code, and accessibility. - Use Case: Before shipping a new checkout page, run a polish pass to confirm spacing uses design tokens, all buttons have loading states, contrast meets WCAG AA, and no layout shift occurs on load. ## Quick Start Ask the AI to run a final polish pass on the current feature, checking alignment, interaction states, and accessibility before shipping.

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

Run a systematic polish pass covering alignment, spacing tokens, typography hierarchy, interaction states, and accessibility. Verify all breakpoints, test keyboard navigation, and confirm no console errors or layout shifts remain before release.

What interaction states should every button have?▼

Every interactive element needs default, hover, focus, active, disabled, loading, error, and success states. Missing states create confusion and broken experiences, especially for keyboard users who rely on visible focus indicators.

When should I not run a polish pass on frontend work?▼

Do not polish work that is not functionally complete, since polish is the last step. Also triage when shipping is imminent—spending hours on polish minutes before release risks introducing bugs.

Does this polish checklist cover accessibility requirements?▼

Yes, it checks WCAG contrast ratios, visible focus indicators, keyboard navigation, touch targets of at least 44x44px, ARIA labels, semantic HTML, and respect for the prefers-reduced-motion setting.

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

The cause is usually small inconsistencies: random spacing values outside the design scale, mixed icon styles, inconsistent capitalization, or missing transitions. A systematic polish pass identifies and fixes these accumulated details.