Personal agent skills distilled from Karl Koch's writing on design engineering, fluid interfaces, semantic HTML, and AI judgement.
Install selectively. Compose deliberately. Or run the full suite with dxe.
Install the full collection once, available in every project:
npx skills add kemiljk/skills -g --allThat installs every skill (including the dxe master pass) to all detected agents. Verify with:
npx skills ls -gUpdate later with:
npx skills update -gShare skills with a repo/team (committed into the project):
npx skills add kemiljk/skills --allList what’s in the package:
npx skills add kemiljk/skills --listInstall only what you need (add -g for global):
npx skills add kemiljk/skills -g \
--skill fluid-design \
--skill modern-css-html \
--skill ai-output-judgementTarget specific agents:
npx skills add kemiljk/skills -g -a cursor -a claude-code --alldxe is the orchestrator — paired with d×e. One short name; one full-suite design-engineering pass on a repository or scoped path.
Prerequisite: install the full collection (-g --all above). dxe reads each sibling SKILL.md and will stop if any are missing.
In Cursor / Claude Code (or any agent that has the skills installed), ask for a pass:
| Prompt | Behaviour |
|---|---|
dxe / “run a dxe pass” |
Full workspace review; propose fixes |
dxe src/components |
Scope to that path |
dxe review |
Findings only; no edits |
dxe fix |
Findings, then high-confidence fixes |
Phases in order:
- Intent —
write-first-design,subtractive-design
Hypothesis for the pass; cut unexplained chrome and generative residue. - Platform —
semantic-html-first,modern-css-html
Native elements and modern CSS/HTML before ARIA theatre or JS hacks. - Feel —
fluid-design,interface-affordances,product-delight
Interruptible motion, discoverable controls, care over novelty. - Bridge —
design-engineering
Map design structure to code structure; keep taste attached to materials. - Shipping —
ai-output-judgement,prototype-to-production
Name concrete AI-median failures; harden empty/error/auth/focus paths.
You get a single report: hypothesis, findings by severity (tied to skill names), subtractive cuts, and ordered next actions.
Use individual skills when you want a narrow lens. Use dxe when you want the full design-engineering pass on a repo.
| Skill | Use when |
|---|---|
dxe |
Master pass — full design-engineering suite on a repo or path |
fluid-design |
Interfaces need physical motion, gestures, layout continuity |
modern-css-html |
Writing/reviewing CSS & HTML with current platform features |
semantic-html-first |
Building controls, forms, disclosure, dialogs |
interface-affordances |
Discoverability and perceptible interaction cues matter |
write-first-design |
Decisions should be written before pixels or code |
design-engineering |
Bridging design intent and production implementation |
product-delight |
Adding polish without confusing novelty for care |
subtractive-design |
Removing noise and requiring purpose |
ai-output-judgement |
Reviewing generated drafts before shipping |
prototype-to-production |
Hardening happy-path prototypes for real use |
Skills overlap on purpose. Use this order when several activate — or invoke dxe to run them as one pass:
- Intent —
write-first-design,subtractive-design - Platform —
semantic-html-first,modern-css-html - Feel —
fluid-design,interface-affordances,product-delight - Bridge —
design-engineering - Shipping —
ai-output-judgement,prototype-to-production
When motion taste and CSS purity disagree:
fluid-designdecides how the interaction should feelmodern-css-htmlchooses the most native implementation that can deliver it- JavaScript/Motion/SwiftUI remain appropriate for interruption, velocity, and gesture continuity CSS cannot express
fluid-design and modern-css-html previously lived in standalone repositories:
Those names are preserved here with tighter activation files, clearer checklists, and on-demand references. New installs should use this collection.
These skills compress lessons from essays such as:
- 10 Principles for Fluid UI
- On the semantic web
- Write-first design
- The slop isn't the models
- Ten principles for product delight
- Beauty comes from absence
- Design for handshakes, not handovers
- On teaching AI how you work
Each skill should stay:
- trigger-precise in frontmatter
description - compact in activated
SKILL.md - actionable via prefer/reject rules and checklists
- progressively disclosed when examples are long enough for
references/
MIT