agentleFS
Sign inStart free
memi-designmemi-design/design-skills/skills/emil-design-eng/SKILL.md

emil-design-eng

Skill7 starsChanged 4 months agoMITView on GitHub

Apply Emil Kowalski's design-engineering guidance when polishing interface details, choosing motion, or reviewing whether a product feels responsive and intentional.

133 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

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 132 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill as a broad design-engineering field guide.

    line 8
  2. Distinctive:

    Read the relevant section of the upstream field guide.

    line 12
  3. Distinctive:

    Use exact values only when the current component and context support them.

    line 15
  4. Distinctive:

    Verify the result at normal speed, reduced motion, and the target input modality.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 132 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

Emil design engineering

Use this skill as a broad design-engineering field guide. Prefer a narrower skill such as review-animations, improve-animations, or find-animation-opportunities when the request has one bounded motion outcome. Route shader, dither, particle, and GPU-effect implementation to shader-design-engineering, and route rendering evidence audits to creative-rendering-audit.

Workflow

  1. Read the relevant section of the upstream field guide.
  2. Inspect the actual interface, code, and interaction frequency before applying a rule.
  3. Preserve the product's established visual language unless a change has clear user value.
  4. Use exact values only when the current component and context support them.
  5. Verify the result at normal speed, reduced motion, and the target input modality.

This adaptation preserves Emil Kowalski's MIT-licensed upstream guide and routes it through progressive disclosure.

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.

Check your setup, free