polish

Review UI and code for spacing, typography, interaction states, and accessibility.

Updated May 22, 2026
One-click install
npx skills add https://github.com/Nweremizu/ekklesia --skill polish-nweremizu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polish
Source: https://github.com/Nweremizu/ekklesia/tree/main/.junie/skills/polish
Command: npx skills add https://github.com/Nweremizu/ekklesia --skill polish-nweremizu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch the small but important issues that make a finished product feel rough, inconsistent, or not quite ready to ship.

Core Features & Use Cases

  • Visual refinement: Tightens spacing, alignment, typography, and layout consistency across screens and breakpoints.
  • Interaction polish: Checks hover, focus, active, loading, success, and error states so the experience feels complete.
  • Quality cleanup: Removes copy inconsistencies, accessibility gaps, code clutter, and other finish-line defects.
  • Use case: Apply it before launch to turn a functional feature into one that feels intentional, reliable, and production-ready.

Quick Start

Use this skill to review the attached feature for spacing, typography, interaction states, accessibility, and copy consistency, then return a prioritized list of precise polish fixes.

Frequently Asked Questions about polish

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

FAQPage Schema
How do I check UI spacing and typography before shipping a feature?

Run a pre-release UI review to check spacing, alignment, and typography consistency across responsive breakpoints. This process validates your design system coverage and interaction states to ensure the feature feels finished and shippable.

What interaction states should I verify for a polished responsive design?

Verify hover, focus, active, loading, success, and error states to ensure a polished responsive design. Covering these interaction states prevents finish-line defects and makes the experience feel complete and reliable.

How do I find accessibility gaps in a finished UI feature?

Audit the finished feature for accessibility gaps by checking interaction states, copy clarity, and design-system compliance. This quality cleanup identifies and resolves barriers so the interface meets production-ready standards.

Does code cleanup matter when finalizing UI details for release?

Code cleanup matters when finalizing UI details because removing clutter and validating code hygiene prevents finish-line defects. This ensures the released feature remains visually polished, performant, and maintainable.

What is the best way to review a design system for shippable quality?

Audit spacing, typography, and interaction states across responsive interfaces to review a design system for shippable quality. This validates state coverage and performance checks to ensure the result is polished and release-ready.

Why does my functional feature still feel rough before launch?

A functional feature feels rough due to unpolished spacing, incomplete interaction states, or accessibility gaps. Applying a final UI review catches these small but important issues to make the product feel intentional and production-ready.