polish

Correct visual details and consistency in frontend UI before shipping.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/Tea-4-Life/Tea4Life-Frontend-Website --skill polish-tea-4-life
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/Tea-4-Life/Tea4Life-Frontend-Website/tree/main/.agents/skills/polish
Command: npx skills add https://github.com/Tea-4-Life/Tea4Life-Frontend-Website --skill polish-tea-4-life

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Final quality pass to fix alignment, spacing, consistency, and detail issues that separate good from great, ensuring shipped UI meets design intent.

Core Features & Use Cases

  • Visual alignment and spacing checks across breakpoints
  • Typography and color refinement for consistency
  • Review of interaction states and accessibility cues
  • Final QA on polish readiness for release

Quick Start

Run a final polish pass on the current frontend build to fix alignment, spacing, typography, and interaction details before shipping.

Frequently Asked Questions about polish

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

FAQPage Schema
How do I fix UI alignment and spacing inconsistencies before shipping a frontend build?

To fix UI alignment and spacing inconsistencies before shipping, run a final polish pass that audits visual details across breakpoints. This enforces consistent spacing, typography, and accessible focus states to ensure the frontend build meets design intent.

What is a frontend polish pass for visual design and accessibility?

A frontend polish pass for visual design and accessibility is a last-mile QA step that corrects alignment, refines typography and color, and reviews interaction states. It ensures consistent, accessible focus cues across UI components before release.

Do I need design tokens and component specs to perform a UI consistency check?

Yes, performing a UI consistency check requires access to design tokens and component specs. These inputs allow the polish pass to output a frontend with strictly consistent spacing, typography, color, and accessible interaction states.

What's the best way to review interaction states and accessibility cues for release readiness?

The best way to review interaction states and accessibility cues for release readiness is applying a final QA pass. It systematically audits focus states and visual details, ensuring the UI is pixel-perfect and ship-ready.

When should I not use a final visual polish pass for frontend UI?

You should not use a final visual polish pass when lacking design tokens or component specs, as it targets last-mile QA. It is not for initial layout construction, but for correcting spacing and typography consistency before shipping.