POINT IT AT YOUR VIBE-CODED APP
Shared design memory for you, your agents, and your team.
Harnd — the AI harness for your design system.
Point harnd at the app your agents already built. In minutes, your tokens, components, and the reasoning behind them become one source your agents read before writing UI — and your team can trust. Design quality holds as you add people, agents, and clients.
This is what happens without a harness.
Your agent hardcoded another hex value.
You caught it last week. It's back this week, in a different file.
Three versions of the same button now exist.
No one meant to. Each agent just built what looked right, in isolation.
Nobody remembers why that decision was made.
The diff survived. The reasoning didn't.
How it works
Scan what you've built
npx harnd scan reads your existing code and extracts your tokens, components, and how often each is actually reused. No setup, no account.
Catch drift at the door
harnd validate flags raw colors and off-scale spacing before they ship — and Claude Code, Cursor, Copilot, and Codex read the same harness before writing a line of UI.
Confirm the why, keep the record
Your AI drafts what each token and component is for; you confirm it. Every decision — what changed and why — is recorded locally, forever.
Questions
Does this replace our designer?
No — the opposite. Harnd gives your designer, PM, founder, and agents one shared source, so design decisions don't live in one person's head and no one has to gatekeep every PR. Working solo? It installs the discipline of the designer you don't have yet.
Which agents does it work with?
Any of them. harnd scan writes a plain-Markdown brief into .harnd/agents/ that Claude Code, Cursor, Copilot, Codex — or whatever you switch to next — can read. And harnd validate runs in your terminal and in CI, so the gate holds no matter which agent wrote the code.
Is my code sent anywhere?
harnd init, scan, and validate are fully local — no account, no network, nothing leaves your machine. Only link and sync talk to our cloud, and only if you opt in. It sends harness metadata (token and component names, gates, usage counts, decisions), the file paths those live at, and the single offending line of each violation, up to 200 characters, so the dashboard can show you what drifted. We never upload your codebase — and harnd sync --redact omits even that line.
What do I need to run it?
Node.js 20 or later and a Git repository. That's it — no design tool, no account for the local commands.
What does it cost?
Free while in beta. Waitlist members get first access to pricing and an early-partner offer before anyone else.
Get early access
Join the waitlist. Three quick questions — that's all.