jakubkrehel / make-interfaces-feel-better

The skill is drawn directly from the author's own article, "Details that make interfaces feel better," and turns its list into instructions an agent can act on: text-wrap: balance/pretty for headlines and paragraphs, concentric border radius on nested elements, contextual icon animations built from opacity, scale, and blur rather than a single fade, font smoothing on macOS, tabular numbers for values that tick over, CSS transitions instead of keyframes so an animation stays interruptible, split-and-stagger enter animations, deliberately subtle exit animations, optical rather than geometric alignment, shadows in place of borders, and outlines on images for depth. It ships with quick and full review modes, so an agent can either sweep a diff for the obvious misses or work through the full list.

There is nothing to configure: the skill needs no API key, package, or local tool (our dependency label for it is ready), and once installed it applies automatically whenever a build, review, or animation task looks like it touches UI polish; it can also be invoked directly with /make-interfaces-feel-better. It is written for whoever is already building or reviewing frontend code with a coding agent, not for backend work, and it does not replace a design system — it is a checklist layered on top of one, aimed at the small details a design system usually leaves unspecified.

READ THE FULL ANALYSIS＋

It is one person's taste, not a tested methodology. The readme cites no research, framework, or team behind the list beyond the author's own article, and the repository is exactly this one skill file — there is no examples directory and no test suite to check the guidance against. The readme's closing line claims an MIT license, but our own capture recorded no license field for this repository, so treat that claim as unverified rather than confirmed.