Design engineering
Skill AgentsORG/design-engineering/skills/design-engineering
Load when reviewing UI code, designing a component or page layout, picking an easing curve or transition pattern, deciding whether something should animate at all, choosing an avatar/typography/color system, writing UI copy or error messages, auditing for AI-default tells or a11y misses, consuming a project's DESIGN.md tokens, giving feedback through Agentation or a similar annotation tool, asking why a UI feels flat, or judging when delight earns its weight. Distills Emil Kowalski, Benji Taylor, Jakub Antalik (transitions.dev), guidelines.sh, Vercel design guidelines, Ben DC, DiceBear, lucide-animated, Google Labs design.md, Agentation, and Index (index.how — Emil Kowalski and Glenn Carstens-Peters).From its SKILL.md
npx -y skills add AgentsORG/design-engineering --skill design-engineeringAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 15 stars15 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.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
8.5 KB, as published. Nobody here has run it
design-engineering
This skill is a graph, not a file. The body below is the Map of Content. Follow the
[[wikilinks]]only as needed — that's the whole point of progressive disclosure.
How to use this skill
- Route first:
[[routing-table]]maps intent → entry node for most single questions. If two intents blur,[[disambiguation]]names the tiebreaker. Multi-cluster jobs follow[[stacking-chains]]. - Otherwise scan the MOCs below, pick the cluster, and open its
MOC-*.mdfor the atomic nodes under it. - Read only the atomic nodes that match. Each node is standalone — you don't need siblings.
- Before reviewing UI code, also load
[[gotchas]]and[[pov]].
If the user asks for a UI code review, use the format defined in [[review-format]] and scan against [[review-checklist]].
Philosophy — when, where, and why polish matters
How to think about taste, delight, and the difference between marketing and product UI.
[[MOC-philosophy]]→ [[taste-is-trained]], [[unseen-details-compound]], [[beauty-is-leverage]], [[delight-impact-curve]], [[feeling-right]], [[marketing-vs-product-ui]], [[states-are-the-work]], [[data-is-content]], [[dependency-discipline]], [[pointing-beats-describing]], [[articulate-precisely]]
Motion — when something should move, and how
The largest cluster. Animation is the most overused tool in modern UI; this cluster tells you when not to animate as much as when to.
[[MOC-motion]]→ [[animation-decision-framework]], [[easing-curves]], [[duration-table]], [[spring-animations]], [[transform-opacity-only]], [[transform-mastery]], [[clip-path-tricks]], [[never-scale-from-zero]], [[gesture-momentum]], [[stagger-choreography]], [[prefers-reduced-motion]], [[fly-not-teleport]], [[responsive-feedback]], [[sonner-principles]], [[debugging-animations]], [[lerp-breathing]], [[morphing-icons]], [[shared-letter-morph]], [[hover-default-imperative]], [[tray-rules]], [[css-conventions]]
Transition techniques — Jakub Antalik's catalog
A subset of motion focused on canonical transitions for common UI archetypes. Where the Motion MOC teaches principles, these nodes teach implementation. From transitions.dev.
- [[cross-blur-transitions]] — Pair opacity 0↔1 with
filter: blur(2px) ↔ 0to mask imperfect crossfades. - [[compose-subtract-asymmetry]] — Enter with more properties than exit. Disappearance feels soft, not reversed.
- [[distance-falloff-propagation]] — Per-element lift via
lift * pow(falloff, distance)for grouped hover. - [[multi-segment-shake]] — Form-error shake at 0%, 28.57%, 57.14%, 78.57%, 100% over 280ms.
Typography — humanizing text
The font defaults of the AI era are tells. Better choices and the rules around them.
[[MOC-typography]]→ [[typography-humanity]], [[line-length-tracking]]
Surface — color, shadow, radius, dark mode, imperfection
The "background" choices that most decks of guidelines skip. They're load-bearing for feel.
[[MOC-surface]]→ [[color-monochromatic]], [[dark-mode]], [[shadows-whisper]], [[border-radius]], [[visual-imperfection]], [[contrast-and-color-scheme]]
Layout — page-level grids, viewports, sticky chrome, URL-as-state
The container, not the component. Marketing especially benefits from custom-per-viewport thinking; product apps benefit from URL-driven state.
[[MOC-layout]]→ [[viewport-custom-design]], [[sticky-and-scroll-tells]], [[url-as-state]]
Components — buttons, hovers, states, cards, forms, avatars, icons, a11y, copy
The atoms users actually touch. Their behavior is where craft lives.
[[MOC-components]]→ [[hover-states-subtle]], [[empty-loading-states]], [[icon-systems]], [[cards-design]], [[forms-validation]], [[avatar-systems]], [[interaction-personality]], [[accessibility-baseline]], [[optimistic-updates]], [[copy-voice]]
Anti-patterns — what AI-generated UI gives away
What looks "AI default" and what to do instead. High-value because it's about deletion, not addition.
[[MOC-anti-patterns]]→ [[ai-default-tells]], [[content-authenticity]]
Meta — review format, design.md, Agentation, evals, per-installer files
Procedural rules and growing files. [[review-format]] is mandatory when doing UI code reviews.
- [[routing-table]] — Intent → entry-node router with the four postures (build / judge / decide / name). Open this before anything else on a single question.
- [[disambiguation]] — The questions that blur together (four motion questions, three dark-mode owners, two layout-shift owners) and which node owns each.
- [[stacking-chains]] — Ordered node chains for multi-step jobs (new screen, feel-better pass, design system, marketing site, a11y pass).
- [[review-format]] — Required output format for UI critiques (Before | After | Why markdown table).
- [[review-checklist]] — Eleven-row audit to scan against before signing off on a UI review.
- [[design-vocabulary]] — The precise word for each design phenomenon and where the skill goes deeper. The lexicon behind [[articulate-precisely]]; seeded by Index (Emil Kowalski & Glenn Carstens-Peters).
- [[using-design-file]] — How to consume a project's
.designcontract (schemadesign.v1). Machine-readable tokens, committed intent, executable policy — and it outranks this skill's defaults. - [[using-design-md]] — How to consume a project's DESIGN.md (Google Labs spec). Tokens are normative; prose is context.
- [[agentation-workflow]] — Install and use Agentation for click-to-annotate design review. Two-session critique-then-fix workflow.
- [[cross-model-testing]] — How to test description / routing changes across GPT, Claude Opus, and Claude Sonnet.
- [[gotchas]] — lived failures, appended as the agent trips up.
- [[pov]] — author/installer's opinions and taste calls that override defaults. Edit this when you fork.
- [[animations-dev-curriculum]] — external pointer to Emil's course; don't duplicate.
Workflow subagents — sibling agents/ directory
Six narrow-purpose subagents live in agents/ next to this file. Spawn one when its specific workflow matches the user's ask. Each subagent loads its own slice of the graph and returns to the main agent with a structured result.
- [[ui-reviewer]] — Runs the
[[review-format]]table +[[review-checklist]]audit on a UI snippet. - [[motion-auditor]] — Animation/transition critique against the motion cluster + transitions.dev nodes.
- [[anti-pattern-scanner]] — Scans for AI-default tells and content-authenticity misses.
- [[agentation-fix-loop]] — Session-2 fix side of
[[agentation-workflow]]. Reads MCP annotations and applies fixes. - [[design-md-consumer]] — Reads a project's DESIGN.md and threads its tokens through generated UI per
[[using-design-md]]. - [[pov-curator]] — Helps the installer fork
[[pov]]and append to[[gotchas]]after a real failure.
See agents/README.md for the full directory and selection guide.
Identity — SOUL.md
The repo also ships a SOUL.md at root — voice, stance, and taste lineage for any agent operating in this skill. AGENTS.md is the "what/how"; SOUL.md is the "who/why". Read it once per session if your harness doesn't auto-inject it.
Tax check
Every sentence above costs tokens in every session. If you find yourself adding a sentence, ask: would the agent get this wrong without it? If no, delete it. If yes, it belongs in an atomic node, not here.
— HKTITAN, 2026.
What ships with it: 80 files
288.0 KB alongside SKILL.md
agents/
- README.md401 B
evals/
- loading.jsonl2.6 KB
- progressive-reads.jsonl3.3 KB
- README.md3.2 KB
references/
- anti-patterns/ai-default-tells.md3.5 KB
- anti-patterns/content-authenticity.md4.8 KB
- anti-patterns/MOC-anti-patterns.md988 B
- components/accessibility-baseline.md3.2 KB
- components/avatar-systems.md8.8 KB
- components/cards-design.md3.9 KB
- components/component-confusables.md2.9 KB
- components/copy-voice.md4.1 KB
- components/empty-loading-states.md2.9 KB
- components/forms-validation.md4.4 KB
- components/hover-states-subtle.md2.9 KB
- components/icon-systems.md3.1 KB
- components/interaction-personality.md5.6 KB
- components/MOC-components.md2.2 KB
- components/optimistic-updates.md4.0 KB
- layout/MOC-layout.md974 B
- layout/sticky-and-scroll-tells.md4.8 KB
- layout/url-as-state.md3.3 KB
- layout/viewport-custom-design.md4.2 KB
- meta/agentation-workflow.md6.4 KB
- meta/cross-model-testing.md3.9 KB
- meta/design-vocabulary.md26.8 KB
- meta/gotchas.md2.8 KB
- meta/pov.md4.6 KB
- meta/review-checklist.md3.0 KB
- meta/review-format.md3.9 KB
- meta/using-design-md.md5.0 KB
- motion/animation-decision-framework.md2.5 KB
- motion/animations-dev-curriculum.md2.9 KB
- motion/clip-path-tricks.md3.9 KB
- motion/compose-subtract-asymmetry.md3.0 KB
- motion/cross-blur-transitions.md2.3 KB
- motion/css-conventions.md4.5 KB
- motion/debugging-animations.md3.7 KB
- motion/distance-falloff-propagation.md3.5 KB
- motion/duration-table.md2.1 KB
40 more files not listed here. See all 80 in the repository.
Gives 0 of the 12 instructions most design frontend skills give
Counted across 1,179 of the 2,086 authors here whose files we hold, read 2026-09-06
- Commit to a bold aesthetic directionin 31 of 1179, across 24 files
- Prefer component composition over inheritancein 28 of 1179, across 14 files
- Animate only transform and opacity propertiesin 27 of 1179, across 22 files
- Memoize expensive computations with useMemoin 26 of 1179, across 13 files
- Use semantic HTML elementsin 24 of 1179, across 23 files
- Virtualize long lists for performancein 21 of 1179, across 10 files
- Use CSS variables for design tokensin 20 of 1179, across 14 files
- Implement loading, empty, and error statesin 20 of 1179
- Lazy load heavy components with Suspensein 19 of 1179, across 8 files
- Respect prefers-reduced-motion media queriesin 18 of 1179, across 10 files
- Prioritize CSS-only animations for HTMLin 18 of 1179, across 16 files
- Use compound components for related UI elementsin 18 of 1179, across 7 files
Said here and by no other author read
- route intent using the routing table first
- read atomic nodes matching the user request
- load gotchas and pov before reviewing UI code
- use the review format for UI code reviews
- scan UI code against the review checklist
- spawn subagents for specific workflow tasks
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.