What is the make interfaces feel better skill?
Make interfaces feel better is a skill in the affaan-m/ECC repo for design-engineering details. It teaches an AI coding agent concentric radius, optical alignment, balanced text wrapping, tabular numbers, image outlines, scoped transitions and 40 pixel hit areas, and it reports changes as before and after rows.
This is a single SKILL.md in the ECC repository about the small design-engineering details that compound into a polished interface. It applies when someone says the UI feels off, cramped, jumpy or unfinished.
It is a checklist of specific CSS and interaction rules rather than a design philosophy. Each rule is concrete enough for an agent to apply and for a reviewer to verify in a diff.
What changes in your agent's output
- Nested rounded surfaces follow outer radius equals inner radius plus padding, so corners look coherent.
- Headings use text-wrap balance, short body text uses pretty, and counters or prices use tabular numerals.
- Transitions name their properties. The skill forbids transition all and will-change all.
- Small controls keep at least a 40 by 40 pixel hit area, ideally 44, expanded with a pseudo-element.
- Reviews arrive as before and after rows that name the file and property that changed.
Who it is for
Best for
- Finished-but-flat screens that need a final polish pass without a redesign.
- Controls, cards, lists, forms and toolbars that need hover, active and focus states.
- Reviewers who want specific before and after recommendations instead of general taste notes.
Not for
- Choosing a visual direction or brand. It assumes the design already exists.
- Component-library rules for a particular framework.
- WordPress output. It edits CSS and markup in your project.
Use it with UiChemy
Polish rules like these apply to code you own. If the finished design moves to WordPress, UiChemy Figma to WordPress converts a design into editable pages, and you can apply the same ideas in the Figma file. Click Get Started on uichemy.com.
How to install Make Interfaces Feel Better Skill: UI Polish Details for AI Agents
npx [email protected] setupSetup can be rerun later to update ECC or change scope. A manual route is also described in the README: clone the repository and copy the skill folder you want.Check the prerequisites
The README asks for Node.js 18 or newer. The Claude Code plugin route also needs Git and Claude Code 2.1 or newer on your PATH.
Run the guided setup
Run
npx [email protected] setupand follow the prompts. It installs the ECC plugin, which carries the whole skill library, not this skill on its own.Choose one install method
The README warns against stacking install methods in the same harness, because that can duplicate skills, commands and hooks. Pick the plugin route or a manual route, not both.
Other agents
For Codex or Kimi Code run
npx [email protected] install --guided. It lets you pick the harnesses and shows each destination before writing.Use the skill
Ask your agent to run the make interfaces feel better pass on a component or page and to return before and after rows.
Check that it loaded
Ask the agent for its loaded skills and look for make-interfaces-feel-better, or request a polish review and check that the output uses before and after rows.
Key features
- Concentric radiusFor nearby nested rounded surfaces the outer radius is the inner radius plus the padding. When padding is large, treat the layers as separate surfaces, since the aim is optical coherence.
- Optical alignmentGeometric centering is not always visual centering. Play triangles, arrows and stars often need a small offset, best fixed in the SVG itself.
- Shadows and bordersBorders separate surfaces and draw focus rings. Layered, transparent shadows add depth to cards, buttons, dropdowns and popovers across different backgrounds.
- Text wrappingBalance suits headings and short titles, pretty suits short to medium body text, and both are avoided on long prose, code and preformatted content. Tabular numerals suit updating numbers.
- Font smoothingOn macOS the skill suggests antialiased smoothing at the root layout when the project does not already set it, with the matching Firefox property.
- Image outlinesImages get a one pixel inset outline in black or white alpha so edges do not blur into the surface. The skill says not to tint these outlines with the brand palette.
- Interruptible motionCSS transitions handle interactive state because they retarget mid-motion. Keyframes are reserved for staged one-shot entrances. Exits are shorter than enters, around 150 milliseconds.
- Press feedbackTactile buttons can scale to 0.96 on press, with a way to turn it off when the movement distracts. Icon swaps cross-fade instead of toggling visibility.
- Transition scopeTransition properties and durations are listed explicitly. Will-change is used only for first-frame stutter on transform, opacity and filter.
- Hit areasInteractive controls keep at least 40 by 40 pixels, ideally 44 where the layout allows, and expanded hit areas must not overlap.
Frequently asked questions
What is make interfaces feel better?
It is a skill in the affaan-m/ECC repository with concrete rules for UI polish. It covers concentric radius, optical alignment, shadows and borders, text wrapping, tabular numbers, image outlines, scoped transitions and hit areas, and it asks for before and after rows in reviews.
How do I install make interfaces feel better?
It ships inside ECC. The README's recommended route is npx [email protected] setup, which needs Node.js 18 or newer. Use one install method per agent, because the README warns that stacking a plugin and a manual install can duplicate skills.
What is concentric radius?
When rounded shapes sit inside each other, the outer radius should equal the inner radius plus the padding between them. That keeps the curved gap even. The skill adds that very large padding means the layers read as separate surfaces, so the formula should not be forced.
Why does the skill ban transition all?
Transition all animates every property that changes, including ones you did not intend, and prevents the browser from retargeting cleanly. The skill asks you to list the changed properties, such as transform, background-color and box-shadow, with an explicit duration and timing function.
What hit area size does it recommend?
At least 40 by 40 pixels for interactive controls, ideally 44 by 44 pixels where the layout allows. When the visible icon is smaller, expand the target with a pseudo-element, and make sure neighbouring expanded areas do not overlap each other.
Does it work with Claude Code, Cursor and Codex?
The ECC README says it works best with Claude Code, has native Codex and Qoder plugin paths, and offers capability-limited adapters for Cursor, OpenCode, Gemini and others. See its support matrix before assuming every feature is available in your tool.
What are alternatives to make interfaces feel better?
For a similar final pass, see Polish and Emil Design Eng, which covers animation and UI polish rules. Baseline UI sets guardrails for cleaner AI-built interfaces. They overlap in intent but differ in how prescriptive the CSS rules are.


