[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0AWA0J1JEYCB6MB9WPRW8":3,"skill-same:01M7F0AWA0J1JEYCB6MB9WPRW8":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7F0AWA0J1JEYCB6MB9WPRW8","design-system",null,"Workspace styling and UI-structure standards. Use for any UI work in \u002FUsers\u002FFord\u002Fworkspace, including CSS, Tailwind, colors, spacing, type, radius, light and dark themes, app layout or sidebars, new pages or components, component folder structure, restyling an app, or moving an app onto the shared tokens.","Codecaine-AI\u002Fdesign-system","Codecaine-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F268717725?v=4","01M7F0A67C4WQDS26TV514BNDF","Codecaine AI","01M7F0A681XQZRHSV0TNKWXNNZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fskill\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: design-system\ndescription: Workspace styling and UI-structure standards. Use for any UI work in \u002FUsers\u002FFord\u002Fworkspace, including CSS, Tailwind, colors, spacing, type, radius, light and dark themes, app layout or sidebars, new pages or components, component folder structure, restyling an app, or moving an app onto the shared tokens.\nmetadata:\n  version: \"0.1.0\"\n---\n\n# Design System\n\n`\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system` (`@codecaine-ai\u002Fdesign-system`) is the one source of truth for how every Codecaine and Lascari AI app looks and is laid out. Read its `AGENTS.md` before UI work.\n\n## Style UI\n\n1. Style only with tokens: `var(--ds-*)` in CSS, the utilities from `@codecaine-ai\u002Fdesign-system\u002Ftailwind.css` (Tailwind v4), or `cssVar()` and `tokens` from `@codecaine-ai\u002Fdesign-system` in JS. With `tailwind.css`, `dark:` follows `data-theme`, not the OS.\n2. Use the semantic roles (surface, text, border, fill, accent, link, status). Use hue tokens only for categorical color. Text uses `link`, never `accent`. `dist\u002Fguide\u002Ftokens.md` lists every token, and the docs page `docs\u002F30-guide\u002F10-tokens` gives the rules.\n3. Never hard-code a color, size, spacing, radius, font, shadow, duration or z-index. Never copy token values into an app. In Tailwind, never use Tailwind's own scales (`bg-red-500`, `text-sm`, `shadow-md`, `rounded-lg`). New apps import `tailwind-strict.css` before `tailwind.css`, so those utilities don't generate at all.\n4. Check light and dark: set `data-theme=\"dark\"` on `\u003Chtml>`.\n5. Scan the folders you touched with `bun \u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system\u002Fscripts\u002Fscan-literals.ts \u003Cdir>`. A new hard-coded literal is a bug.\n\n## Build a New App or Screen\n\n1. Use the app shell in the docs page `docs\u002F30-guide\u002F20-layout`: a collapsible left sidebar (`⌘\\` toggles it and the state persists), a topbar with the page title and actions, content in lanes, and an optional inspector. Start from `templates\u002Freact-app-shell\u002F` for React, or from the markup in `docs\u002F30-guide\u002F20-layout`.\n2. Organize code by vertical slice, as the docs page `docs\u002F30-guide\u002F30-code-structure` describes. Every component is a folder, `_components\u002F\u003CName>\u002Findex.tsx`. Its parts go in its own `_components\u002F`. Keep breaking components down. Move shared code up to the nearest common ancestor.\n\n## Change the Look\n\n1. Edit `tokens\u002F`. Never edit `dist\u002F`.\n2. In `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system`, run `bun run build`, `bun run check` and `bun run test`.\n3. Open `dist\u002Fguide\u002Findex.html` and check light and dark. Every connected app picks up the change.\n\n## Connect an App\n\n- **Inside Codecaine Core:** add `\"@codecaine-ai\u002Fdesign-system\": \"workspace:*\"` to the package, then run `bun install` at the Core root. Core's `workspaces` already lists `design-system` (the folder sits inside Core), so the link is live.\n- **Another local bun app:** add the relative path to the root `workspaces` and depend on `workspace:*`, or use `bun link`. That gives a live link. Avoid a bun `file:` dependency: bun links it file by file at install time, so files added later (new outputs) are missing until someone reruns `bun install`.\n- **npm apps:** use a `file:` dependency, which npm links live, or `@import` the CSS by relative path.\n- **Apps built on Vercel, Railway or Docker:** vendor a packed copy. Run `bun run pack --out ..\u002F\u003Capp>\u002Fvendor` in design-system (`--out` is relative to the design-system folder) and depend on `file:vendor\u002F\u003Ctgz name>`. Repack after a token change.\n- **Load order:** `@codecaine-ai\u002Fdesign-system\u002Ffonts.css`, then `tokens.css` (`tokens-dark-first.css` on a dark-first surface), then `layout.css`. Agent-viewer hosts add `host-contract.css` after the tokens. For Tailwind v4, `tailwind-strict.css` comes before `tailwind.css`; Tailwind v3 apps use the `tailwind-v3-preset` export as a preset.\n- The docs page `docs\u002F30-guide\u002F40-consume` has the full recipe, including the Vite settings.\n\n## Check an App\n\nRun these in `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system`. `--root` defaults to the workspace that holds it: `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases`, three levels up.\n\n1. Find the app's entry in `apps.json`: repo, wiring, entry stylesheet, scan paths, literal floor, run profile and routes. After you change an entry, run `bun run registry:check`.\n2. Run `bun run lint:apps \u003Capp>` (add `--pass \u003Cn>` to check one migration pass). It prints one line per violation and exits 0 when the app is wired and conformant.\n3. Run `bun run verify:apps \u003Capp>`. It starts the app under its run profile and proves in a browser that it renders from the tokens in light and dark.\n4. Run `bun run test:apps \u003Capp>` for the app's tests (add `--commands typecheck,build` for those; a command the entry does not set is skipped). It runs them under the run profile and the sandbox, fails on a write into the app's own checkout, and compares the results with the baselines in `apps.json`. Never run an app's tests or commands directly.\n5. Run `bun run use:app --app \u003Capp>` to use the app under its run profile. It visits every route in each theme, runs the route's steps, toggles the sidebar and hovers buttons and links. It clicks only the registry's route steps, which the managing agent reviews, and the sidebar toggle. A guard checks each click and key press as a second line of defence: it refuses a submit control, anything in a form, a control whose label names a write, and any key but Tab, Escape, the arrows, PageUp\u002FPageDown, Home\u002FEnd and a plain Enter or Space. It exits 1 on a console error, a failed or blocked request, a refused step, or a change to the app's checkout, and prints the path of its JSON log.\n6. Never start the app outside its run profile. `verify:apps`, `snapshot`, `test:apps` and `use:app` start and stop it for you.\n7. The app passes when every gate its `apps.json` entry marks required passes: lint, verify, tests, snapshot and pixel diff.\n8. `bun run progress` writes one page with every app's status and literal count.\n\n## Move an Existing App\n\n`apps.json` holds each app's registry entry, and `bun run progress` reports each app's pass status. The migration waves are finished. Move tokens first, then the shell, then the code structure, one app per change:\n\n1. Capture the before state: `bun run snapshot --app \u003Cid> --set before`.\n2. Run `bun run codemod:literals --app \u003Cid> propose`, mark the rows you accept `\"approve\": \"yes\"`, then run `bun run codemod:literals apply --table \u003Cmapping.json>`.\n3. Wire the CSS (`docs\u002F30-guide\u002F40-consume`) and fix what is left until `lint:apps --pass \u003Cn>` and `verify:apps --pass \u003Cn>` both pass, and `test:apps \u003Cid>` shows no failure beyond the baseline.\n4. Run `bun run snapshot --app \u003Cid> --set after`, then `bun run snapshot:sheet --app \u003Cid> --a before --b after` (and `snapshot:diff` with the same flags) to prove the change.\n","# Design System\n\n`\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system` (`@codecaine-ai\u002Fdesign-system`) is the one source of truth for how every Codecaine and Lascari AI app looks and is laid out. Read its `AGENTS.md` before UI work.\n\n## Style UI\n\n1. Style only with tokens: `var(--ds-*)` in CSS, the utilities from `@codecaine-ai\u002Fdesign-system\u002Ftailwind.css` (Tailwind v4), or `cssVar()` and `tokens` from `@codecaine-ai\u002Fdesign-system` in JS. With `tailwind.css`, `dark:` follows `data-theme`, not the OS.\n2. Use the semantic roles (surface, text, border, fill, accent, link, status). Use hue tokens only for categorical color. Text uses `link`, never `accent`. `dist\u002Fguide\u002Ftokens.md` lists every token, and the docs page `docs\u002F30-guide\u002F10-tokens` gives the rules.\n3. Never hard-code a color, size, spacing, radius, font, shadow, duration or z-index. Never copy token values into an app. In Tailwind, never use Tailwind's own scales (`bg-red-500`, `text-sm`, `shadow-md`, `rounded-lg`). New apps import `tailwind-strict.css` before `tailwind.css`, so those utilities don't generate at all.\n4. Check light and dark: set `data-theme=\"dark\"` on `\u003Chtml>`.\n5. Scan the folders you touched with `bun \u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system\u002Fscripts\u002Fscan-literals.ts \u003Cdir>`. A new hard-coded literal is a bug.\n\n## Build a New App or Screen\n\n1. Use the app shell in the docs page `docs\u002F30-guide\u002F20-layout`: a collapsible left sidebar (`⌘\\` toggles it and the state persists), a topbar with the page title and actions, content in lanes, and an optional inspector. Start from `templates\u002Freact-app-shell\u002F` for React, or from the markup in `docs\u002F30-guide\u002F20-layout`.\n2. Organize code by vertical slice, as the docs page `docs\u002F30-guide\u002F30-code-structure` describes. Every component is a folder, `_components\u002F\u003CName>\u002Findex.tsx`. Its parts go in its own `_components\u002F`. Keep breaking components down. Move shared code up to the nearest common ancestor.\n\n## Change the Look\n\n1. Edit `tokens\u002F`. Never edit `dist\u002F`.\n2. In `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system`, run `bun run build`, `bun run check` and `bun run test`.\n3. Open `dist\u002Fguide\u002Findex.html` and check light and dark. Every connected app picks up the change.\n\n## Connect an App\n\n- **Inside Codecaine Core:** add `\"@codecaine-ai\u002Fdesign-system\": \"workspace:*\"` to the package, then run `bun install` at the Core root. Core's `workspaces` already lists `design-system` (the folder sits inside Core), so the link is live.\n- **Another local bun app:** add the relative path to the root `workspaces` and depend on `workspace:*`, or use `bun link`. That gives a live link. Avoid a bun `file:` dependency: bun links it file by file at install time, so files added later (new outputs) are missing until someone reruns `bun install`.\n- **npm apps:** use a `file:` dependency, which npm links live, or `@import` the CSS by relative path.\n- **Apps built on Vercel, Railway or Docker:** vendor a packed copy. Run `bun run pack --out ..\u002F\u003Capp>\u002Fvendor` in design-system (`--out` is relative to the design-system folder) and depend on `file:vendor\u002F\u003Ctgz name>`. Repack after a token change.\n- **Load order:** `@codecaine-ai\u002Fdesign-system\u002Ffonts.css`, then `tokens.css` (`tokens-dark-first.css` on a dark-first surface), then `layout.css`. Agent-viewer hosts add `host-contract.css` after the tokens. For Tailwind v4, `tailwind-strict.css` comes before `tailwind.css`; Tailwind v3 apps use the `tailwind-v3-preset` export as a preset.\n- The docs page `docs\u002F30-guide\u002F40-consume` has the full recipe, including the Vite settings.\n\n## Check an App\n\nRun these in `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases\u002Fcodecaine\u002Fcore\u002Fdesign-system`. `--root` defaults to the workspace that holds it: `\u002FUsers\u002FFord\u002Fworkspace\u002Fcodebases`, three levels up.\n\n1. Find the app's entry in `apps.json`: repo, wiring, entry stylesheet, scan paths, literal floor, run profile and routes. After you change an entry, run `bun run registry:check`.\n2. Run `bun run lint:apps \u003Capp>` (add `--pass \u003Cn>` to check one migration pass). It prints one line per violation and exits 0 when the app is wired and conformant.\n3. Run `bun run verify:apps \u003Capp>`. It starts the app under its run profile and proves in a browser that it renders from the tokens in light and dark.\n4. Run `bun run test:apps \u003Capp>` for the app's tests (add `--commands typecheck,build` for those; a command the entry does not set is skipped). It runs them under the run profile and the sandbox, fails on a write into the app's own checkout, and compares the results with the baselines in `apps.json`. Never run an app's tests or commands directly.\n5. Run `bun run use:app --app \u003Capp>` to use the app under its run profile. It visits every route in each theme, runs the route's steps, toggles the sidebar and hovers buttons and links. It clicks only the registry's route steps, which the managing agent reviews, and the sidebar toggle. A guard checks each click and key press as a second line of defence: it refuses a submit control, anything in a form, a control whose label names a write, and any key but Tab, Escape, the arrows, PageUp\u002FPageDown, Home\u002FEnd and a plain Enter or Space. It exits 1 on a console error, a failed or blocked request, a refused step, or a change to the app's checkout, and prints the path of its JSON log.\n6. Never start the app outside its run profile. `verify:apps`, `snapshot`, `test:apps` and `use:app` start and stop it for you.\n7. The app passes when every gate its `apps.json` entry marks required passes: lint, verify, tests, snapshot and pixel diff.\n8. `bun run progress` writes one page with every app's status and literal count.\n\n## Move an Existing App\n\n`apps.json` holds each app's registry entry, and `bun run progress` reports each app's pass status. The migration waves are finished. Move tokens first, then the shell, then the code structure, one app per change:\n\n1. Capture the before state: `bun run snapshot --app \u003Cid> --set before`.\n2. Run `bun run codemod:literals --app \u003Cid> propose`, mark the rows you accept `\"approve\": \"yes\"`, then run `bun run codemod:literals apply --table \u003Cmapping.json>`.\n3. Wire the CSS (`docs\u002F30-guide\u002F40-consume`) and fix what is left until `lint:apps --pass \u003Cn>` and `verify:apps --pass \u003Cn>` both pass, and `test:apps \u003Cid>` shows no failure beyond the baseline.\n4. Run `bun run snapshot --app \u003Cid> --set after`, then `bun run snapshot:sheet --app \u003Cid> --a before --b after` (and `snapshot:diff` with the same flags) to prove the change.\n",{"name":5,"metadata":24,"description":7},{"version":25},"0.1.0","main","4f1968a236954ebf51a67404a07f38619b1f4bae","skill","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system","https:\u002F\u002Fgithub.com\u002FCodecaine-AI","https:\u002F\u002Fwww.codecaine.ai\u002F","A software design studio. High-craft tools for people who care how software feels.","2026-11-07 06:01:02",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Codecaine-AI\u002Fdesign-system --skill design-system",{"tool":40,"command":41},"bunx","bunx skills add Codecaine-AI\u002Fdesign-system --skill design-system",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Codecaine-AI\u002Fdesign-system --skill design-system","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fskill\u002FSKILL.md",true,[],[49,56,63,70,75],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7F0ATVN9K63AF1J9H6AQJM3","beta","Drafts a commit message from a staged diff.","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fapps\u002Ffixtures\u002Fagent-skills-manager\u002Fskills\u002Fmy-skills\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7F0ASCXH0MRFJT79ECWQ1KJ","gamma","Summarizes a test run into a short report.","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fapps\u002Ffixtures\u002Fagent-skills-manager\u002Fskills\u002Flibrary\u002Fexample\u002Fgamma\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7F0ARBPS1TGTPJ54KRJW7A4","alpha","Formats release notes from a changelog.","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fapps\u002Ffixtures\u002Fagent-skills-manager\u002Fskills\u002Flibrary\u002Fexample\u002Falpha\u002FSKILL.md",[],[],{"skillNo":71,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7F0APJ5PFTQCJEV2P442KD0","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fapps\u002Ffixtures\u002Fagent-skills-manager\u002Fskills\u002Factive\u002Fbeta\u002FSKILL.md",[],[],{"skillNo":76,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7F0AMXTZ3EGQHZG9AD5005F","https:\u002F\u002Fgithub.com\u002FCodecaine-AI\u002Fdesign-system\u002Fblob\u002Fmain\u002Fapps\u002Ffixtures\u002Fagent-skills-manager\u002Fskills\u002Factive\u002Falpha\u002FSKILL.md",[],[]]