Make Interfaces Feel Better
UI refinement checklist: micro-interactions, easing, transitions, feedback states
Curated by Skill Harbor — a UI refinement checklist skill: the details that make an interface *feel* better — easing curves, transitions, hover and press states, loading and empty states, feedback on every interaction, consistent motion language. Note the skill itself is a checklist that asks the agent to first inspect the existing UI before proposing changes, and to apply only what fits the project's context — a deliberate fix, not decoration. Distinct from the same author's previously published `jakubkrehel-better-interface` (lot 32) fiche, which covers a different skill in the same repository. By @jakubkrehel, listed here with credit to its creator. Honest caveats: taste-dependent — what feels better is subjective, so review the proposed changes yourself; Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Make Interfaces Feel Better is a UI refinement checklist skill: the small details that make an interface feel right — easing curves, transitions, hover and press states, loading and empty states, feedback on every interaction, a consistent motion language. It works as a checklist, not decoration: the agent first inspects your existing UI, then proposes changes and applies only what fits your project's context.
At a glance
| What it is | A checklist skill for refining interfaces: micro-interactions, easing, transitions, feedback states, loading and empty states, applied deliberately after inspecting the UI that already exists. |
|---|---|
| Who it's for | Developers and designers whose interface works but feels off, and who want a structured pass over the details instead of a redesign. |
| What you give it | Your existing interface — the project or screens you want refined — and your own judgement at the end: the listing is explicit that what feels better is subjective, so you review the proposed changes yourself. |
| What you get | A set of targeted refinement proposals drawn from the checklist — motion, states and feedback — with only the fitting ones applied to your project. |
| Works with | Installed from this listing with the copy-paste install prompt into Muse, then used on your own interface project. It is a distinct skill from the same author's earlier better-interface listing, which covers a different skill in the same repository. |
| Cost | Free |
| Time | A few minutes to install. A refinement pass takes as long as reviewing one screen's states and motion with the checklist. |
Example — a refinement pass on one screen
An example of a typical use, following the inspect-first approach the skill documents — not a reported result.
- You point the agent at a settings screen that feels abrupt; it inspects the current UI before proposing anything.
- Working from the checklist, it proposes easing on the panel transition, a press state on the main button, and a proper empty state for the list.
- You keep the changes that fit your project's motion language and drop the rest — taste stays yours.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 35545eaStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none Install "Make Interfaces Feel Better" for me. Give my agent the UI refinement checklist — micro-interactions, easing, transitions, feedback states Repository: https://raw.githubusercontent.com/jakubkrehel/make-interfaces-feel-better/35545ea1512ad59fa463e6b1f95ca9c052981fe6/skills/make-interfaces-feel-better/SKILL.md Pinned version: install the code at commit 35545ea1512ad59fa463e6b1f95ca9c052981fe6 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the jakubkrehel-make-interfaces-feel-better skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "jakubkrehel-make-interfaces-feel-better". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 35545ea · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.