dsh-claude-design-system 2.7.2 → 2.8.0

package/NOTICE.md

@@ -11,6 +11,7 @@ Copyright (c) 2026 Jim Liu 宝玉, under the MIT License in [LICENSE](LICENSE):
 - The local tooling: each skill's `scripts/artifact.mjs` and, where there is one, `scripts/server.mjs` (the command line and the local editor server), the local comments, and what lets the editors run on a local machine instead of claude.ai.
 - The DeepSeek Harness plugins' own code and files: `dsh-plugins/*/lib/`, `cordis.patch.yml`, `locale/`, `docs/` and `icon.svg`.
 - The parts of the skills' text written for local agents: how to open and run the editors, local paths and files, comments.
+- A skill whose `license:` line says plain MIT is wholly the maintainer's work: all of its files are MIT.
 - The READMEs, the changelogs, the images in `assets/` and the files in `.github/`.
 - The maintainer's tools in `archive/baoyu-design/agents/`, apart from the open-source code vendored there (section 3).
 
@@ -43,7 +44,7 @@ If you hold rights in anything here and want it credited differently, changed or
 
 本仓库（以及 npm 上的 DeepSeek Harness 插件）里的内容分三类，许可各不相同。[LICENSE](LICENSE) 里的 MIT 许可只管第一类。
 
-1. **维护者自己写的部分，MIT。** 本地命令行和编辑器服务器（各技能的 `scripts/artifact.mjs`，以及有的技能带的 `scripts/server.mjs`）、本地评论、让编辑器离开 claude.ai 在本机运行的那部分代码；DeepSeek Harness 插件自己的代码和文件（`dsh-plugins/*/lib/`、`cordis.patch.yml`、`locale/`、`docs/`、`icon.svg`）；技能说明里为本地 Agent 写的部分；README、更新日志、`assets/` 里的图片、`.github/`；`archive/baoyu-design/agents/` 里维护者写的工具。
+1. **维护者自己写的部分，MIT。** 本地命令行和编辑器服务器（各技能的 `scripts/artifact.mjs`，以及有的技能带的 `scripts/server.mjs`）、本地评论、让编辑器离开 claude.ai 在本机运行的那部分代码；DeepSeek Harness 插件自己的代码和文件（`dsh-plugins/*/lib/`、`cordis.patch.yml`、`locale/`、`docs/`、`icon.svg`）；技能说明里为本地 Agent 写的部分；`license:` 一行只写 MIT 的技能，整个是维护者写的，它的全部文件都是；README、更新日志、`assets/` 里的图片、`.github/`；`archive/baoyu-design/agents/` 里维护者写的工具。
 2. **取自 Anthropic 的部分，不适用 MIT。** 权利归 Anthropic。除 frontend-design 外，Anthropic 没有为这些内容公开许可，本项目也不授予任何许可。包括：
    - 各 `skills/claude-*/SKILL.md` 所改编的 Artifact 类型技能说明；
    - `artifact-type/reference/` 里的参考文档；

package/lib/client.js

@@ -1,4 +1,4 @@
-// dsh-claude-design-system 2.7.2: built from baoyu-design.
+// dsh-claude-design-system 2.8.0: built from baoyu-design.
 window.__ModuleLoader__.load({
 	id: "dsh-claude-design-system",
 	factory: (require) => {

package/lib/index.js

@@ -1,4 +1,4 @@
-// dsh-claude-design-system 2.7.2: built from baoyu-design.
+// dsh-claude-design-system 2.8.0: built from baoyu-design.
 var define_PLUGIN_default = { name: "claude-design-system", provider: "dsh-claude-design-system", skills: [{ name: "claude-design-system", description: "Create and revise design systems in the Design System artifact format (project/design-system.json, tokens.json, a README brand book, component previews, fonts and asset groups) as local files, then open them in a local design-system page where the user can browse and edit tokens, type, components and assets. Use when the user asks for a design system or brand kit in this format, built from a code repository, a design tool or scratch, names claude-design-system or the Design System type, or wants to revise a folder that holds project/design-system.json. claude-slides and claude-design install these systems. A free-form HTML style guide, UI kit or token page is baoyu-design's.", comments: true }] };
 
 import { spawn as spawn2 } from "node:child_process";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-claude-design-system",
-  "version": "2.7.2",
+  "version": "2.8.0",
   "description": "DeepSeek Harness plugin: the claude-design-system skill from baoyu-design. The agent writes design systems (tokens, type, components, assets) as files and opens them in a local design-system page.",
   "keywords": [
     "dsh",

package/skills/claude-design-system/SKILL.md

@@ -163,7 +163,7 @@ leave alone stays as it is, and removing a file is deleting it. The rest goes th
 - `upload <root> <file> --group <Group>` → `{url:"/_blob/<id>", record, indexPath, shownAs, …}`: stores a copy as `project/_blobs/<id>.<ext>`; the same bytes always get the same id. Write `record` into the index at `indexPath` (with the index, LAST). `<root>` must exist.
 - `check <root>` → `problems` (0: done); `issues` (each a `file` under `project/` and its fix) and `notes`, each when any; it exits 1 while any problem remains. The generated files and whether previews render are not checked.
 - `list [dir …]` → the design systems in the working directory (or the folders given, and those in `$CLAUDE_DESIGN_SYSTEMS`), each `{title, namespace, folder, root, readme, tokens}`.
-- `open <root>` → `{url, pid, stop, …}`: starts the page on this machine in the background (once; later calls reuse it, `reused: true`) and prints its address, 127.0.0.1:4730 (the next free port up when 4730 is taken; `--port n` starts from n, `--port 0` takes any). `stop <root>` ends it (`serve <root>` runs it in the foreground instead). The page saves the user's edits (and the generated files) into the same folder, and shows yours as soon as you write them. `.artifact-server.json` and `.artifact-server.log` beside `project/` are its own: leave them; so is `comments.json` (the comments, see Comments), which only the comment commands below change.
+- `open <root>` → `{url, pid, stop, …}`: starts the page on this machine in the background (once; later calls reuse it, `reused: true`) and prints its address, `http://127.0.0.1:4730/design-system/<id>/`. All the systems open on this computer share one server and port (4730, the next free port up when that is taken; `--port n` looks for it at n and starts from n, `--port 0` runs a server of its own on any port), each at its own path, which stays the same from one start to the next. `stop <root>` takes this one off, and the server ends with the last (`serve <root>` runs it in the foreground instead). The page saves the user's edits (and the generated files) into the same folder, and shows yours as soon as you write them. `.artifact-server.json` and `.artifact-server.log` beside `project/` are its own: leave them; so is `comments.json` (the comments, see Comments), which only the comment commands below change.
 - `share <root>` (or `open <root> --lan`): opens the page to the local network and prints a link per role (Sharing, below).
 - `archive <root> [--out file.zip|dir]` → `{file, files, bytes, open}`: the whole folder, history and comments too, as one zip beside it (`--out`: another file or folder), to back it up, move it to another computer or send it to someone; unzipped anywhere, `open` carries on. The owner's Download folder button in the page (between History and Share) does the same. The server's own files and the share links stay out.
 
@@ -247,12 +247,12 @@ People comment in the open editor: Comment (or C), then a click on a token, colo
 
 ## Sharing
 
-`share <root>` opens the system to the local network (the same Wi-Fi or LAN, as `http://<this computer's address>:4730/`), starting the server if it isn't running, and prints a link per role: `editor` edits and comments, `commenter` comments without editing, `viewer` only looks. `open <root> --lan` (or `serve --lan`) shares it as it starts.
+`share <root>` opens the system to the local network (the same Wi-Fi or LAN, as `http://<this computer's address>:4730/design-system/<id>/`), starting the server if it isn't running, and prints a link per role (the other systems on the same server stay closed to the network): `editor` edits and comments, `commenter` comments without editing, `viewer` only looks. `open <root> --lan` (or `serve --lan`) shares it as it starts.
 
 - The person at this computer is the owner: everything, plus the Share button in the bar across the top of the page, next to the comments button (the links, the people who joined and who is online, each one's role, sharing on or off). On this computer (`127.0.0.1`) they stay the owner even when they open a link; a link opened at the network address shows what that role sees.
 - Give the person the links to pass on. Whoever opens one types a name and is in as that role; what they change and comment lands in the same folder as the owner's. The links survive a restart while the server gets its port back; if not, `share <root>` prints the new ones to give out again.
 - Guests have a Share button too. It holds the links they may pass on, their own role's and the ones below it (an editor's has all three, a commenter's the commenter and viewer links, a viewer's the viewer link), and Copy link for the page's address, which only people who already have access can open. Whoever joins through a guest's link shows in the owner's panel like anyone else; turning links off, resetting them, changing roles and removing people stay the owner's.
-- `share <root> --disable <role>` / `--enable <role>` turns a link off or on (`<role>`: one, `editor,viewer`, or `all`); off, it holds everyone who came by it until it is on again. `--reset <role>` gives the role a new link: the old one stops working and the people who came by it are out. `--role <guest>=<role>` gives someone who joined another role (`<guest>`: an id from the `guests` it prints). `--off` stops sharing on the network.
+- `share <root> --disable <role>` / `--enable <role>` turns a link off or on (`<role>`: one, `editor,viewer`, or `all`); off, it holds everyone who came by it until it is on again. `--reset <role>` gives the role a new link: the old one stops working and the people who came by it are out. `--role <guest>=<role>` gives someone who joined another role (`<guest>`: an id from the `guests` it prints). `--off` stops sharing on the network, and only `share <root>` alone opens it: the link options leave it shared or not as it was.
 - Who is here: while someone else has the system open, their avatars sit before History (who, not where on the page). After you change a file you show there as Agent for about 20 s.
 - Only the owner's page sends to you (Send to Agent); what guests comment is saved for you to read with `comments <root>`.
 - The links and the people who joined are in `<root>/.sharing.json`: leave it. It is plain http on the local network: anyone there can read what passes, and a link is the permission: whoever has one gets its role, so send each only to the people meant to have it, and `--reset` a role's link that went further (the Share panel says so too). When this computer has a Tailscale address (100.64.0.0/10), `share` also prints `tailscale`: the same links at that address, for people on the owner's tailnet from any network (the Share panel: Copy Tailscale link in a link's More menu). Nothing else reaches past the local network; there is no tunnel.