moai-ref-ui-polish

Applies interface polish rules for motion, typography, icons, and hit areas to frontend UI work.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-ui-polish-seung-zedd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-ui-polish
Source: https://github.com/Seung-zedd/secure-file-upload/tree/main/.claude/skills/moai-ref-ui-polish
Command: npx skills add https://github.com/Seung-zedd/secure-file-upload --skill moai-ref-ui-polish-seung-zedd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI-generated interfaces often miss the small visual details — wrong easing curves, mismatched border radii, solid borders used for depth, undersized hit areas — that separate polished interfaces from generic ones. This Skill encodes those interface-taste rules so agents apply them consistently during UI implementation and review. ## Core Features & Use Cases - Polish Rule Tables: Concrete rules for concentric border radius, optical alignment, shadow-vs-border elevation, motion easing, typography smoothing, tabular numbers, icon stroke weight, and minimum hit areas. - Review Modes with Severity Model: quick and full review modes with HIGH/MEDIUM/LOW severity, finding caps, and Block/Needs-changes/Approve verdicts. - On-Demand Reference Depth: references/design-audit.md provides grep-based mechanical detection patterns for codebase-wide audits, and references/motion-principles.md covers motion design reasoning (stagger budgets, personality archetypes, emotion-to-motion mapping). - Use Case: While building a Svelte or React component, apply the Motion table to set ease-out enter animations with a prefers-reduced-motion branch, then run the Verification checklist before shipping. ## Quick Start Review this UI component against the UI polish rules and fix any motion, spacing, or hit-area violations you find.

Frequently Asked Questions about moai-ref-ui-polish

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

FAQPage Schema
How do I make UI animations feel polished instead of generic?▼

Use ease-out deceleration for enter animations and ease-in for exits, with entrances running 30-50% longer than exits. Animate only transform and opacity, specify exact transition properties instead of transition: all, and add a prefers-reduced-motion branch to every non-decorative animation.

What easing curve should I use for CSS transitions?▼

Use cubic-bezier(0.2, 0, 0, 1) as the standard decelerate curve for CSS without a motion library. With a library like Framer Motion, use a spring with duration 0.3 and bounce 0. Never use transition: all; always name exact properties.

Does this apply to native mobile UI or only web CSS?▼

The design principles are platform-neutral and apply to native mobile and desktop UI. Implementation examples are Web/CSS, but the audit reference includes detection patterns for Swift and Kotlin, including reduce-motion handlers on Apple and Android platforms.

What is the minimum hit area for touch targets?▼

Touch and mobile targets need a minimum 44 by 44 px hit area; dense desktop interfaces need at least 40 by 40 px, extendable with a pseudo-element if the visual is smaller. Hit areas must never overlap.

When should I not use this UI polish skill?▼

Do not use it for backend logic, database design, DevOps, or security audits — it is scoped to visual interface detail work only. Also avoid introducing a second styling system for polish fixes; extend the project's existing design tokens and motion library instead.