Skip to main content
Agent skill

Make Interfaces Feel Better

Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Make Interfaces Feel Better when an AI agent needs a reusable SKILL.md workflow for this job: Apply concrete design-engineering details that make interfaces feel polished. Use when reviewing or improving UI spacing, typography, borders, shadows, motion, hit areas, icons, text wrapping, and interaction states.

When not to use it

Skip Make Interfaces Feel Better when the task is outside the creativity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/make-interfaces-feel-better
# Save SKILL.md to ~/.claude/skills/make-interfaces-feel-better/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/make-interfaces-feel-better/SKILL.md. For a shared project, commit the folder at .claude/skills/make-interfaces-feel-better/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Make Interfaces Feel Better skill for this task: The user says the UI feels off, flat, generic, cramped, jumpy, or unfinished. Confirm any required inputs or files before making changes.

What supports this recommendation?

83/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
92/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Make Interfaces Feel Better

Use this skill for the small design-engineering details that compound into a more polished interface.

Source: salvaged from stale community PR #1659 by `linus707`.

## When to Use

- The user says the UI feels off, flat, generic, cramped, jumpy, or unfinished. - You are building controls, cards, lists, dashboards, navigation, forms, or toolbars. - A component needs hover, active, focus, enter, exit, loading, or empty states. - A frontend review needs specific before/after recommendations.

## Core Principles

### Concentric Radius

For nearby nested rounded surfaces:

```text outer radius = inner radius + padding ```

If padding is large, treat layers as separate surfaces instead of forcing the math. The point is optical coherence, not formula worship.

### Optical Alignment

Geometric centering is not always visual centering. Icon buttons, play triangles, arrows, stars, and asymmetric icons often need a small offset. Fix the SVG when possible; otherwise adjust with a pixel-level margin or padding change.

### Shadows And Borders

Use borders for separation and focus rings. Use layered shadows when a card, button, dropdown, or popover needs depth. Shadows should be transparent and subtle enough to work across backgrounds.

### Text Wrapping

- Use `text-wrap: balance` on headings and short titles. - Use `text-wrap: pretty` on short-to-medium body text, captions, descriptions, and list items. - Avoid both on long prose, code, and preformatted content. - Use `font-variant-numeric: tabular-nums` for counters, timers, prices, tables, and other updating numbers.

### Font Smoothing

On macOS, apply antialiased font smoothing at the root layout when the project does not already do so:

```css html { -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; } ```

### Image Outlines

Images often need a subtle inset outline so their edges do not blur into the surface.

```css img { outline: 1px solid rgba(0, 0, 0, 0.1); outline-offset: -1px; }

@media (prefers-color-scheme: dark) { img { outline-color: rgba(255, 255, 255, 0.1); } } ```

Use neutral black or white alpha outlines. Do not tint image outlines with the brand palette.

### Motion

Use CSS transitions for interactive state changes because they can retarget when the user changes intent mid-motion. Reserve keyframes for staged one-shot entrances or loading sequences.

Good motion defaults:

- Enter: combine opacity, small `translateY`, and optionally blur. - Exit: shorter and quieter than enter, usually 150ms. - Press: `scale(0.96)` for tactile buttons, with a way to disable it when the movement distracts. - Icon swaps: cross-fade with opacity, scale, and blur instead of instant visibility toggles.

### Transition Scope

Never use `transition: all`. Specify the changed properties:

```css .button { transition-property: transform, background-color, box-shadow; transition-duration: 150ms; transition-timing-function: ease-out; } ```

Use `will-change` only for first-frame stutter on compositor-friendly properties such as `transform`, `opacity`, and `filter`. Never use `will-change: all`.

### Hit Areas

Interactive controls should have at least a 40x40px hit area, ideally 44x44px where the layout allows it. Expand with a pseudo-element when the visible icon is smaller, but do not let expanded hit areas overlap.

## Review Output

When reviewing a UI polish pass, report concrete changes in before/after rows:

| Principle | Before | After | | --- | --- | --- | | Concentric radius | Same radius on parent and child | Parent radius accounts for padding | | Tabular numbers | Counter shifts as digits change | Counter uses `tabular-nums` | | Transition scope | `transition: all` | Explicit transition properties |

Include file paths and properties when they are not obvious from the snippets. Omit principles that you checked but did not change.

## Checklist

- Nested rounded elements are optically coherent. - Icons are visually centered. - Buttons, cards, and popovers use borders or shadows for the right reason. - Headings and short text avoid awkward wrapping. - Dynamic numbers use tabular numerals. - Images have neutral outlines where needed. - Enter and exit animations are split, subtle, and interruptible where appropriate. - Buttons have tactile active states without exaggerated motion. - `transition: all` and `will-change: all` are absent. - Small controls still have usable hit areas.

Intended uses

  • The user says the UI feels off, flat, generic, cramped, jumpy, or unfinished.
  • You are building controls, cards, lists, dashboards, navigation, forms, or
  • A component needs hover, active, focus, enter, exit, loading, or empty states.
  • A frontend review needs specific before/after recommendations.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.