Design Engineering Skill for Muse
Emil Kowalski's animation and design-engineering craft, on tap.
Curated by Skill Harbor — a free, open-source skill (MIT) by @emilkowalski (author of Sonner), listed here with credit to its creator. This is his design-engineering craft in a box: an animation decision framework, CSS transform and clip-path techniques, spring physics, gesture interactions, performance rules, accessibility, and the component-building principles behind Sonner — plus Before/After/Why reviews for your own UI. Paste your interface or code and ask; Muse answers like a design-engineering advisor. Heads-up: the skill is code-heavy (CSS/JS snippets), so it's best suited to people building web interfaces. Discovered via skills.sh. Skill Harbor never reviews the code, review it yourself before use. Not verified.
Version:
Quick answer
This skill packages Emil Kowalski's design-engineering craft — the author of Sonner — for Muse: an animation decision framework, CSS transform and clip-path techniques, spring physics, gesture interactions, performance rules and accessibility. Paste your interface or code and ask; it answers like a design-engineering advisor, including Before/After/Why reviews.
At a glance
| What it is | A practitioner's knowledge base in skill form: how a respected design engineer decides animations, builds components like Sonner, and reviews interfaces — as principles, techniques and code snippets. |
|---|---|
| Who it's for | People building web interfaces who want their motion and interaction details to feel crafted instead of default. It is code-heavy, so it suits builders comfortable reading CSS and JS. |
| What you give it | Your interface or its code, and a question — an animation to choose, a gesture to implement, a component to review. |
| What you get | Advisor-style answers grounded in the framework: which animation fits and why, the transform or spring approach, performance and accessibility checks — and Before/After/Why reviews of your own UI when you ask for one. |
| Works with | Muse, installed from this page with the copy-paste install prompt. Free and open source under MIT. |
| Cost | Free |
| Time | A few minutes to install. Each question is then a single exchange: paste, ask, apply. |
Example — reviewing a drawer animation
An example of the exchange the listing describes — advice and review, in the format the skill itself uses:
- You paste the code of a drawer component whose slide-in feels off, and ask what is wrong with the motion.
- The skill answers from its animation framework: it looks at the easing and spring behavior, the transform technique, and whether the gesture handling and performance rules are respected.
- It gives you the review in its Before/After/Why form — what the interaction does now, what it should do instead, and the reasoning — so you can apply the change and keep the principle for the next component.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit e8a175dStep 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 — just paste the prompt into a Muse conversation. (Basic web/CSS familiarity helps you apply the advice.) Install "Design Engineering Skill for Muse" for me. Emil Kowalski's animation and design-engineering craft as an on-demand advisor: springs, gestures, performance, and Before/After/Why UI reviews. Repository: https://raw.githubusercontent.com/emilkowalski/skills/e8a175de22ae1e49370fc144c1f3bb9aeedf988d/skills/emil-design-eng/SKILL.md Pinned version: install the code at commit e8a175de22ae1e49370fc144c1f3bb9aeedf988d 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 from the repository path 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. 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 "emil-design-eng". 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. Rules: don't touch anything outside the temp folder and the install target. 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
- e8a175d · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 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.