agentleFS
ZhouYinLong-labZhouYinLong-lab/Dog-Skills/make-interfaces-feel-better/SKILL.md

make-interfaces-feel-better

Skill7 starsChanged 5 months agoMITView on GitHub

UI polish skill — 16 design engineering principles for making interfaces feel polished and professional. Covers typography, surfaces, animations, and performance. Triggers on UI review, design details, "make it feel better", "feels off", 界面打磨, UI细节, border radius, shadows, stagger animations, enter/exit transitions, optical alignment, font smoothing, tabular numbers, image outlines.

40 other projects use a version of this, 32 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use add-block, userinterface-wiki and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Ame-AlSkill

    add-block

    Create or update a Sim integration block with correct subBlocks, conditions, dependsOn, modes, canonicalParamId usage, outputs, and tool wiring. Use when working on `apps/sim/blocks/blocks/{service}.ts` or aligning a block with its tools.

    Also in 3 projects that use this

  • raphaelsalajaSkill

    userinterface-wiki

    UI/UX best practices for web interfaces. Use when reviewing animations, CSS, audio, typography, UX patterns, prefetching, or icon implementations. Covers 11 categories from animation principles to typography. Outputs file:line findings.

    Also in 3 projects that use this

  • AnasX7Skill

    transitions-dev

    Production-ready CSS transitions for web apps. Use when implementing notification badges, dropdowns, modals, panel reveals, page transitions, card resizes, number pop-ins, text swaps, icon swaps, success checks, avatar group hovers, error state shakes, search/input clear, skeleton loaders, shimmer text, sliding tabs, tooltips, staggered text reveals, card hover tilt, plus-to-menu morph, accordions, toasts, like buttons, learn-more hovers, checkbox checks, spinning counters, toggles, AI thinking states, reasoning streams, streaming text, matrix dot loaders, or banner stacking. Triggers on "add a transition", "animate the dropdown", "make the modal open smoothly", "swap icon", "page slide", "stagger animation", "open / close transition", "make it animate", "fade between", "success animation", "form error", "shake on invalid", "hover lift", "avatar stack hover", "clear the search", "skeleton loader", "loading shimmer", "shimmer text", "sliding tabs", "segmented control", "tooltip", "reveal text", "tilt card", "3D hover tilt", "cursor glare", "plus to menu", "FAB morph", "accordion", "collapsible", "expand / collapse", "disclosure", "toast", "snackbar", "like button", "heart animation", "learn more arrow", "checkbox", "check animation", "spinning counter", "odometer", "slot machine digits", "toggle", "switch", "thinking states", "AI status line", "agent reasoning", "reasoning stream", "streaming text", "stream words in", "matrix loader", "dot loader", "banner stack", "stacked toasts". Also "motion tokens", "scan for ad-hoc transitions", "replace hardcoded durations with motion tokens", "tokenize my animations", and the commands transitions reveal, transitions review, transitions apply, transitions refine.

    Also in 6 projects that use this

  • AnasX7Skill

    better-typography

    Focuses on type scale, spacing, sizing, variable fonts, OpenType features, wrapping, truncation and other details that make typography feel great across your product.

    Also in 5 projects that use this

  • agentset-aiSkill

    fixing-accessibility

    Fix accessibility issues.

    Also in 4 projects that use this

  • +6 more from AnasX7

The file

We split this skill into the rules it gives an agent

9 rules. 2 are common, 1 is distinctive, and 6 are very specific to this project.

  • 2

    Common

    Most of the 39 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    When geometric centering looks off, align optically.

    line 31
  2. Common:

    Use CSS transitions for interactive state changes — they can be interrupted mid-animation.

    line 37
  3. Common:

    Don't animate a single container.

    line 40
  4. Very specific:

    Use a small fixed translateY(-12px) instead of full height.

    line 43
  5. Very specific:

    Use font-variant-numeric: tabular-nums for dynamically updating numbers to prevent layout shift.

    line 52
  6. Very specific:

    Add 1px outline: pure black rgba(0,0,0,0.1) in light mode, pure white rgba(255,255,255,0.1) in dark mode.

    line 58
  7. Very specific:

    Always specify exact properties.

    line 67
  8. Very specific:

    Only for transform, opacity, filter — GPU-compositable properties.

    line 70
  9. Distinctive:

    Always present changes as a markdown table with Before and After columns.

    line 92

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Details That Make Interfaces Feel Better

Great interfaces rarely come from a single thing. It's usually a collection of small details that compound into a great experience. Apply these principles when building or reviewing UI code.

Quick Reference

CategoryReferenceWhen to Use
Typographytypography.mdText wrapping, font smoothing, tabular numbers
Surfacessurfaces.mdBorder radius, optical alignment, shadows, image outlines, hit areas
Animationsanimations.mdInterruptible animations, enter/exit transitions, icon animations, scale on press
Performanceperformance.mdTransition specificity, will-change usage

Core Principles

1. Concentric Border Radius

outerRadius = innerRadius + padding. Mismatched radii on nested elements is the most common thing that makes interfaces feel off.

2. Optical Over Geometric Alignment

When geometric centering looks off, align optically. Buttons with icons need manual adjustment — icon-side padding = text-side padding - 2px.

3. Shadows Over Borders

Layer multiple transparent box-shadow values for natural depth. Shadows adapt to any background; solid borders don't.

4. Interruptible Animations

Use CSS transitions for interactive state changes — they can be interrupted mid-animation. Reserve keyframes for staged sequences that run once.

5. Split and Stagger Enter Animations

Don't animate a single container. Break content into semantic chunks and stagger each with ~100ms delay.

6. Subtle Exit Animations

Use a small fixed translateY(-12px) instead of full height. Exits should be softer and shorter than enters.

7. Contextual Icon Animations

Animate icons with opacity, scale (0.25→1), and blur (4px→0). Use spring with bounce=0 if Motion available; CSS cross-fade if not.

8. Font Smoothing

Apply -webkit-font-smoothing: antialiased on macOS for crisper text.

9. Tabular Numbers

Use font-variant-numeric: tabular-nums for dynamically updating numbers to prevent layout shift.

10. Text Wrapping

text-wrap: balance on headings (≤6 lines). text-wrap: pretty on body text to avoid orphans.

11. Image Outlines

Add 1px outline: pure black rgba(0,0,0,0.1) in light mode, pure white rgba(255,255,255,0.1) in dark mode. Never use tinted neutrals.

12. Scale on Press

scale(0.96) on click gives buttons tactile feedback. Never below 0.95. Add static prop to disable when distracting.

13. Skip Animation on Page Load

initial={false} on AnimatePresence for default-state elements. Verify it doesn't break intentional entrance animations.

14. Never Use transition: all

Always specify exact properties. Tailwind: transition-transform or transition-[scale,opacity].

15. Use will-change Sparingly

Only for transform, opacity, filter — GPU-compositable properties. Never will-change: all. Only add when you notice first-frame stutter.

16. Minimum Hit Area

44×44px for touch/mobile, ≥40×40px for dense desktop. Extend with pseudo-element. Never let two hit areas overlap.

Common Mistakes

MistakeFix
Same border radius on parent and childouterRadius = innerRadius + padding
Icons look off-centerAdjust optically with padding or fix SVG
Hard borders between sectionsUse layered box-shadow with transparency
Jarring enter/exit animationsSplit, stagger, and keep exits subtle
Numbers cause layout shiftApply tabular-nums
Heavy text on macOSApply antialiased to root
Animation plays on page loadAdd initial={false} to AnimatePresence
transition: allSpecify exact properties
First-frame animation stutterAdd will-change: transform (sparingly)
Tiny hit areasExtend with pseudo-element to 44×44px

Review Output Format

Always present changes as a markdown table with Before and After columns. Group by principle with a heading. Only include principles where changes were made — omit empty tables.

Example

Concentric border radius

BeforeAfter
rounded-xl on card + rounded-xl on inner button (p-2)rounded-2xl on card, rounded-lg on inner button

Scale on press

BeforeAfter
<button className="...">Added active:scale-[0.96] transition-transform

Review Checklist

  • Nested rounded elements use concentric border radius
  • Icons are optically centered, not just geometrically
  • Shadows used instead of borders where appropriate
  • Enter animations are split and staggered
  • Exit animations are subtle
  • Dynamic numbers use tabular-nums
  • Font smoothing is applied
  • Headings use text-wrap: balance
  • Images have subtle outlines (pure black/white, not tinted)
  • Buttons use scale(0.96) on press where appropriate
  • AnimatePresence uses initial={false} for default-state elements
  • No transition: all — only specific properties
  • will-change only on transform/opacity/filter, never all
  • Interactive elements have ≥44×44px hit areas (touch) or ≥40×40px (desktop)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.