Frontend & UI
Details that make interfaces feel better
Sixteen concrete UI polish rules with a review checklist.
What it is
A set of design engineering principles for interface polish: concentric radii, optical alignment, layered shadows, staggered enter animations, tabular numbers, hit areas, and transition specificity.
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/
Why it matters for design
- Names exact values, so scale on press is always 0.96, never guesswork.
- Fixes the nested radius mismatch that makes most components read as off.
- Catches layout shift from changing numbers before it reaches users.
What it covers
- Quick reference
- Core principles
- Common mistakes
- Review output format
- Review checklist
- Reference files
How to install
Details that make interfaces feel better
-
Clone the repo.
git clone https://github.com/jakubkrehel/make-interfaces-feel-better -
Point Codex at the skill file.
skills/make-interfaces-feel-better/SKILL.md -
Then describe the UI you want. Codex follows the skill.
How to run it with Codex
-
Point Codex at a component and ask it to apply the principles.
-
Request a review; findings come back as Before and After tables.
-
Run the fourteen-item checklist before merging any frontend change.
Every plugin here is free, open source, and links to its real upstream source.
More on the codex-design list ↗Next step
Design with Open Design, without the setup
Install this plugin yourself, or run a whole curated design layer around Codex with Open Design. Bring your own key, own your output.