@adobe/design-data-skill 2.2.8 → 2.2.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "spectrum-design-data",
3
- "version": "2.2.8",
3
+ "version": "2.2.9",
4
4
  "description": "Read-only Spectrum lookup: find official design tokens, inspect component options, resolve values across modes, read design guidelines, and render components to SVG or PNG. Bundles the @adobe/design-data-mcp server.",
5
5
  "author": {
6
6
  "name": "Adobe"
package/.mcp.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "mcpServers": {
3
3
  "design-data": {
4
4
  "command": "npx",
5
- "args": ["-y", "@adobe/design-data-mcp@1.13.6"]
5
+ "args": ["-y", "@adobe/design-data-mcp@1.14.0"]
6
6
  }
7
7
  }
8
8
  }
package/README.md CHANGED
@@ -24,6 +24,15 @@ tools/design-data-skill/
24
24
 
25
25
  ## Installation
26
26
 
27
+ **Install it once, from one place.** The plugin is published in two marketplaces: the Design AI
28
+ Marketplace and `adobe/spectrum-design-data`. Use one. Every copy registers an MCP server and a
29
+ skill both called `design-data`, so a second copy (or a `design-data` entry in a repo's
30
+ `mcp.json` or `.github/mcp.json`) gives the client duplicates, and it may expose none of them.
31
+ If the assistant says it has no `design-data` tools, check **Customize → Installed** (Copilot app)
32
+ or `copilot plugin list` for more than one `design-data` or `spectrum-design-data` plugin, remove
33
+ the extras, and start a new session. If you install the plugin, remove any `design-data`
34
+ entry you added by hand from an MCP config.
35
+
27
36
  ### Claude Code
28
37
 
29
38
  ```
@@ -78,12 +87,27 @@ This installs only the skill. Add the MCP server to `.cursor/mcp.json` yourself:
78
87
  "mcpServers": {
79
88
  "design-data": {
80
89
  "command": "npx",
81
- "args": ["-y", "@adobe/design-data-mcp@1.13.6"]
90
+ "args": ["-y", "@adobe/design-data-mcp@1.14.0"]
82
91
  }
83
92
  }
84
93
  }
85
94
  ```
86
95
 
96
+ ## Updating
97
+
98
+ Plugins do not update themselves. After a new release, update by hand and start a new session
99
+ (Claude Code needs a restart):
100
+
101
+ * **Copilot app:** Customize → Installed → the plugin's menu → Update, or **Update all**.
102
+ * **Copilot CLI:** `copilot plugin marketplace update spectrum-design-data`, then
103
+ `copilot plugin update spectrum-design-data@spectrum-design-data`. A copy installed from the
104
+ Design AI Marketplace uses `@design-marketplace` instead.
105
+ * **Claude Code:** `claude plugin marketplace update spectrum-design-data`, then
106
+ `claude plugin update spectrum-design-data@spectrum-design-data`.
107
+
108
+ The installed version shows next to the plugin's name. The current one is in
109
+ [`package.json`](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/package.json).
110
+
87
111
  ## What the plugin includes
88
112
 
89
113
  * **Skill + MCP server.** The plugin registers the MCP server itself (`.mcp.json`);
package/llms.txt CHANGED
@@ -22,6 +22,7 @@ Also published on npm as `@adobe/design-data-skill` for versioned installs.
22
22
  - [README](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md): usage and API overview
23
23
  - [Structure](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#structure)
24
24
  - [Installation](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#installation)
25
+ - [Updating](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#updating)
25
26
  - [What the plugin includes](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#what-the-plugin-includes)
26
27
  - [Data and freshness](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#data-and-freshness)
27
28
  - [Not included](https://github.com/adobe/spectrum-design-data/blob/main/tools/design-data-skill/README.md#not-included)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@adobe/design-data-skill",
3
- "version": "2.2.8",
3
+ "version": "2.2.9",
4
4
  "description": "Read-only Spectrum design-data lookup plugin: a skill plus the bundled @adobe/design-data-mcp server",
5
5
  "type": "module",
6
6
  "files": [
@@ -34,7 +34,7 @@
34
34
  "design-data"
35
35
  ],
36
36
  "dependencies": {
37
- "@adobe/design-data-mcp": "1.13.6"
37
+ "@adobe/design-data-mcp": "1.14.0"
38
38
  },
39
39
  "devDependencies": {
40
40
  "ava": "^6.0.1"
@@ -8,8 +8,8 @@ description: >
8
8
  snapshot; it does not generate component code.
9
9
  metadata:
10
10
  author: adobe
11
- version: "2.2.8"
12
- designDataVersion: "3.16.0"
11
+ version: "2.2.9"
12
+ designDataVersion: "3.17.0"
13
13
  when_to_use: >
14
14
  Trigger on: token names (color, spacing, typography, dimension), "which token",
15
15
  "Spectrum component options", design-data primer, query tokens, suggest token,
@@ -43,7 +43,7 @@ skill was written for:
43
43
  "mcpServers": {
44
44
  "design-data": {
45
45
  "command": "npx",
46
- "args": ["-y", "@adobe/design-data-mcp@1.13.6"]
46
+ "args": ["-y", "@adobe/design-data-mcp@1.14.0"]
47
47
  }
48
48
  }
49
49
  }
@@ -70,12 +70,21 @@ Filter tokens by expression. Required: `filter` (string), e.g. `component=button
70
70
  `component=button,state=hover`, `property=*color*`, `state=hover,colorScheme=dark`.
71
71
  Filterable fields: `property`, `component`, `variant`, `state`, `colorScheme`, `scale`,
72
72
  `contrast`, `uuid`. `component` matches the tokens a component's relationships bind to.
73
- Returns an array of matching tokens (empty when none match).
73
+ Optional: `limit` (integer, default 25, max 200) and `detail` (`compact`, the default, or
74
+ `full`). Returns `{ total, shown, tokens }`. Each compact token has `name`, `value` (aliases
75
+ already followed, so there is nothing to look up by uuid), `layer`, `uuid`, and its
76
+ `colorScheme`/`scale`/`contrast` when it has them; active tokens come before deprecated ones.
77
+ When a token's value differs by a mode its name does not pin, it has `values` instead of
78
+ `value`, keyed by mode-set then mode (`values.colorScheme.dark`): use the one for the user's
79
+ mode, never the first.
80
+ When `total` is larger than `shown`, add `state=`, `property=` or `colorScheme=` to the filter
81
+ instead of raising `limit`. `detail: "full"` returns the complete token objects and is large.
74
82
 
75
83
  ### `design-data-suggest`
76
84
 
77
85
  Rank tokens against a natural-language intent. Required: `intent` (string), e.g.
78
- `"primary CTA button background color"`. Optional: `limit` (number, default 5).
86
+ `"primary CTA button background color"`. Optional: `limit` (number, default 5). Each match has
87
+ `name`, `value` (aliases followed), `layer`, `uuid`, modes and `confidence`.
79
88
 
80
89
  ### `design-data-component`
81
90
 
@@ -127,8 +136,8 @@ the SVG as a PNG.
127
136
 
128
137
  ### `design-data-font-status`
129
138
 
130
- Which font draws text in PNG renders: `{ found, fallback, using, rejected, related,
131
- help, searched }`. Optional: `fontPath` to check a specific file. Call it before a
139
+ Which font draws text in PNG renders: `{ found, fallback, using, family, installed,
140
+ rejected, related, help, searched }`. Optional: `fontPath` to check a specific file. Call it before a
132
141
  PNG when the user cares about typography, or any time a render's `font.fallback` is
133
142
  true.
134
143
 
@@ -136,15 +145,18 @@ true.
136
145
 
137
146
  PNG text uses **Adobe Clean Spectrum VF** when it is installed on the user's machine:
138
147
  the server finds it by itself in the usual font folders and in Creative Cloud's font
139
- cache, so there is nothing to ask the user for. When it is not installed, the server
140
- draws text in a bundled open font (Source Sans 3) and says so.
148
+ cache, so there is nothing to ask the user for. Order: Adobe Clean Spectrum VF Roman
149
+ (`.ttf`), then Adobe Clean VF Roman (`.ttf`), then a bundled open font (Source Sans 3).
150
+ Adobe Clean Serif VF, Italic and `.otf` files are never used.
141
151
 
142
152
  Follow the status, not a guess:
143
153
 
144
154
  * `font.found` is `true`: the real font was used. Do not tell the user to download or
145
155
  install anything.
146
- * `font.fallback` is `true`: say that the text is drawn in a similar open font and may
147
- differ slightly in width, and do not call the image exact. Then pass on `font.help`.
156
+ * `font.fallback` is `true`: name the font actually used (`font.family`, `font.using`; it
157
+ is Adobe Clean VF when `font.installed` is `true`, else bundled Source Sans 3), say its
158
+ metrics, spacing and wrapping may differ from Adobe Clean Spectrum VF, and do not call
159
+ the image exact. Then pass on `font.help`.
148
160
  For an Adobe employee that means: download `AdobeCleanSpectrumVF-Roman.ttf` from the
149
161
  Brand Center (<https://inside.corp.adobe.com/content/inside/en/brand-center/font.html>,
150
162
  employees only) and install it (double-click the file). If they are not at Adobe they
@@ -152,8 +164,8 @@ Follow the status, not a guess:
152
164
  * `font.rejected` lists files that were found but cannot be used (for example the `.otf`
153
165
  version: only the `.ttf` file works, and the Italic file is not used for upright
154
166
  text). Tell the user which file and why.
155
- * `font.related` lists other Adobe Clean fonts on the machine. Creative Cloud's "Adobe
156
- Clean" is a different font from Adobe Clean Spectrum VF and is not used.
167
+ * `font.related` lists other Adobe Clean fonts on the machine. Creative Cloud's static
168
+ "Adobe Clean" is a different font and is not used.
157
169
  * The user says the font is installed but `found` is `false`: ask for the file's full
158
170
  path and pass it as `fontPath`. To make it permanent, they set `DESIGN_DATA_FONT` to
159
171
  that path in the MCP server's `env` (in the MCP configuration), or pick the file in the