@adobe/design-data-agent-mcp 0.0.0-size-token-taxonomy-20260929225107

package/.claude-plugin/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "design-data-agent",
+  "description": "Spec-conformant design token lookup, validation, diff, and authoring for any dataset via the design-data CLI.",
+  "author": {
+    "name": "Adobe"
+  },
+  "homepage": "https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-agent-mcp",
+  "repository": "https://github.com/adobe/spectrum-design-data",
+  "license": "Apache-2.0"
+}

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "{}"
+replaced with your own identifying information. (Don't include
+the brackets!)  The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright 2026 Adobe
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,168 @@
+# `@adobe/design-data-agent-mcp`
+
+MCP server and Claude Code skill for the [Spectrum Design Data](../../packages/design-data/) agent surface. Read tools (`primer`, `resolve_token`, `query_tokens`, `describe_component`, `describe_guideline`, `list_guidelines`) run fully in-process via `@adobe/design-data-wasm` — no CLI binary required for those. Only `authoring_session_step_intent` still invokes the native binary (for NLP suggest ranking, not yet on the wasm surface).
+
+## Install
+
+### Claude Code (skill + optional MCP)
+
+Add the Spectrum Design Data marketplace, then install the spec-generic skill:
+
+```
+/plugin marketplace add adobe/spectrum-design-data
+/plugin install design-data-agent@spectrum-design-data
+```
+
+For Spectrum tokens with zero setup (embedded snapshot), install `design-data@spectrum-design-data` instead — see [`tools/design-data-skill/`](../design-data-skill/).
+
+### Cursor (skill)
+
+Cursor Settings → Rules → **Add Rule** → **Remote Rule (GitHub)** → paste:
+
+```
+https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-agent-mcp/skills/design-data
+```
+
+### npm (MCP server)
+
+```sh
+npx @adobe/design-data-agent-mcp@latest
+```
+
+The `@adobe/design-data` CLI binary is **only** needed for `authoring_session_step_intent`. All other tools run in-process. Set `DESIGN_DATA_BIN` if the binary is not on `PATH`.
+
+### Staying current
+
+The embedded Spectrum snapshot is baked into the wasm at build time and travels with the
+package version — there's no separate data update to run. Pin `@latest` (as above) so `npx`
+fetches the newest published version rather than reusing whatever it last cached; `-y` alone
+only skips the install confirmation, it doesn't force a re-fetch. Already on `/plugin`? Run
+`/plugin update design-data-agent@spectrum-design-data`. Call the primer tool and check
+`provenance.designDataVersion` to see which dataset version is embedded. The primer tool
+also does a best-effort check against the latest published `@adobe/spectrum-design-data`
+version — if the embedded dataset is behind, it adds a `provenance.datasetStatus` field and
+logs a one-line warning to stderr. This is silent on any network failure (offline/air-gapped
+use is unaffected); set `DESIGN_DATA_SKIP_VERSION_CHECK=1` to disable the check entirely.
+
+## MCP server
+
+Configure your MCP client to run:
+
+```sh
+npx -y @adobe/design-data-agent-mcp@latest
+```
+
+Or from a repo clone:
+
+```bash
+node tools/design-data-agent-mcp/src/index.js
+```
+
+### Environment variables
+
+| Variable                 | Default       | Description                                                                    |
+| ------------------------ | ------------- | ------------------------------------------------------------------------------ |
+| `DESIGN_DATA_BIN`        | `design-data` | Path to the `design-data` binary (authoring only)                              |
+| `DESIGN_DATA_ROOT`       | —             | Absolute root that relative paths are anchored to                              |
+| `DESIGN_DATA_PATH`       | `.`           | Dataset root path                                                              |
+| `DESIGN_DATA_COMPONENTS` | —             | Override components directory                                                  |
+| `DESIGN_DATA_GUIDELINES` | —             | Override guidelines directory                                                  |
+| `DESIGN_DATA_FIELDS`     | —             | Override fields directory                                                      |
+| `DESIGN_DATA_SCHEMAS`    | —             | Override schema path (for `validate`)                                          |
+| `DESIGN_DATA_EXCEPTIONS` | —             | Override exceptions path (for `validate`)                                      |
+| `DESIGN_DATA_CONFIG`     | —             | Path to a `.design-data.toml` (or its directory) to resolve a platform cascade |
+
+> **Platform cascade.** If `DESIGN_DATA_CONFIG` is set, the server shells out to
+> the `design-data` CLI once at startup (`design-data query --filter "" --format
+> json`, run from the config's directory) to resolve its `.design-data.toml`
+> source (path/npm/github/git) and any top-level `manifest` cascade, then
+> materializes the result to a temp dir and points `primer` / `resolve_token` /
+> `query_tokens` / `validate_usage` / `describe_component` /
+> `describe_guideline` / `list_guidelines` at it instead of the embedded
+> Spectrum snapshot. Component, relationship, and guideline catalogs are copied
+> from the fallback dataset and overlaid with platform manifest extensions. If
+> resolution fails
+> (e.g. no network for a github source), the server logs a warning and falls
+> back to the embedded/local dataset rather than crashing.
+
+> **Path resolution.** The MCP client launches this server with the working
+> directory inherited from wherever the editor was opened — which may be a
+> subdirectory of your repo (e.g. `sdk/`), not the repo root. To stay independent
+> of that working directory, each data path is resolved in this order:
+>
+> 1. **Explicit env override.** If `DESIGN_DATA_PATH` / `DESIGN_DATA_COMPONENTS` /
+>    `DESIGN_DATA_FIELDS` is set, it is used. Relative values are anchored to
+>    `DESIGN_DATA_ROOT` (absolute, recommended when launching via `npx`) or, if
+>    that is unset, to the server package's own location in the monorepo. Absolute
+>    values are used as-is.
+> 2. **Resolved `@adobe/spectrum-design-data` package** (zero config). When no env
+>    override is set, the server resolves the installed `@adobe/spectrum-design-data`
+>    package via Node module resolution and reads its `tokens/`, `components/`, and
+>    `fields/` directories. In a pnpm workspace this follows the symlink to
+>    `packages/design-data`; when published it uses the installed dependency. This
+>    is independent of the working directory.
+> 3. **Fallback.** `dataPath` falls back to the (anchored) current directory; the
+>    component/field overrides fall back to `null` (not supplied), which means
+>    `describe_component` / `describe_guideline` will throw an error if
+>    `@adobe/spectrum-design-data` is not resolvable.
+>
+> In a monorepo checkout you typically need no `DESIGN_DATA_*` env vars at all —
+> resolution via the workspace package handles it.
+
+### Example (Cursor `.cursor/mcp.json`)
+
+```json
+{
+  "mcpServers": {
+    "design-data-agent": {
+      "command": "npx",
+      "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
+      "env": {
+        "DESIGN_DATA_ROOT": "/abs/path/to/your/repo",
+        "DESIGN_DATA_PATH": "packages/design-data/tokens",
+        "DESIGN_DATA_COMPONENTS": "packages/design-data/components",
+        "DESIGN_DATA_FIELDS": "packages/design-data/fields"
+      }
+    }
+  }
+}
+```
+
+### Example (Claude Desktop `claude_desktop_config.json`)
+
+```json
+{
+  "mcpServers": {
+    "design-data-agent": {
+      "command": "npx",
+      "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
+      "env": {
+        "DESIGN_DATA_BIN": "design-data",
+        "DESIGN_DATA_PATH": "/path/to/your/dataset"
+      }
+    }
+  }
+}
+```
+
+## Tools exposed
+
+| Tool                 | Description                                                     |
+| -------------------- | --------------------------------------------------------------- |
+| `primer`             | Load full token taxonomy, component list, and field definitions |
+| `resolve_token`      | Resolve a token property to its literal value                   |
+| `query_tokens`       | Filter tokens by expression                                     |
+| `describe_component` | Fetch component schema and token bindings                       |
+| `describe_guideline` | Fetch guideline documentBlocks content and metadata             |
+| `list_guidelines`    | List guideline slugs and metadata, optionally by category       |
+| `validate_usage`     | Validate token usage and return a diagnostic report             |
+| `diff_datasets`      | Compare two datasets and return a semantic diff                 |
+| `write`              | Write agent-generated product context to the dataset            |
+
+## Skill
+
+The Claude Code skill lives at [`skills/design-data/SKILL.md`](skills/design-data/SKILL.md). It shells out to `npx @adobe/design-data` for validate, query, resolve, diff, and write operations against local datasets.
+
+## License
+
+Apache-2.0

package/package.json

@@ -0,0 +1,57 @@
+{
+  "name": "@adobe/design-data-agent-mcp",
+  "version": "0.0.0-size-token-taxonomy-20260929225107",
+  "description": "MCP server and Claude Code skill for the design-data agent surface — read tools run in-process via wasm",
+  "type": "module",
+  "main": "./src/index.js",
+  "bin": {
+    "design-data-agent-mcp": "./src/index.js"
+  },
+  "files": [
+    "src/",
+    ".claude-plugin/",
+    "skills/",
+    "README.md",
+    "LICENSE"
+  ],
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/adobe/spectrum-design-data.git",
+    "directory": "tools/design-data-agent-mcp"
+  },
+  "bugs": {
+    "url": "https://github.com/adobe/spectrum-design-data/issues"
+  },
+  "homepage": "https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-agent-mcp#readme",
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org/",
+    "provenance": true
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.27.1",
+    "@adobe/design-data": "0.0.0-size-token-taxonomy-20260929225107",
+    "@adobe/design-data-wasm": "0.0.0-size-token-taxonomy-20260929225107",
+    "@adobe/spectrum-design-data": "0.0.0-size-token-taxonomy-20260929225107"
+  },
+  "devDependencies": {
+    "ava": "^6.0.1"
+  },
+  "engines": {
+    "node": ">=20.12.0"
+  },
+  "keywords": [
+    "mcp",
+    "design-system",
+    "design-tokens",
+    "design-data",
+    "agent-surface",
+    "cli"
+  ],
+  "author": "Adobe",
+  "license": "Apache-2.0",
+  "scripts": {
+    "start": "node src/index.js",
+    "test": "ava"
+  }
+}

package/skills/design-data/SKILL.md

@@ -0,0 +1,184 @@
+---
+name: design-data-agent
+description: >
+  Validate, query, resolve, diff, and author spec-conformant design tokens and components using the
+  design-data MCP tools against a local dataset. Use when the user asks about design tokens, a design
+  system, token lookup, spec-conformance, drift detection, or token authoring on custom data.
+metadata:
+  author: adobe
+  version: "1.11.0"
+when_to_use: >
+  Trigger on: design system, design tokens, spec-conformant, drift, validate tokens, token
+  authoring, custom dataset, DESIGN_DATA_PATH, design-data validate, design-data diff,
+  design-data write, product-context.json.
+allowed-tools: mcp__design-data-agent__primer, mcp__design-data-agent__query_tokens, mcp__design-data-agent__resolve_token, mcp__design-data-agent__describe_component, mcp__design-data-agent__validate_usage, mcp__design-data-agent__diff_datasets, mcp__design-data-agent__write, mcp__design-data-agent__start_authoring_session, mcp__design-data-agent__authoring_session_step_intent, mcp__design-data-agent__authoring_session_step_classification, mcp__design-data-agent__authoring_session_step_values, mcp__design-data-agent__authoring_session_commit, mcp__design-data-agent__authoring_session_cancel, mcp__design-data-agent__authoring_session_get, mcp__design-data-agent__authoring_session_list
+---
+
+# design-data agent skill
+
+`@adobe/design-data-agent-mcp` provides in-process wasm tools for validating, querying,
+resolving, diffing, and authoring spec-conformant tokens and components from any dataset
+on the local filesystem.
+
+Set two path variables once and reference them throughout:
+
+```bash
+export DESIGN_DATA_PATH=./packages/design-data/tokens
+export DESIGN_DATA_SPEC_PATH=./packages/design-data
+```
+
+For Spectrum tokens with zero setup (embedded snapshot), use the `design-data` skill instead — this skill targets custom or repo-local datasets.
+
+## Bootstrap
+
+Add `@adobe/design-data-agent-mcp` to your `.cursor/mcp.json`:
+
+```json
+{
+  "mcpServers": {
+    "design-data-agent": {
+      "command": "npx",
+      "args": ["-y", "@adobe/design-data-agent-mcp@latest"],
+      "env": {
+        "DESIGN_DATA_PATH": "./packages/tokens/src",
+        "DESIGN_DATA_COMPONENTS": "./packages/design-data/components",
+        "DESIGN_DATA_FIELDS": "./packages/design-data/fields"
+      }
+    }
+  }
+}
+```
+
+Adjust paths to match your dataset layout. Pin `@latest` — the embedded Spectrum snapshot is
+baked into the wasm at build time and travels with the package version, so there's no separate
+data update to run, but plain `npx -y <pkg>` (no tag) can reuse a cached older build.
+
+***
+
+## Session start — call `primer` first
+
+Call `primer` at the start of every session that touches design data. It returns the active
+dimensions, component list, taxonomy fields, and token count — structural context that scopes
+all subsequent lookups. No inputs required.
+
+***
+
+## Token lookup
+
+### Resolve a token to its literal value — `resolve_token`
+
+Required: `property` (string) — the bare `name.property` segment, e.g. `"background-color"`
+or `"corner-radius"` (see `primer().properties` for the full list). **Not** a flattened
+legacyKey like `"accent-background-color-default"` — that form never resolves.
+Optional context: `colorScheme` (`"light"` or `"dark"`), `scale` (`"desktop"` or `"mobile"`),
+`contrast` (`"regular"` or `"high"`). Optional narrowing: `component`, `variant`, `state`, and
+`colorRole`. Set `excludeDeprecated` to omit tokens with `lifecycle.deprecatedIn`.
+
+> **Gotcha:** when several tokens share a property, use `variant`, `state`, or `colorRole` to
+> narrow the match, then check `ambiguous` and `deprecated` on the result. `component` is
+> sparsely populated in the current dataset, so prefer the other fields when available.
+> `resolve_token` still uses cascade ranking when multiple candidates remain; use `query_tokens`
+> to inspect the full candidate set.
+
+### Query tokens by filter expression — `query_tokens`
+
+Required: `filter` (string)
+
+Valid filter keys: `property`, `component`, `variant`, `state`, `colorScheme`, `scale`,
+`contrast`, `uuid`, `$schema`.
+
+Filter syntax examples:
+
+```
+property=background-color
+property=*background*
+property=background-color|property=border-color
+$schema=https://spectrum.adobe.com/page/design-token/
+```
+
+> **Gotcha:** `component=<id>` currently always returns `[]` — tokens aren't
+> component-indexed in this dataset. Use `describe_component` to see a component's known
+> token bindings instead.
+
+> **Exit codes:** `0` = matches found; empty array = no matches (not an error).
+
+***
+
+## Component info — `describe_component`
+
+Required: `id` (string) — kebab-case component ID, e.g. `button`, `action-button`
+
+Returns the component contract: `name`, `displayName`, `options`, `anatomy`, `states`,
+and `tokenBindings`.
+
+***
+
+## Validation — `validate_usage`
+
+Optional inputs:
+
+* `path` — dataset path (defaults to `DESIGN_DATA_PATH`)
+* `strict` (boolean) — treat warnings as errors
+* `schema_path` — override schemas directory (defaults to `@adobe/spectrum-tokens` schemas)
+
+Runs Layer-1 JSON-Schema structural validation and Layer-2 relational rules.
+Returns `{ valid, errors, warnings }`.
+
+> **Note:** `--exceptions-path` (SPEC-007 naming allowlist) is not supported in the
+> in-process path. Use the `design-data` CLI directly if you need exceptions support.
+
+***
+
+## Dataset diff — `diff_datasets`
+
+Required: `oldPath`, `newPath`
+Optional: `filter` (substring to narrow results by token name)
+
+Returns `{ renamed, deprecated, reverted, added, deleted, updated }`.
+
+***
+
+## Product-layer authoring — `write`
+
+Write or update the product context document in the dataset.
+
+Optional inputs: `output` (defaults to `$DESIGN_DATA_PATH/product-context.json`),
+`rationale` (string)
+
+***
+
+## Token authoring session
+
+Use the following tools in sequence to create a new token through the wizard:
+
+1. **`start_authoring_session`** — start a session (returns `session_id`)
+2. **`authoring_session_step_intent`** — provide natural-language intent; get token suggestions
+3. **`authoring_session_step_classification`** — set layer, property, name fields
+4. **`authoring_session_step_values`** — set mode-specific value rows
+5. **`authoring_session_commit`** — validate and write the token to disk
+6. **`authoring_session_cancel`** — cancel without writing
+
+Helper tools: `authoring_session_get` (inspect state), `authoring_session_list` (all active sessions).
+
+`authoring_session_commit` accepts an optional `schema_path` to override the schemas directory
+for Layer-1 JSON-Schema validation before writing.
+
+> **Note:** `authoring_session_step_intent` (NLP suggestion ranking) still delegates to the
+> `design-data` CLI because the NLP `suggest` API is not yet on the wasm surface.
+
+***
+
+## Gotchas
+
+* **Scale values:** `desktop` and `mobile` — not `medium`/`large`.
+* **Contrast values:** `regular` and `high` — not `standard`/`high`.
+* **`query_tokens` returns `[]`** when no tokens match — not an error.
+* **`diff_datasets` filter** matches by token name substring (case-insensitive).
+
+## When working in Cursor
+
+Cursor Settings → Rules → **Add Rule** → **Remote Rule (GitHub)** → paste this URL:
+
+```
+https://github.com/adobe/spectrum-design-data/tree/main/tools/design-data-agent-mcp/skills/design-data
+```