polish

Reviews frontend work for alignment, spacing, interaction states, and consistency issues before shipping.

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

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 erode perceived quality. This Skill provides a systematic final review pass to catch those details before release. ## Core Features & Use Cases - Systematic Quality Checklist: Walks through alignment, typography, color contrast, interaction states, micro-interactions, forms, responsiveness, and performance dimensions. - Design Token & Accessibility Enforcement: Verifies spacing uses design tokens, contrast meets WCAG standards, focus indicators are visible, and touch targets reach 44x44px. - Use Case: Before shipping a new settings page, run a polish pass to confirm every button has hover, focus, active, disabled, and loading states, spacing follows the grid at all breakpoints, and no console logs remain in the code. ## Quick Start Ask the AI to run a final polish pass on the current feature, checking alignment, interaction states, and accessibility 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 do a final UI quality check before shipping a feature?▼

Run a systematic polish pass covering alignment, spacing, typography, interaction states, and responsiveness. Verify every interactive element has hover, focus, active, disabled, and loading states, and test at mobile, tablet, and desktop breakpoints.

What should a frontend polish checklist include?▼

A polish checklist should cover pixel-perfect alignment, consistent spacing tokens, typography hierarchy, all interaction states, smooth 150-300ms transitions, WCAG contrast ratios, keyboard navigation, helpful empty and error states, and clean code without console logs.

When should I run a polish pass in the development workflow?▼

Polish is the last step, only after the feature is functionally complete. Polishing incomplete work wastes effort, and the amount of polish should match the quality bar—an MVP shipping in 30 minutes needs triage, not hours of refinement.

What accessibility requirements does a UI polish pass check?▼

It verifies text contrast meets WCAG standards, focus indicators are visible with sufficient contrast, keyboard navigation and tab order work logically, touch targets are at least 44x44px, and animations respect the prefers-reduced-motion setting.

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

The cause is usually small inconsistencies: random spacing values instead of a spacing scale, missing hover or focus states, mixed icon styles, or inconsistent capitalization in copy. A systematic dimension-by-dimension review surfaces these issues.