agentleFS
ahonnahonn/dotfiles/.claude/skills/emil-design-eng/SKILL.md

emil-design-eng

Skill62 starsChanged 2 months agoMITView on GitHub

Refine web component feedback and motion when implementing or polishing a specific interaction.

140 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture-learning-tools, design-frontend-dev and 6 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • The-Vibe-CompanySkill

    capture-learning-tools

    Turn technical conversations, bugs, CI failures, review comments,

    Also in 5 projects that use this

  • The-Vibe-CompanySkill

    design-frontend-dev

    Clean Impeccable frontend design skill. Use when the user wants to

    Also in 5 projects that use this

  • cal1888Skill

    pick-ui-library

    Pick the right library for a given frontend task from a curated, opinionated list — numbers, OTP inputs, charts, command menus, virtualization, drag and drop, toasts, state, styling, and more. Only runs when explicitly invoked; it does not trigger on its own.

    Also in 40 projects that use this

  • sanmidableSkill

    ask-sonner

    Also in 24 projects that use this

  • sanmidableSkill

    animate-expo

    Also in 21 projects that use this

  • +3 more from The-Vibe-Company

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 139 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check rapid reversal, repeated input, varying content, and reduced motion where relevant.

    line 20
  2. Distinctive:

    Treat timings, curves, scales, and effects as starting points to tune, not universal pass/fail rules.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 139 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Design Engineering

Apply Emil Kowalski's design engineering approach to the requested component. Make feedback immediate, preserve spatial relationships, and handle interaction edge cases without burdening the user. Begin with the task; do not return a readiness message or require a fixed review format.

Working approach

  1. Inspect the component, existing design tokens, input methods, and lifecycle.
  2. Identify the user benefit of motion: feedback, state change, orientation, or explanation. Repeated interactions need less ceremony and must remain usable.
  3. Improve the smallest relevant surface. Prefer existing primitives and the product's motion language before introducing another library or abstraction.
  4. Check rapid reversal, repeated input, varying content, and reduced motion where relevant. Report what was inspected or observed and what remains unverified.

Treat timings, curves, scales, and effects as starting points to tune, not universal pass/fail rules. A fade, built-in easing, static state change, or deliberate layout animation can be appropriate. Do not infer poor performance from syntax alone or add motion solely to satisfy a checklist.

Read only the relevant reference

  • Choosing whether and how to animate, timing, easing, springs, or stagger: Motion decisions.
  • Building buttons, tooltips, overlays, toasts, clipped reveals, or other CSS motion: Web component patterns.
  • Investigating frame drops, reduced motion, touch hover, or visual verification: Performance and accessibility.

These implementation references target the web. For React Native or native UI, carry over interaction principles only; use the target platform's animation, gesture, and accessibility APIs. Use apple-design when continuous gesture physics is the central problem, and review-animations for an explicitly requested motion audit. Do not load those skills merely because this file mentions them.

Completion

Explain the visible improvement, cite affected code when reviewing, and disclose device or visual checks that could not be performed. Separate confirmed defects from stylistic alternatives. Follow the task's test mode rather than adding tests for purely visual tuning.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.