Skip to content
designmotionhq

Make Claude Code ship UI that thinks before it renders.

UX Engine is a Claude Code plugin: nine skills of senior-designer reasoning, four commands that run them.

Works inClaude CodeCursorCodexOpenCode· one-time payment

30-day money-back guarantee, no questions asked

Not templates. Rules.

24 products, 24 looks. Every screen here was made by UX Engine 2.4.

4 commands you type. 9 skills that decide.

/restyle Diagnoses an existing UI axis by axis, applies DESIGN.md, hands back a before/after.

It reads the screen axis by axis (type, colour, space, finish) and says what is a decision and what is a default. Then it applies your DESIGN.md, writing one first if you have none, and hands back the before and after. Logic and structure stay untouched.

When the UI works but looks like every other AI-built app.

The 9 skills underneath

The commands run them on demand, and Claude also loads them on its own whenever it touches UI.

  • Intent Discovery. Forces the who / what / worst-case questions before a single line of UI is written.

  • Information Hierarchy. Ranks actions primary / secondary / tertiary and enforces scanning patterns and density.

  • State Completeness. Covers the states a component can actually be in: loading, empty, error, success, plus partial and offline where they apply.

  • Form UX. Field grouping, label placement, validation strategy, smart defaults, progressive disclosure.

  • Feedback & Affordance. Feedback under 100ms, confirmation on destructive actions, clickable looks clickable.

  • UX Auditor. Point it at any UI: “audit” returns a severity-ranked fix list, “fix” returns the fixed code with the findings it addresses.

  • Design System. Makes sure DESIGN.md exists and is complete before the first screen: written from the tokens you already have, completed when sections are missing, then followed by every screen and every later session.

  • Visual Character. A look taken from what your product is about, with a font that actually loads. Type, color, space and finish decided as tokens before the markup, never the framework palette.

  • Responsive. What tables, amounts, inputs, touch targets and bottom bars become under 640 px, so app screens hold on a phone.

One payment. Yours forever.

No subscription: pay once, keep it, get a year of updates. One licence per person who runs the plugin, client work included.

one-time payment ·Works inClaude CodeCursorCodexOpenCode

Soloone licence per person

$79

Your products, and your clients'.

Everything UX Engine does, for you, on every project: your own SaaS and the sites you build for clients.

  • All 9 skills, 2 sub-agents, 4 slash commands
  • A guide: where to start on a screen you already shipped, and how to tell each skill is working
  • 12 months of updates included
  • Email support, 72h response
Get UX Engine · $79

Buying for several people? One licence each. More than 10, or a particular need? Email support@designmotionhq.com.

Try it for 30 days. If it doesn't change how Claude ships UI, one email to support@designmotionhq.com gets you a full refund. No questions, no forms.

Buy. Paste two lines. Done.

Your receipt holds your key; the install page turns it into two lines to paste into Claude Code. Updates come through Claude Code from then on, no re-download. Prefer files? The ZIP is still there.

35 blind tests. 35 wins.

It picked UX Engine every time. We run the same test before every release.

How we test

We gave Claude Code seven everyday requests: add an invoices page, clean up a users table, build a signup form, design a pricing page. Each one ran ten times in four React projects, from a shadcn admin to a bare form, five times with UX Engine and five times without. Then a second model looked at each pair without knowing which was which, and picked the one it would ship.

Claude Code alone compared with Claude Code and UX Engine, on the same prompts
Examples from the test promptsClaude aloneWith UX Engine
Users table cut to the columns that matter0/55/5
Signup: a network failure gets a specific message and keeps what was typed0/55/5
Inputs with the right type and autocomplete1/55/5
Invoice search with no match offers a way to clear it0/55/5
Pricing page colours taken from the project's tokens0/55/5
Type, colour and radii chosen for the product, not framework defaults0/54/5
Audit of a page with 18 planted defects: share found49%62%

Claude Sonnet, 5 runs per side and per prompt. Measured on our test projects, not a promise on yours: the 30-day refund covers the rest.

From people who installed it.

  • The UX engine became a standard plugin in my Claude, really love it”

    Developer, UX Engine customer

  • I just purchased and it's sick, it helped me so much”

    UX Engine customer

Things you probably want to know.

My product is already shipped. Is this only for new screens?

No. /restyle gives a screen you already shipped a look of its own, applied through your DESIGN.md, and hands back the before and after. /ux-audit returns a severity-ranked list of what to fix, or the fixed code. The included guide shows where to start on a screen you already have.

Will it keep my client's design system?

Yes, it builds on it. It reads the tokens the project already has, writes them to DESIGN.md at the root of the repo and only completes what is missing, so the next screens start from the same file. In our test, the pricing page took its colours from the project's tokens in 5 runs out of 5, and 0 out of 5 without the plugin.

How do I know it works?

Before release, the same everyday prompts run with and without the plugin in four real projects, and a second model that cannot tell which is which picks the code it would ship. In release 2.2 it picked the plugin's version in 35 duels out of 35. Then check it on your own screens: the guide shows how to tell each skill is working, and you have 30 days to decide.

Will it interrogate me before every screen?

No. It reads your project first (README, DESIGN.md, the screens next to the new one) and builds. It only asks when the request is wide open, like “build me a dashboard”, and nothing in the project says who the screen is for. A change to an existing screen gets no questions at all.

Will it slow me down?

A small edit runs just like Claude alone. A new screen takes about twice the time and tokens up front, because the plugin reads your project and decides before it writes, so you don't rebuild the screen twice after.

Does it work outside Claude Code?

Yes. Cursor, Codex and OpenCode are tested, and any agent that loads skills in the standard SKILL.md format works. The install steps for each come in your receipt.

Which licence do I need?

One licence for each person who runs the plugin, client work included. Your clients, and the people who use what you build for them, never need one. More than ten people, or a particular need: email support@designmotionhq.com.

The free breakdowns UX Engine is built on.

One pattern, one video, one takeaway. 76 of them, free to read.

Browse all 76

Stop debugging interfaces. Start designing them.

One plugin. Nine skills. Two agents. Four commands. Your Claude Code, but with senior-designer reasoning baked in.

30-day money-back guarantee, no questions asked

Works inClaude CodeCursorCodexOpenCode· one-time payment