Building on a client brand
Stop agents inventing near-miss blues.
A saved project becomes a hosted MCP server. Your agent reads the current tokens and rules instead of guessing hex values, and Brand Check lints the code it writes against the same system.
From a saved project to a result, in four steps.
Capture a site into the Vault. The newest snapshot, or one you pin, is what gets served.
Open the project’s Connect tab and create a token. It is shown once and sent as a bearer header, never in the URL.
Copy the command for Claude Code, a Cursor config, or a shared .mcp.json that reads the token from your environment.
The agent calls get_brand_rules, get_design_md, find_nearest_token and check_code. In CI, designlang check lints files on your machine against the project.
Stop agents inventing near-miss blues.
Make the agent’s default the system, not the previous sprint’s copy-paste.
Run Brand Check on a branch and see each off-token value with its nearest token.
Read a site’s design system from the Internet Archive and see every rebrand on a timeline.
ProA 0 to 100 score for how much of a site’s styling resolves to a design token, with a ranked fix list and a trend line.
ProScheduled checks that email you only when a confirmed design change happens.
Free accounts get 3 live runs. Pro is $9 a month with 200 credits.