better-ui

Applies design engineering principles to polish UI components, animations, icons, and surfaces.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/xzedm/clipplic-landing --skill better-ui-xzedm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: better-ui
Source: https://github.com/xzedm/clipplic-landing/tree/main/.agents/skills/better-ui
Command: npx skills add https://github.com/xzedm/clipplic-landing --skill better-ui-xzedm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interfaces often feel off due to small compounding details like mismatched border radii, jarring animations, or inconsistent icon weights. This Skill provides concrete principles and review workflows to identify and fix these visual polish issues in frontend code. ## Core Features & Use Cases - UI Polish Principles: Fifteen concrete rules covering concentric border radius, optical alignment, layered shadows, interruptible animations, staggered entrances, and icon stroke matching. - Structured Review Output: Generates findings tables with severity levels, before/after code, file locations, and a final verdict (Block, Needs changes, Approve). - Animation Guidance: Prescribes exact values for icon animations, press feedback (scale 0.96), exit transitions, and motion restraint, with fallbacks for projects without framer-motion. - Use Case: When a button feels unresponsive or a card looks off, apply the principles to add scale-on-press feedback, fix nested border radii, and replace elevation borders with layered box-shadows. ## Quick Start Review my React component code for UI polish issues and suggest fixes for animations, shadows, and icon states.

Frequently Asked Questions about better-ui

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

FAQPage Schema
How do I make UI animations feel more polished?▼

Use CSS transitions for interactive state changes since they can be interrupted mid-animation, and reserve keyframes for staged sequences. Stagger infrequent entrances by about 100ms, keep exits subtle with small translateY values, and use ease-out for both.

How to fix nested border radius that looks off?▼

Calculate concentric radii with the formula outer radius equals inner radius plus padding. For example, a card with 16px inner radius and 8px padding needs a 24px outer radius. Equal nested radii make inner surfaces look pinched.

Should I use framer-motion or CSS transitions for icon animations?▼

If framer-motion is in package.json, use it with spring transitions, duration 0.3, and bounce 0. Without a motion library, keep both icons in the DOM and cross-fade with CSS transitions using cubic-bezier(0.2, 0, 0, 1).

Why does transition: all cause animation problems?▼

transition: all animates every property including ones that should change instantly, causing unexpected motion and performance issues. Always specify exact properties like scale and opacity, and use will-change only for transform, opacity, or filter.

When should I not add animations to UI elements?▼

Skip custom animation on high-frequency interactions like hover or keystroke feedback, since the attention cost repeats on every trigger. Use instant feedback or transitions under 150ms, and never make motion the only feedback channel.