moai-ref-ui-polish

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

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/taewook486/Masters_degree --skill moai-ref-ui-polish-taewook486
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: moai-ref-ui-polish
Source: https://github.com/taewook486/Masters_degree/tree/main/.claude/skills/moai-ref-ui-polish
Command: npx skills add https://github.com/taewook486/Masters_degree --skill moai-ref-ui-polish-taewook486

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Frontend code written by developers or AI agents often misses the small visual details — wrong easing curves, mismatched border radii, undersized hit areas, missing reduced-motion handling — that separate polished interfaces from generic ones. This Skill provides a structured rule set and audit methodology to catch and fix those details. ## Core Features & Use Cases - Polish Rule Tables: Concrete rules for concentric border radius, optical alignment, shadow-vs-border usage, motion easing, typography smoothing, tabular numbers, icon stroke weight, and minimum hit areas. - Design Audit Suite: Grep-based mechanical detection patterns (in references/design-audit.md) for motion gaps, accessibility violations, layout-property animation, and duration/easing consistency across a whole codebase. - Motion Principles Reference: Platform-neutral guidance on emotional intent, stagger budgets, motion archetypes, and Disney-adapted animation ranges (in references/motion-principles.md). - Use Case: When reviewing a React frontend pull request, use this Skill to verify enter animations use ease-out, every animation has a prefers-reduced-motion branch, hit areas meet 44x44px, and icons use currentColor rather than separate state assets. ## Quick Start Review this UI component against the UI polish rules and report any HIGH or MEDIUM findings on motion, typography, and hit areas.

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 review frontend code for UI polish issues?▼

Run the design audit patterns in references/design-audit.md using grep against the project source. Check motion gaps, accessibility handlers, layout-property animation, and duration/easing consistency, then report findings using the HIGH/MEDIUM/LOW severity scale with the quick (5) or full (15) finding caps.

What easing should enter and exit animations use in CSS?▼

Enter animations use ease-out so elements decelerate as they arrive; exit animations use ease-in so they accelerate away. The standard CSS decelerate curve is cubic-bezier(0.2, 0, 0, 1), and entrances should run 30-50% longer than exits.

Does this UI polish guidance apply to native mobile apps?▼

Yes, the design principles are platform-neutral and stated in milliseconds and easing families. The audit suite includes Swift and Kotlin grep patterns for reduced-motion handlers and easing inventories, though implementation examples in the main rules are Web/CSS.

Why is transition: all considered a problem in CSS?▼

transition: all animates properties you did not intend, including layout properties like width and margin, causing unexpected motion and layout thrashing. Always specify exact properties such as transition-property: scale, opacity.

What is the minimum touch hit area for mobile UI?▼

Touch targets need a minimum of 44x44px on mobile and 40x40px on dense desktop interfaces, extendable with pseudo-elements when the visual is smaller. Hit areas must never overlap, and hover-only affordances must not be load-bearing on touch devices.

When should I not use this UI polish skill?▼

Do not use it for backend logic, database design, DevOps, security audits, or any non-UI work. It is scoped to visual detail and interaction polish for frontend and interface code only.