- Library + Pantheon popovers. Tap any row in 02 — The Library or any Pantheon card; a paper-card dialog lifts off the page. Four designers added; total seventeen.
- Foundations expanded. New grids.md (Swiss + asymmetric); new layouts.md (32 patterns by register); craft.md gains the iteration-sizing framework.
- Register, layout, intent gates wired in. plan opens with a register hard-ask; build enforces register, layout-catalog walk, aspect-ratio inventory, asset-fit re-check.
- New taxonomies + self-review + slop catalog. styles/ ships editorial and expressive; voices/ ships ux-copy, long-form, and four marketing files by ad-lord. Impeccable's catalog folded into anti-slop.md.
The design-expert, at your service.
Most AI ships the same UI because it learned from the same slop.
design-expert teaches it taste.
A complete design discipline — manifesto, craft, references, reviewer — installed into Claude Code as a single command.
01 — Commands
Four verbs.
A shared vocabulary.
design-expert exposes itself through four commands. Each one points at a different mode of design work — the same modes a senior designer moves through every day. Type any of them in Claude Code with a target.
/design-expert:plan
Plan the design first.
Discovery before pixels. Audience, register, brand voice, anti-references — captured as a brief the rest of the work reads. Stops the model from one-shotting a generic mock.
$ /design-expert:plan checkout flow for a calm clinical SaaS /design-expert:buildBuild it on the bar.
From brief to real screens, real components, real type. Reads your tokens, respects your system, ships code — not a Figma mock the model can't render.
$ /design-expert:build pricing page from PLAN.md /design-expert:writeWrite copy that holds.
Display lines, microcopy, error states, empty states — written in the voice the brief committed to, not in default-AI breeziness.
$ /design-expert:write hero for a calm clinical SaaS /design-expert:reviewReview with a real reviewer.
The work gets walked, scored against the foundations, and graded. The reviewer cites the principle behind every note — no vibes-based feedback, no "looks great, ship it."
$ /design-expert:review src/pages/pricing.tsxAll four commands read the same skill files. Edits to SKILL.md propagate everywhere.
02 — The Library
A small library
of skills.
design-expert is markdown all the way down. Every file is a discipline. Every discipline is editable. You can read it, fork it, override a section in PROJECT.md, or hand the whole library to a junior on day one.
Skills · root files
Folders · curated indexes
03 — The Pantheon
The designers
the skill listens to.
A small canon, deliberately curated. Each name has a file in design-gods/ with their work, their rules, and the moments when their judgment overrides the skill's defaults. This is the bar.
04 — Install
2 minute install
design-expert ships as a Claude Code plugin under the khev-tools marketplace. Requires a current Claude Code build (run claude --version; update via Homebrew, npm, or the native installer if /plugin isn't recognized).
Add the marketplace, install the plugin.
Two slash commands, run in sequence. The first registers the khev‑tools marketplace. The second installs design‑expert. Restart the session so the four /design-expert commands register.
$ /plugin marketplace add https://github.com/Khevin/khev-tools
# clones over HTTPS · no SSH key required
$ /plugin install design-expert@khev-tools
# SKILL.md loaded · 14 markdown files · 17 design-gods
# clones over HTTPS · no SSH key required
$ /plugin install design-expert@khev-tools
# SKILL.md loaded · 14 markdown files · 17 design-gods
✓ marketplace added · 1 plugin available
✓ design-expert installed
✓ /design-expert:plan · :build · :write · :review
✓ design-expert installed
✓ /design-expert:plan · :build · :write · :review
Plan something. Then build it.
A brief, then a build, then a review. Each command writes to disk — PRODUCT.md + DESIGN.md from /plan, source files from /build, scored notes from /review.
$ /design-expert:plan a billing-settings page for a subscription SaaS
# writes PRODUCT.md + DESIGN.md · audience, register, tokens, restrictions
$ /design-expert:build billing-settings from PRODUCT.md + DESIGN.md
# reads SKILL.md + the two briefs · ships components in src/billing/
$ /design-expert:review src/billing/
# writes PRODUCT.md + DESIGN.md · audience, register, tokens, restrictions
$ /design-expert:build billing-settings from PRODUCT.md + DESIGN.md
# reads SKILL.md + the two briefs · ships components in src/billing/
$ /design-expert:review src/billing/
✓ scored against 10-lens framework · 6 notes · 0 blockers
05 — FAQ
Six things you might be wondering.
Most of what a designer or engineer asks before installing. Short answers here — the long ones are in the markdown.
-
Q · 01What it is
Is design-expert just a system prompt?
No. It's a plugin: a manifest, a SKILL.md, four sub-commands, a 14-file markdown library, a 17-designer pantheon, and the curated references/, styles/, voices/, and layouts.md taxonomies the commands load on demand. The reviewer doesn't pull typography.md; the writer doesn't pull output-format.md. Context loads when context is needed, every byte earning its place.
-
Q · 02Cost
What does it cost?
Nothing. Open source. Fork the markdown, override what you disagree with, send pull requests. The skill improves when more designers argue with it.
-
Q · 03Compatibility
Does it work with my design system?
Yes — that's the point. The build command reads your tokens, components, and existing screens before it generates anything. design-expert grows with your system rather than around it. Ship a per-surface PRODUCT.md + DESIGN.md pair with your conventions and the skill treats them as the contract.
-
Q · 04Compatibility
Cursor? Codex? Other harnesses?
The skill files are pure markdown and portable. Anywhere you can drop a system prompt, you can paste the contents of SKILL.md + the foundationals and get most of the value. The Claude-Code-shaped wrapper — slash commands, gate-driven workflows, marketplace install — is what's idiomatic today; a universal package will follow once the agent-skill protocol stabilizes across harnesses.
-
Q · 05Future
Will there be other khev-tools plugins?
Yes. design-expert is the first; the marketplace is built to host more. Until then, this is the entire shelf.
-
Q · 06Naming
Why "design-expert" and not something fancier?
Because it does what it says. The plugin is what you reach for when you want a designer in the loop and there isn't one in the room. The name is the contract.
06 — What's New
Recent updates.
design-expert is the first plugin in the khev-tools marketplace. The skill itself is the product, and it ships small.
- Initial plugin release. Four commands — plan, build, write, review — backed by a 12-file markdown library and 13 designer-specific reference files in design-gods/.
- Reviewer scores against ten lenses. Foundations, hierarchy, type, color, composition, motion, copy, accessibility, anti-slop, brand fit. Each note cites the principle behind it.
- PROJECT.md awareness. Per-project overrides — audience, brand voice, anti-references — read on every command. Drop one in your repo root.
- anti-slop.md graduates. 30+ named patterns the reviewer now flags on sight, each with a recommended replacement.
- Brand vs product registers. The skill picks before it generates — landing pages stop being critiqued for breaking dashboard conventions and vice versa.
- First public alpha. SKILL.md + foundations + craft + a single review command. The reviewer was the seed; everything else grew around it.