Return the registry's manifest: schema version, registry version, project info, and configured design tool(s). Use this first to confirm a registry exists and understand what project it describes.

List all design components in the registry, optionally filtered by lifecycle status or tag. Use this to browse what already exists before proposing a new component.

Fetch a single component by its exact stable registry id. Returns an error if no such component exists.

Deterministic substring search across component id, name, aliases, tags, and description. NOT semantic/AI search — use registry_get_component or registry_find_by_design_reference when you already know an exact identifier.

Deterministically resolve a design-tool reference (e.g. a Figma fileKey/nodeId pair) to a registered component. Returns status 'resolved' with exactly one component, 'ambiguous' with all matching candidates, or 'unresolved' if nothing matches. Never guesses — if you get 'unresolved', treat the mapping as genuinely absent rather than inferring one.

List all design tokens, optionally filtered by category (color, spacing, typography, ...).

Fetch a single design token by its exact stable registry id.

List all higher-level UI patterns (e.g. empty state, search toolbar) registered in the project.

Fetch a single UI pattern by its exact stable registry id, including the components it composes.

Return the full set of structured design/engineering rules (e.g. 'prefer existing Button component', 'do not use arbitrary colors'). Read this before generating UI code to respect project-specific constraints.

Run comprehensive validation across the whole registry: duplicate ids, duplicate design references, broken cross-references (patterns/rules pointing at nonexistent components/tokens/patterns), circular pattern references, and other integrity issues. Returns valid=false with a list of issues if anything is wrong.

Create a complete starter registry (.design/registry/{manifest,components,tokens,patterns,rules}.json + README) at the resolved registry path. Fails if a registry already exists there unless force=true.

Register a brand-new design component. Fails with DUPLICATE_ID if the id already exists — use registry_update_component instead. Only propose a new component when registry_find_component / registry_find_by_design_reference confirm no equivalent component exists.

Patch an existing component by id. Only provided fields are changed; omitted fields are left as-is. Fails with NOT_FOUND if the id doesn't exist yet — use registry_create_component instead.

Mark a component as deprecated instead of deleting it. There is no destructive delete operation for components by design — history stays in git and agents can still see what a component used to map to.

Register a brand-new design token. Fails with DUPLICATE_ID if the id already exists — use registry_update_token instead.

Patch an existing token by id. Fails with NOT_FOUND if the id doesn't exist yet.

Register a brand-new higher-level UI pattern composed of one or more components.

Patch an existing pattern by id. Fails with NOT_FOUND if the id doesn't exist yet.

Replace the full set of structured design/engineering rules. This is a full-document replace (send the complete desired rule list, not a delta) so the rules file stays deterministic and diff-friendly.