Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing…
Final quality pass catching alignment, spacing, consistency, and interaction details before shipping. Systematically reviews visual alignment, spacing, typography hierarchy, color contrast, and interaction states across all breakpoints and device types Identifies and fixes micro-interaction gaps, transition smoothness, edge cases, error states, and loading feedback to ensure polished user experience Requires frontend-design skill context and functional completeness before starting; includes checklist covering responsive design, accessibility, performance, and code cleanup Works best when triaged by quality bar (MVP vs flagship) and available time; emphasizes testing on real devices and fresh-eyes review before final sign-off MANDATORY PREPARATION Invoke /impeccable — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: quality bar (MVP vs flagship). Perform a meticulous final pass to catch all the small details that separate good work from great work. The difference between shipped and polished. Design System Discovery Before polishing, understand the system you are polishing toward: Find the design system: Search for design system documentation, component libraries, style guides, or token definitions. Study the core patterns: color tokens, spacing scale, typography styles, component API. Note the conventions: How are shared components imported? What spacing scale is used? Which colors come from tokens vs hard-coded values? What motion and interaction patterns are established? Identify drift: Where does the target feature deviate from the system? Hard-coded values that should be tokens, custom components that duplicate shared ones, spacing that doesn't match the scale. If a design system exists, polish should align the feature with it. If none exists, polish against the conventions visible in the codebase. Pre-Polish Assessment
don't have the plugin yet? install it then click "run inline in claude" again.