Candor UI docs

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, its tier and install command, an example with the import paths an app uses, every prop, the string keys, and the rules to keep).

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 LocaleProvider string keys.

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 an app re-tokens for its brand; and how to build the screens around Candor components (surfaces, rhythm, writing, do and don't).

Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.

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 unknown, a locked control says why, nothing pre-selected, approve the exact change, reasoning is believed, the app names the agent, say what can be undone, plus status, progress and accessibility). From the candor-agent-ui skill; works with or without Candor.

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, the honesty rules that matter most on it, and a brief to hand to the coding agent that builds it.

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. With `prompt: true`, only "Give this to your agent": one block of text for adopting Candor into an app that already exists (it asks about the stack and the agent's API first, installs with the CLI, leaves the licence key to the person and names the providers to wrap the app in).

What changed in one item between two released versions, from facts only, to plan an update and write its PR: props added, removed or retyped, exports and LocaleProvider string keys added or removed, and files touched, from each release's API record; then the CHANGELOG entries in the range that name the item or its exports. Plain words first, then the same as JSON. Records start at 2.7.0: for an earlier version it says "not recorded before 2.7.0" and what is known from the first recorded release on, never a guess. `from` is the version the project has (candor-lock.json records it), and defaults to the one the server URL passes (`?kit=`, written by `npx candor-ui mcp`); `to` defaults to the latest. Example arguments: { "item": "plan", "from": "2.7.0", "to": "2.8.0" }

List every item by group (Chat, Agent work, App shell, …), or one group's items with descriptions.

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 one with get_screen.

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-line descriptions; read one with get_component_docs.

Describe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns and screens, and an install command per tier. When nothing in Candor fits, it says so rather than suggesting something close. Pass `sdk` so only your agent SDK's adapter is suggested. Read each suggestion's docs before using it.

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 pairing in light, dark and high contrast, each with its ratio and the ratio it needs; then the --cd-motion-* and --cd-sound-* values against the motion manifest; then token names and data-slot selectors against the token manifest, as warnings that don't fail the check (a --cd-* name the kit doesn't read, with the nearest one it does; a value outside a token's range; an internal --cd-* name a brand file shouldn't set; a [data-slot] selector no component renders). Call it with the file's contents after you edit candor-brand.css, and fix what it reports before you say the theme is done. Returns a short summary (failures first, with a suggested lightness that would pass; findings with file, line and the fix), then the findings as JSON (ok, motionChecked, counts, themes with every pairing, suggestions, motionAndSound.findings, tokens.findings). Anything it can't read (a color-mix(), a var(), a sound file) is reported as not measured, never as a pass. Sound files are not measured here: the server can't see your public/ folder, so `npx candor-ui theme check` in the project does that. It checks against the current kit; an older @candor-kit in the file is checked against the current names, with a note. It reads only the CSS you send, follows no @import and fetches nothing. At most 256 KB. Example arguments: { "css": ":root { --primary: oklch(0.55 0.2 260); --cd-motion-pop-dur: 140ms; }", "filename": "candor-brand.css" }