AI and MCP

Agents write better code when they install the real component instead of recreating it from memory. Blank gives them three ways in.

Copy prompt

Every component, block and docs page has a Copy prompt button next to its title. It copies a short brief for your agent: what the item is, the registry entry for components.json, the install command with the right namespace, the import line with the exact exported names, and a link back to the page. Paste it into Claude Code, Cursor, Codex or v0 and add what you want built.

Prompts for Pro items tell the agent to read the key from BLANK_LICENSE_KEY and to ask you for it rather than invent one.

llms.txt

/llms.txt is a plain-text index of the whole site in the llmstxt.org format: every docs page, every component and block with its tier, a one-line description and the install command. Point an agent at it when it needs to choose between components:

Read https://useblank.design/llms.txt and pick the Blank components for a
settings page with a profile form and a danger zone.

The index is generated from the same registry files the CLI installs from, so it lists new items the day they ship.

shadcn MCP server

The shadcn CLI includes an MCP server that can search registries, read items and install them. It uses the registries in your components.json, so once @blank (and @blank-pro) are listed there it can reach every Blank item:

npx shadcn@latest mcp init --client claude

Supported clients include claude, cursor, vscode and codex. After a restart, ask for what you need — "install the Blank login block and wire it to our auth action" — and the agent finds and installs it.

Conventions to tell your agent

If your agent writes components on top of Blank, these two rules keep the output on-system:

• Use shadcn's names: variant, size, asChild, and the same part structure (Card, CardHeader, CardContent).
• Colour through roles only: bg-primary, text-muted-foreground, bg-item-secondary, text-brand. No hex values, no Tailwind palette classes.