polish

Review UI/UX features for visual alignment, typography, accessibility, and interaction states.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ceshez/VELAR --skill polish-ceshez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/ceshez/VELAR/tree/main/.agents/skills/polish
Command: npx skills add https://github.com/ceshez/VELAR --skill polish-ceshez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the small but noticeable issues—misalignment, inconsistent spacing, missing states, rough copy, and accessibility gaps—that make otherwise good work feel unfinished.

Core Features & Use Cases

  • System-aligned visual refinement: Verifies alignment, spacing scale usage, typography hierarchy, and optical balance against the design system (or visible conventions if none exist).
  • Interaction-state completeness: Ensures every interactive element has default/hover/focus/active/disabled/loading/error/success states with consistent motion and reduced-motion support.
  • Final quality and ship readiness: Covers edge cases, responsiveness, performance basics (CLS/LCP awareness), and cleanup checks (no debug logs, no dead code, no TypeScript laxness).

Quick Start

Tell the agent to polish the target feature for a final pre-launch review, including visual, typography, interaction states, responsiveness, and a last cleanup pass.

Frequently Asked Questions about polish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I catch UI polish issues like misalignment and missing interaction states before launch?

Pre-launch QA for UI polish requires a checklist-driven review verifying visual alignment, typography, interaction states, edge cases, and performance basics. This process identifies design system drift, validates micro-interactions, and prevents new bugs before marking the feature done.

What is included in a pre-launch QA checklist for responsive layout and accessibility?

A pre-launch QA checklist covers visual alignment, typography hierarchy, interaction states, edge cases, and performance basics. It validates responsive layout behavior, ensures accessibility gaps are closed, and checks for cleanup issues like debug logs or dead code before shipping.

How do I ensure interaction state completeness for default, hover, focus, and disabled elements?

Interaction state completeness is ensured by verifying every interactive element has default, hover, focus, active, disabled, loading, error, and success states. The review validates consistent motion and confirms reduced-motion support is implemented across all states.

Can I use this final review process on a feature that is still missing core workflow functionality?

No, this final review process applies only to completed features where the core workflow is already functionally complete. It targets last-mile details like consistency with an existing design system, interaction states, and edge cases rather than building core functionality.

What's the best way to test edge cases and performance basics like CLS and LCP before shipping?

Testing edge cases and performance basics requires a meticulous checklist-driven process covering responsiveness, CLS and LCP awareness, and cleanup checks. This approach prevents new bugs by removing debug logs, dead code, and TypeScript laxness before marking work done.

Why does my otherwise good UI feature feel unfinished despite having all the core functionality?

A UI feature feels unfinished due to small but noticeable issues like misalignment, inconsistent spacing, missing interaction states, rough copy, and accessibility gaps. A systematic final review across visual and functional quality removes these issues to achieve ship readiness.