Get started
For agents
Three steps: connect, ask, check. Your agent gets the docs, the code and a reviewer.
Connect
Add the read-only MCP server to your agent.
claude mcp add --transport http dtheo https://ui.dtheo.dev/mcpAsk
Tell it to use the system. This prompt works well.
Build the run review screen with the dtheo/ui design system. Look components up with the dtheo MCP server before writing code, add them with `npx dtheo add`, use only token classes for color, and run `npx dtheo check` until it reports 0 errors.Check
It runs the design check and fixes what it finds. Add it to CI too.
npx dtheo check srcoutputsrc/run-card.tsx:14:9 error icon-button-label Icon-only button without an accessible name. → Add aria-label naming the action ("Delete run"), not the icon. 12 files checked: 1 error, 0 warnings.
What it can call
- list_components
- Every component, one line each
- get_component
- The contract: install, props, do and don’t, keyboard
- get_component_source
- The source files, ready to write
- search_docs
- Ranked matches across components, foundations and patterns
- get_tokens
- Color roles and geometry for a preset and mode
- get_guidelines
- Color, type, geometry, motion or writing rules
- check_ui_code
- Design-check findings for a snippet, with fixes
No MCP? Use these
Plain URLs any agent can read, no JavaScript needed.
- llms.txthttps://ui.dtheo.dev/llms.txtA described index of every page
- llms-full.txthttps://ui.dtheo.dev/llms-full.txtEvery page in one file
- Any page + .mdhttps://ui.dtheo.dev/docs/components/button.mdThe Markdown copy of that page
- Registryhttps://ui.dtheo.dev/r/registry.jsonEvery item, shadcn format