Token group names only — the cheapest way to orient before fetching values.

Return only the requested token group (and theme for color). Avoids shipping the whole system.

Resolve a single token by name (e.g. "accent2", "space.4", "radius.md") to its value(s) + canonical CSS var, theme-aware for color.

Emit the whole token set as ready-to-use css | json | scss | tailwind. Dual-theme, self-consistent with scaffold_component variable names.

Every component id + purpose + domain + regulatory flags, optionally filtered by domain.

Full contract: purpose, props, whenToUse/whenNot, a11y, regulatory anchors, tokens, dataContract.

The data shape + required render states (loading / empty / error / stale) for a component.

The four-cell register (when to use / when not & instead / behaviour & a11y / regulatory) — the line between a kit and a system.

Ranked keyword search across id, domain, regulatory, purpose, whenToUse. Returns ids + purpose + score.

Find every component that serves a given rule (e.g. "FINRA 2111", "NACHA", "SEC 17a-4"). Compliance-driven discovery.

Describe a use case in natural language; get ranked component recommendations, each with its whenNot warning so the agent avoids misuse.

Resolve requires transitively and return a dependency-ordered set (deps first) plus the union of tokens + regulatory anchors. For composing a surface.

Generate a paste-ready, method-compliant skeleton (ds-section HTML + scoped tokens-only CSS + delegated reduced-motion-safe JS + the four-cell register) from a component contract. The killer tool: the agent gets correct structure, not invented structure.

Validate a proposed usage against the system: token names must resolve, render states must be canonical, and CSS must be tokens-only (no hardcoded hex/rgb, no inline styles). Returns issues by severity.

Static accessibility audit of a component against its contract: a11y contract present, error state declared (status in words not colour alone), every colour token defined for both themes in lock-step, reduced-motion guard, regulatory anchor — plus a per-token contrast read in both themes. Verifies the contract, not a running DOM.

The WCAG 2.1 contrast ladder for the token set in both themes (or one): foreground tokens over backgrounds with AA / AA-large / AAA classification and a failures list. The machine version of the Accessibility Lab contrast checker.

Map a jurisdiction (us | eu | uk | au | sg | jp | global) and optional feature keywords to the regulatory anchors and guardrail components PRESENT in this design system. A coverage map for design, not legal advice.

Assemble a multi-component flow from a list of ids: dependency-resolved order (deps first), per-step decision register, and the union of tokens + regulatory anchors across the flow. For building a KYC / order / onboarding surface end to end.

Generate a dependency-free, runnable contract-conformance smoke test for a component (tokens resolve, states canonical, regulatory anchors intact, a11y contract passes, scaffold CSS tokens-only). Ships the test discipline with the component.

Version + per-file SHA-256 checksums for sync verification.

Given a consumer version, report whether a newer contract exists so it pulls only the delta. Auto-sync primitive.

The Edwson operating contract — the nine non-negotiables + verification gates that every component and scaffold satisfies. The Ed-agent in machine-readable form.

System overview: version, component + domain counts, regulatory-framework coverage, token count.

The Consumer Design System (B2C sibling, 118 categories / 11 domains incl. a 22-entry AI & Agents domain). List entries — id, name, domain, platform anchor, canonical URL — optionally filtered by domain (e.g. "ai", "commerce", "growth").

One consumer entry with its bundle obligations attached (what it requires, what requires it). The when-not-to cell of the register at url is binding.

Keyword search across consumer names, summaries, domains and anchors, e.g. "paywall", "child", "cancel".

Regulation-first discovery over the consumer catalogue: "COPPA" / "GDPR Art 7" / "FTC" / "WCAG" / "EU AI Act" returns the entries (and hard rules) that answer to it. Start from the rule, not the widget.

Bundled-by-contract pairs (paywall→cancellation, UGC→report & block, checkout→order tracking, agent-confirm→agent-trace). All of them, or the obligations of one id — include them unprompted.

The consumer system's machine-carried reading logic: the seven-step read path (discover → fetch index → select → read register → resolve bundles & hard rules → build from tokens → gate to a human) plus the hard rules that can BLOCK a build.