Three families, one standard.
View all 15 specimens →Fifteen colorways, three families — each a complete visual system your AI builds from, not a theme you bolt on. Pick the look; your AI builds to it automatically — and over MCP it works from the pack and checks its own build against the standard, in the same loop.
How it works
the look is automatic · build & check live over MCPThe look comes through from the pack with no setup — drop the files in, or paste a single text file. The structured pack files give file-based tools more to read, and over MCP your AI works from the pack and runs a live check against the standard. swatchdog doesn't deliver a template, so the composition and layout are still yours to refine.
-
01
Get the pack
Buy a family or the full bundle and download the zip. Inside: the complete coded system — tokens, CSS, components, rules, agent prompt — plus a ready-to-paste single text file for each look.
-
02
Give it to your AI
Two ways — go by how you build:
If you build by chatting (Base44, Lovable, v0, Replit, ChatGPT, Claude) — paste the single text file as your first message.
If your tool works in your files (Claude Code, Cursor, Codex) — drop the pack folder into your project and tell it to use it.
-
03
Build
Your AI builds your app in the pack's look — automatically. You direct the layout; the standard keeps colors, type, components, and character coherent throughout.
Build and check — over MCP. Connect swatchdog as an MCP server and your AI works the pack as a live source — pulling its tokens and rules as it builds, and calling check_drift on its own output for structured findings on declared styles and tokens. Not an after-the-fact audit: build + validation in the same loop — check, revise, check again.
Questions
limitations · warranty · refundsWill swatchdog force my agent to follow the design?
No. The pack gives your agent a standard to build from, and the live check is something your agent calls on its own work — neither one forces its hand. swatchdog makes the standard available and points out where the build doesn't match; your agent does the building and the fixing.
What does the live check actually check?
It reads the declared styles and tokens your agent produced — CSS declarations and token usage — and returns structured issues where they don't match the pack. It runs over MCP when your agent calls check_drift. It doesn't look at pixels or rendered output.
Do I need the MCP server?
Not for the guidance — the pack files (tokens, CSS, components, rules, agent prompt) work dropped into any agent. MCP is the live channel: connect swatchdog as an MCP server and your agent works from the pack as a live source and can call check_drift on its own work. The executable check is the MCP-only 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. Because the packs 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.


