Candor UI docs

• search_docs — Search Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list"). Returns names, tiers and one
• get_component_docs — Read one item's docs as Markdown: what it is, its tier and install command, an example with the import paths an app uses, every prop, function, type, and the Lo
• suggest_components — Describe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns, and one install command. Read each suggestion's do
• list_components — List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.
• get_pattern — Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.
• list_screens — List the screen catalogue by area (talking to the agent, approving and controlling, watching the work, …), one line per screen: what it's for and its slug. Read
• get_screen — Read one screen as Markdown: what it's for, two or three layouts with when to pick each, the Candor UI items that build each (with tiers), an install command, t
• get_started — How to install Candor UI in a React or Next.js app, render a chat, connect an agent SDK, add licensed items and keep them updated.
• get_brief — One item's brief to hand to the coding agent that builds the screen: the same Markdown the docs page's "Copy for a coding agent" button copies (what the item is
• get_design — The design system as Markdown: every colour role and what it's for, the type scale, radius, shadows, motion, density and themes, read from the shipped CSS; how
• get_review_checklist — The checklist to run after each screen where an AI agent acts, before moving on: one line per check, each tied to a rule (model output is text, unknown stays un
• theme_check — Check a brand file (candor-brand.css, or any CSS that sets Candor's tokens) the way `npx candor-ui theme check` does: colour contrast of every text and edge pai

No hidden text found in the tool definitions.

Text a person reading a tool definition does not see and a model does. Invisible characters can be pasted in by accident; this says what is there, not why. Covers tools only, not prompts or resources.