Emil design eng
Apply Emil Kowalski's design-engineering guidance when polishing interface details, choosing motion, or reviewing whether a product feels responsive and intentional.From its SKILL.md
npx -y skills add sarveshsea/design-skills --skill emil-design-engAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, 196 tokens by cl100k_base, as published. Nobody here has run it
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
- Read the relevant section of the upstream field guide.
- Inspect the actual interface, code, and interaction frequency before applying a rule.
- Preserve the product's established visual language unless a change has clear user value.
- Use exact values only when the current component and context support them.
- 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.
What ships with it: 3 files
28.5 KB alongside SKILL.md
- FIELD-GUIDE.md26.7 KB
- LICENSE1.0 KB
- note.json794 B