Borrowing it
Nothing to install: this file belongs to ahonn/dotfiles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ahonn/dotfiles/master/.claude/skills/emil-design-eng/SKILL.mdgit clone --depth 1 https://github.com/ahonn/dotfilesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/ahonn/dotfiles/emil-design-eng)<a href="https://agentmods.dev/skills/ahonn/dotfiles/emil-design-eng"><img src="https://agentmods.dev/badge/skills/ahonn/dotfiles/emil-design-eng/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ahonn/dotfiles/emil-design-eng"><img src="https://agentmods.dev/badge/skills/ahonn/dotfiles/emil-design-eng.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00477 |
| Opus 5.5 | $0.00008 | $0.00191 |
| Sonnet 5.5 | $0.00004 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
emil-design-eng scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 20d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
97% identical to emil-design-eng — 694 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
- Inspect the component, existing design tokens, input methods, and lifecycle.
- Identify the user benefit of motion: feedback, state change, orientation, or explanation. Repeated interactions need less ceremony and must remain usable.
- Improve the smallest relevant surface. Prefer existing primitives and the product's motion language before introducing another library or abstraction.
- 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.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 20d ago Changed · -631 lines · -15 tokens per session a53f1fdfa819
- 1mo ago First seen · 680 lines · 35 tokens per session scan A 433b5a239cda
emil-design-eng is a skill published in the GitHub repository ahonn/dotfiles (63 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 477 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to emil-design-eng, differing in 694 lines, and is treated as a copy.
Other skills, from other repositories
manage-theme
Switch, create, or debug the color theme of a machine set up by urmzd/dotfiles: one theme colors Ghostty, Neovim (colorscheme and lualine), tmux (catppuccin flavour and colors), and the dotfiles' own output. Covers dotfiles theme / dotfiles theme set, writing a themes/ .toml or a pack's theme.toml, and per-shell…
style-brand
Frame and document a project's visual identity: terminal theme, font, demo capture pipeline, asset conventions. Use when establishing or maintaining brand consistency. Ships an example brand (Cyberdream + MonaspiceNe + teasr) as a template, not a mandate.
visual-design-system
Visual design principles, colour, typography, layout, and spatial composition for Cowboys & Beans projects. Use when: designing web pages or components, choosing colours, setting up type scales, composing layouts, writing CSS, building design tokens, creating fluid responsive designs, reviewing visual quality…
design-taste-frontend
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
responsive-design
Implement modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first breakpoint strategies. Use when building adaptive interfaces, implementing fluid layouts, or creating component-level responsive behavior.
industrial-brutalist-ui
Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.