# 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.

- Skill: `memi-design/emil-design-eng` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add memi-design/emil-design-eng`
- Raw SKILL.md: https://api.skillmd.com/api/skills/memi-design/emil-design-eng/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: memi-design (https://skillmd.com/u/memi-design)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/memi-design/emil-design-eng

---


# 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](FIELD-GUIDE.md).
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.