Questions
limitations · warranty · refundsWill swatchdog force my agent to follow the design?
No. The standard — your own tokens, or a pack — is something your agent builds from, and the check is something your agent calls on its own work. Neither one forces its hand. swatchdog points out where the build doesn't match; your agent does the building and the fixing.
What does the check actually check?
The declared styles and tokens your agent produced — CSS declarations and token usage — against your standard. Every off-token color, radius, spacing, and type value comes back with the exact token to use instead. It runs when your agent calls it; it doesn't look at pixels or rendered output.
How is swatchdog different from a linter like ESLint?
A linter checks whether your code is valid and well-formatted. swatchdog checks whether your design is on-system. A linter happily passes color: #ff00ff because it's valid CSS — it has no idea magenta isn't in your palette. swatchdog catches exactly that: colors, spacing, radii, and type that have drifted from your reference, even when the code is flawless. Lint catches broken code; swatchdog catches broken design.
Can I check against my own design system?
Yes — that's the point. Your agent reads your design tokens (CSS variables, a tokens file, a Tailwind theme), passes them with each check, and swatchdog reports drift against your standard. Curious how your tokens will be read? Preview them in the normalizer.
Can't I just give my AI agent the design tokens or a design.md?
You can, and it'll still drift. Agents approximate and interpolate even with the rules right in front of them — a tokens file or a design.md is instruction, and having the rules isn't the same as following them. swatchdog verifies conformance in the build loop, where the drift actually happens.
What's free, and what does the $12 key get me?
Connecting and checking is free on a shared, rate-capped lane — in Claude as a connector, or from any MCP client. The $12 key is a personal license: your own dedicated lane with a generous usage envelope, for Claude Code, Claude Desktop, Cursor, and other clients that send auth headers. (claude.ai's connector can't take a key yet.) One-time, no subscription.
What happens to the code and tokens I send?
They're checked in the moment and never stored — tokens in, code in, report out. We log only minimal usage metadata (which pack or source, the finding count), never your code, tokens, or key. Details in the privacy policy.
Do I need a pack?
No — bring your own design system and the check works against it. The packs are for when you don't have one: complete, curated visual systems your agent builds from and checks against. Their guidance files also work dropped into any agent with no connection at all; the executable check is the connected part.
Can I use the packs in commercial work?
Yes — build whatever you want with them, including commercial and client projects, as many times as you like. The one thing you can't do is resell or redistribute a pack itself as a design product.
Is there a warranty?
No. swatchdog is sold as-is, with no warranty — use it at your own risk. The live previews and specimens are the sample, so you can see exactly what you're getting before you buy.
Refunds?
All sales are final. The previews and specimens are the sample — try them first, and the free lane lets you try the check itself before buying a key. Because packs and license keys are digital and delivered on purchase, we don't offer refunds.
swatchdog is provided “as is” and “as available,” without warranties of any kind, express or implied — including merchantability, fitness for a particular purpose, and non-infringement. You assume all risk for how you use the packs and validator. To the maximum extent permitted by law, swatchdog and its authors are not liable for any damages arising from their use.