Communitygithub.com

interface-feel

Use when an app or site should feel more polished, faster or more premium, when auditing or fixing UI feel, motion, animation, transitions or interaction quality, or when applying UX laws, animation principles or UI tips (Fitts, Hick, Doherty, optimistic updates, skeletons, command menu, undo toasts, hit slop, safe triangle, view transitions) to a web or mobile project.

What is interface-feel?

interface-feel is a Claude Code agent skill that use when an app or site should feel more polished, faster or more premium, when auditing or fixing UI feel, motion, animation, transitions or interaction quality, or when applying UX laws, animation principles or UI tips (Fitts, Hick, Doherty, optimistic updates, skeletons, command menu, undo toasts, hit slop, safe triangle, view transitions) to a web or mobile project.

Works with~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/groseljgal/interface-feel/tree/HEAD

Ask in your favorite AI

Open a new chat with this agent skill pre-loaded.

Documentation

Interface feel

The master pass for how an interface moves and responds. It audits what the app does today against forty items (twelve animation principles, eight UX laws, twenty UI techniques) and a motion system, writes a report, then fixes each finding by the pattern for that item. Most apps already have half of the list; the audit says so instead of adding it twice. Speed, targets and trust always apply; decoration is restrained in a work tool.

The project's own design system, motion tokens and rules win over anything here. Performance budgets (LCP, INP, bundle size), accessibility and copy are their own passes beside this one.

Files in this skill

FileUse
reference.mdeach of the 40 items: how to check it, the fix pattern, when to skip it, what a real audit found
motion.mdthe motion system: tokens, twelve rules, CSS patterns, how to audit motion
audit/census.shcode census: counts the patterns behind each item, with file:line leads
audit/probe.jslive page probe: real hit targets, durations, easings, figures, headings, code fields, placeholders
report-template.mdthe audit report: one verdict row per item, order of work, what was not checked

Pass 1: audit (change nothing)

  1. Read the project's design system, motion tokens and UI rules first.
  2. Run the census from the project root: bash <this skill>/audit/census.sh . --show 5. It reads the shipped surface only (dependencies, builds, vendored copies, tests, benches, generated files and comment lines are left out; add more with CENSUS_EXCLUDE="dir1,dir2"). Install ripgrep for a fast run; without it the script falls back to perl. A count is a lead to open, not a verdict.
  3. Run the app. On each key page run audit/probe.js (paste into the console, or await it in a browser tool's JavaScript runner) at 1440 wide and at 375, in each theme the app has. It scrolls the whole page a screen at a time and restores the position. A hidden tab has no width and paints no frames: show it first. Read its output with judgement: a target marked spaced (its gap to the next control reaches the floor) is a lower severity; figures only need tabular-nums where they change; mark decorative mock windows aria-hidden or ignore their rows.
  4. Drive by hand what no script can see, with real pointer events (a browser tool's click, not a synthetic .click()): press each paid or irreversible action twice fast and count server effects; throttle the network and a write to 600 ms and press; open and close every layer fast and reopen it mid-exit, sampling its opacity (motion.md, "Measuring a reopen"); press inside a closing menu; type an accented and a differently cased query; move diagonally toward a hover submenu; Android back with a layer open; swipe a phone sheet.
  5. Write the report from report-template.md: all 40 rows, each there, missing, wrong or skip with a reason, evidence as file:line or a number, and build or pick. Show it before fixing.

Pass 2: fix by the checklist

  1. Trust first: item 39 and anything that can double a charge or lose data, with a test that fails before the fix.
  2. Build items change behaviour without a new look (hit slop, safe triangle, back gesture, accent folding, shortcuts, command menu entries, optimistic writes, skeletons, motion tokens, reversible transitions). Fix each by its pattern in reference.md and motion.md, through the project's own components and tokens, with a test for any logic.
  3. Pick items change the look or the product (corners, blur placeholders, undo instead of a confirm, an error beat, a new motion beat, a view transition). Bench each as before and after at scale 1 in both themes, numbered and separable; build only what the owner picks.
  4. Never trade removed decoration for new decoration.

Pass 3: verify

Re-run the census and the probe and compare the numbers with the report. Drive every fixed interaction the way a user would, in both themes, and at phone width separately. Report built, tested, visually approved and deployed as separate facts, and name what could not be measured (no physical phone, no production build).

The checklist

Numbers match reference.md and the report.

#ItemFails when
AAnimation principles (motion.md)
1Squash and stretcha landing badge, dot or knob stops dead
2Anticipationa press has no state within one frame (scale about 0.97, about 100 ms)
3Stagingan opened layer leaves the primary thing unclear
4Pose to posea busy button, label or icon swap jumps in width or content
5Follow througha layer's content arrives welded to its container
6Slow in, slow outlinear or default ease on UI motion; more than three easings
7Arcssomething travels far in a straight line
8Secondary actiona completed action has no confirming second beat
9Snappy timinga UI response over 300 ms; one surface off its peers; exits not shorter
10Exaggerated feedbackan invalid submit shows only a twitch, no colour beat
11Solid drawingshadows and layers disagree on light and depth
12Appealone real flow, stepped at scale 1, shows a seam
BUX laws
13Fittsa real target under 32 px on desktop or 44 px on a phone
14Bigger hit areastargets grown by enlarging the picture, or siblings overlapping
15Hickmore than five items in one menu block
16Millermore than about seven unchunked top-level items
17Dohertypress to next paint over 400 ms with nothing answering first
18Postelan accent, case or spacing variant of a query finds nothing
19Jakoba pattern behaves unlike its platform (hover submenu, back closes a layer)
20Frequency of usea daily action is more than one step or one command away
CSpeed and feedback
21Skeleton loadersa route paints blank or a spinner on the click frame
22Optimistic updatesa cheap reversible write shows nothing until the server answers
23Command menua destination is reachable by clicking but not by typing
24Shortcut hintsa control with a shortcut does not show it in its tooltip
25Undo toastsa restorable delete has no undo (the owner decides if it replaces a confirm)
26Stale-while-revalidatea revisited page waits instead of painting its last data
27Pre-renderinga likely next page is not prefetched on intent (judge in production)
28Blur placeholdersa loading picture is a grey box
29View transitionsa grid-to-detail open has no shared-element morph
30Swipe-to-dismissa phone sheet or drawer cannot be swiped shut
31Interruptible animationsreopening during an exit replays from zero
DPlatform and detail
32Predictive backAndroid back with a layer open leaves the page
33Hit slopsmall icon controls carry no invisible target growth
34Safe-area insetsbottom floats ignore env(safe-area-inset-*) under viewport-fit=cover
35One-time-code autofilla code field lacks autocomplete="one-time-code" and inputmode="numeric"
36Tabular numberschanging figures jitter (no tabular-nums)
37Balanced headlinesa short multi-line heading leaves an orphan (no text-wrap: balance)
38Continuous cornerssquircle corners not considered (a look call: bench it)
ETrust
39Idempotency keystwo fast presses of a paid or irreversible action make two server effects
40Safe trianglea hover submenu closes on a diagonal move toward it

Common mistakes

  • Adding what exists: skeletons, caching and motion tokens are often there; the verdict is there.
  • Client dedupe as the money guard: two clicks land before a re-render disables the button. Guard on the server (conditional update, deterministic key, lock) and hold the press in a ref.
  • Growing the picture instead of the target; checking targets only at desktop width while a desktop rule kills the phone floor.
  • Keyframes for open and close: they cannot reverse. Use transitions on a state attribute, and make a leaving layer inert.
  • Treating undo, corners or error tone as engineering choices. They belong to the owner.
  • Judging prefetch or timing on a dev server or a background tab.

Related Skills