[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73CAM3WDZR68PWDS4EGJGF3":3,"skill-same:01M73CAM3WDZR68PWDS4EGJGF3":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M73CAM3WDZR68PWDS4EGJGF3","token-usage-lint",null,"Lint procedure that scans project UI code for hardcoded design values (raw hex colors, rgb()\u002Fhsl() literals, raw px spacing) that bypass the tokens.json SSOT. Use when: reviewing generated UI code, auditing for hardcoded design values, or checking design token compliance in playground demos and handoff artifacts.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Ftoken-usage-lint\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: token-usage-lint\ndescription: >\n  Lint procedure that scans project UI code for hardcoded design values (raw hex colors,\n  rgb()\u002Fhsl() literals, raw px spacing) that bypass the tokens.json SSOT. Use when:\n  reviewing generated UI code, auditing for hardcoded design values, or checking design\n  token compliance in playground demos and handoff artifacts.\nversion: 1.1.0\nscope: common\nstatus: active\nowner: pm\nlast_reviewed: 2026-09-06\nprerequisites: none\nrelates_to:\n  - skill: ui-ux-design-intelligence\n    type: follows\nmetadata:\n  type: review\n  triggers:\n    - token lint\n    - hardcoded color\n    - design token compliance\n    - raw hex values\n    - hardcoded spacing\n---\n\n## Context\n\n`tokens.json` is the single source of truth for the project's design language: colors, typography, spacing, radii, and shadows. `scripts\u002Fcompile-tokens.ts` compiles it into the two consumed forms, `tokens.css` (CSS custom properties such as `--color-primary`) and `tokens.ts` (typed constants plus `CSS_VARS`). Every styled surface must consume one of those forms, never a literal value. Theme presets live in the reserved top-level `themes` key (`dark`, `high-contrast`); the compiler emits each as a `[data-theme=\"\u003Cname>\"]` CSS block after `:root` plus a `themes` export in `tokens.ts` — consumers switch themes via the `data-theme` attribute, never by re-declaring values.\n\nA hardcoded palette hex (e.g. a raw `#rrggbb` value) or `padding: 12px` in a demo or prototype file forks the design language silently: it renders correctly today, but the next palette change in `tokens.json` never reaches it. This skill is the detection half of that contract. Reference implementation: the co-design variant (`templates\u002Fco-design\u002Ftokens.json` + `scripts\u002Fdesign-lint.ts`), whose playground binds demo authoring to it (\"hardcoded hex\u002Fpx values defeat the SSOT\").\n\nDecision record: closes the backlog Low row \"No token-usage lint (detecting hardcoded colors\u002Fspacing that bypass the SSOT)\" in `docs\u002Fvariant-benchmark-backlog.md` §3, closed 2026-08-25.\n\n## When to Use\n\n- After generating or editing playground code (`playground\u002Fsrc\u002Fmain.ts`, `playground\u002Fsrc\u002Fstyle.css`, `playground\u002Fsrc\u002Fdemos\u002F`)\n- Before handing off prototype code or interaction specifications to development\n- When auditing any scaffolded project for token compliance\n- Trigger phrases: \"token lint\", \"hardcoded color\", \"design token compliance\", \"raw hex values\", \"hardcoded spacing\"\n\n## Exempt Paths\n\nThe scan must exclude paths that legitimately contain raw values:\n\n| Path | Why it is exempt |\n|------|------------------|\n| `**\u002Fsrc\u002Fgenerated\u002F` | Compiler output (`tokens.css`, `tokens.ts` are regenerated here) |\n| `tokens.json` | The SSOT itself; raw values are its content |\n| Standalone `tokens.ts` \u002F `tokens.css` | Compiler outputs wherever `--output-ts` \u002F `--output-css` point |\n| `**\u002Fnode_modules\u002F` | Third-party code, not ours to lint |\n| `**\u002Fdist\u002F` | Build output, regenerated |\n\n## Execution Steps\n\n**Preferred (v1.1.0)**: run the runnable companion script, which implements the\nsame detection rules, exempt paths, and classification scheme and exits non-zero\non should-be-token findings (audit-integrable):\n\n```bash\nbun scripts\u002Fdesign-lint.ts                # default roots: .\u002Fplayground\u002Fsrc .\u002Fsrc\nbun scripts\u002Fdesign-lint.ts --dir \u003Cpath>   # explicit scan root (repeatable)\n```\n\nInline suppression for documented one-offs: append `design-token-exempt: \u003Creason>`\non the same line as the literal.\n\nThe manual grep procedure below remains valid as the fallback when the script is\nunavailable. Run from the project root (the template playground or a scaffolded project). Both shells report `file:line:match`.\n\n### Step 1: Scan for raw hex colors\n\nGit Bash:\n\n```bash\ngrep -rInE --include='*.css' --include='*.ts' --include='*.tsx' --include='*.js' --include='*.html' \\\n  --exclude-dir=generated --exclude-dir=node_modules --exclude-dir=dist \\\n  --exclude='tokens.ts' --exclude='tokens.css' --exclude='tokens.json' \\\n  '#[0-9a-fA-F]{3,8}\\b' .\n```\n\nPowerShell:\n\n```powershell\nGet-ChildItem -Recurse -Include *.css,*.ts,*.tsx,*.js,*.html |\n  Where-Object { $_.FullName -notmatch '\\\\(generated|node_modules|dist)\\\\' -and $_.Name -notmatch '^tokens\\.(ts|css|json)$' } |\n  Select-String -Pattern '#[0-9a-fA-F]{3,8}\\b'\n```\n\n### Step 2: Scan for rgb()\u002Fhsl() literals and raw px spacing\n\nRerun the same commands, replacing only the trailing pattern (identical in both shells):\n\n- Color function literals: `(rgba?|hsla?)\\(`\n- Raw px spacing: `[0-9]+(\\.[0-9]+)?px\\b`\n\n### Step 3: Verify generated outputs are current\n\nIf findings led to token changes, regenerate the compiled outputs before re-scanning:\n\n```bash\ncd playground && bun run tokens\n```\n\n`bun run tokens` wraps `bun scripts\u002Fcompile-tokens.ts --input ..\u002Ftokens.json --output-css src\u002Fgenerated\u002Ftokens.css --output-ts src\u002Fgenerated\u002Ftokens.ts`; add `--check` to the underlying script call to verify without writing.\n\n## Output Format\n\nFindings are reported as a classification table (one row per hit) followed by a summary line:\n\n```text\n| file:line                  | match              | classification      | action                          |\n|----------------------------|--------------------|---------------------|---------------------------------|\n| src\u002Fdemos\u002Fhero.tsx:14      | (raw palette hex)  | should-be-token     | -> color.primary via CSS_VARS   |\n| src\u002Fdemos\u002Fchart.ts:31      | #7b3fe4            | one-off (documented)| keep; rationale comment added   |\n| src\u002Fmain.ts:8              | href=\"#dec\"        | false positive      | none                            |\n\ntoken-usage-lint: 3 findings (1 should-be-token, 1 one-off, 1 false positive) - NEEDS REMEDIATION\n```\n\nThe summary reads `CLEAN` when no hits remain or every remaining hit is a documented one-off; otherwise `NEEDS REMEDIATION` with the should-be-token count.\n\n## Reviewing Findings\n\nClassify every hit before acting on it.\n\n**False positive (leave as is):**\n- URL fragments and anchor ids caught by the hex regex (`href=\"#dec\"`), hex-like strings in comments, and hex-looking codes in non-styling logic\n\n**Legitimate one-off (document, leave in place):**\n- Data-visualization palette extensions where a chart needs more stops than `tokens.json` defines; record the rationale in a comment next to the value\n- Third-party integration overrides that require raw values by contract\n\n**Should-be-token (remediate):**\n- Any color, spacing, radius, or shadow that mirrors an existing token or will recur across components\n- Hex\u002Fpx values inside a `var()` fallback, for example `var(--color-text, \u003Cfallback>)`: the fallback duplicates the SSOT value and drifts silently on the next recompile. In the playground `tokens.css` is always loaded, so drop the fallback; keep fallbacks only in stylesheets consumed outside the compiled-token bundle, and document each one\n\nRemediation for should-be-token findings:\n\n1. Propose the token addition in `tokens.json` under the correct group (`color`, `typography`, `spacing`, `borderRadius`, `shadow`); theme-preset additions go under the reserved `themes` key and may override `color`\u002F`shadow` only — layout tokens are theme-invariant ([DESIGN-R2])\n2. visual-designer reviews and approves the addition (see Escalation)\n3. Recompile with `bun run tokens` from `playground\u002F` (or `bun scripts\u002Fcompile-tokens.ts` with explicit `--input`, `--output-css`, `--output-ts` flags)\n4. Replace the literal with the `CSS_VARS` entry (TS\u002FTSX) or the `var(--...)` custom property (CSS\u002FHTML)\n5. Re-run Steps 1 and 2 until the scan is clean or every remaining hit is a documented one-off\n\n## Escalation\n\nThe project's token-palette owner (the visual-designer agent where the role exists, otherwise the project design owner) approves additions or changes to `tokens.json`; never edit it unilaterally to make a lint hit go away. If a hardcoded value looks intentional but undocumented, ask the palette owner to classify it before dismissing the finding.\n\n## Related Skills\n\n- **ui-ux-design-intelligence**: designs the token system this lint enforces\n- **accessibility-audit**: validates contrast after any palette change that remediation triggers\n","## Context\n\n`tokens.json` is the single source of truth for the project's design language: colors, typography, spacing, radii, and shadows. `scripts\u002Fcompile-tokens.ts` compiles it into the two consumed forms, `tokens.css` (CSS custom properties such as `--color-primary`) and `tokens.ts` (typed constants plus `CSS_VARS`). Every styled surface must consume one of those forms, never a literal value. Theme presets live in the reserved top-level `themes` key (`dark`, `high-contrast`); the compiler emits each as a `[data-theme=\"\u003Cname>\"]` CSS block after `:root` plus a `themes` export in `tokens.ts` — consumers switch themes via the `data-theme` attribute, never by re-declaring values.\n\nA hardcoded palette hex (e.g. a raw `#rrggbb` value) or `padding: 12px` in a demo or prototype file forks the design language silently: it renders correctly today, but the next palette change in `tokens.json` never reaches it. This skill is the detection half of that contract. Reference implementation: the co-design variant (`templates\u002Fco-design\u002Ftokens.json` + `scripts\u002Fdesign-lint.ts`), whose playground binds demo authoring to it (\"hardcoded hex\u002Fpx values defeat the SSOT\").\n\nDecision record: closes the backlog Low row \"No token-usage lint (detecting hardcoded colors\u002Fspacing that bypass the SSOT)\" in `docs\u002Fvariant-benchmark-backlog.md` §3, closed 2026-08-25.\n\n## When to Use\n\n- After generating or editing playground code (`playground\u002Fsrc\u002Fmain.ts`, `playground\u002Fsrc\u002Fstyle.css`, `playground\u002Fsrc\u002Fdemos\u002F`)\n- Before handing off prototype code or interaction specifications to development\n- When auditing any scaffolded project for token compliance\n- Trigger phrases: \"token lint\", \"hardcoded color\", \"design token compliance\", \"raw hex values\", \"hardcoded spacing\"\n\n## Exempt Paths\n\nThe scan must exclude paths that legitimately contain raw values:\n\n| Path | Why it is exempt |\n|------|------------------|\n| `**\u002Fsrc\u002Fgenerated\u002F` | Compiler output (`tokens.css`, `tokens.ts` are regenerated here) |\n| `tokens.json` | The SSOT itself; raw values are its content |\n| Standalone `tokens.ts` \u002F `tokens.css` | Compiler outputs wherever `--output-ts` \u002F `--output-css` point |\n| `**\u002Fnode_modules\u002F` | Third-party code, not ours to lint |\n| `**\u002Fdist\u002F` | Build output, regenerated |\n\n## Execution Steps\n\n**Preferred (v1.1.0)**: run the runnable companion script, which implements the\nsame detection rules, exempt paths, and classification scheme and exits non-zero\non should-be-token findings (audit-integrable):\n\n```bash\nbun scripts\u002Fdesign-lint.ts                # default roots: .\u002Fplayground\u002Fsrc .\u002Fsrc\nbun scripts\u002Fdesign-lint.ts --dir \u003Cpath>   # explicit scan root (repeatable)\n```\n\nInline suppression for documented one-offs: append `design-token-exempt: \u003Creason>`\non the same line as the literal.\n\nThe manual grep procedure below remains valid as the fallback when the script is\nunavailable. Run from the project root (the template playground or a scaffolded project). Both shells report `file:line:match`.\n\n### Step 1: Scan for raw hex colors\n\nGit Bash:\n\n```bash\ngrep -rInE --include='*.css' --include='*.ts' --include='*.tsx' --include='*.js' --include='*.html' \\\n  --exclude-dir=generated --exclude-dir=node_modules --exclude-dir=dist \\\n  --exclude='tokens.ts' --exclude='tokens.css' --exclude='tokens.json' \\\n  '#[0-9a-fA-F]{3,8}\\b' .\n```\n\nPowerShell:\n\n```powershell\nGet-ChildItem -Recurse -Include *.css,*.ts,*.tsx,*.js,*.html |\n  Where-Object { $_.FullName -notmatch '\\\\(generated|node_modules|dist)\\\\' -and $_.Name -notmatch '^tokens\\.(ts|css|json)$' } |\n  Select-String -Pattern '#[0-9a-fA-F]{3,8}\\b'\n```\n\n### Step 2: Scan for rgb()\u002Fhsl() literals and raw px spacing\n\nRerun the same commands, replacing only the trailing pattern (identical in both shells):\n\n- Color function literals: `(rgba?|hsla?)\\(`\n- Raw px spacing: `[0-9]+(\\.[0-9]+)?px\\b`\n\n### Step 3: Verify generated outputs are current\n\nIf findings led to token changes, regenerate the compiled outputs before re-scanning:\n\n```bash\ncd playground && bun run tokens\n```\n\n`bun run tokens` wraps `bun scripts\u002Fcompile-tokens.ts --input ..\u002Ftokens.json --output-css src\u002Fgenerated\u002Ftokens.css --output-ts src\u002Fgenerated\u002Ftokens.ts`; add `--check` to the underlying script call to verify without writing.\n\n## Output Format\n\nFindings are reported as a classification table (one row per hit) followed by a summary line:\n\n```text\n| file:line                  | match              | classification      | action                          |\n|----------------------------|--------------------|---------------------|---------------------------------|\n| src\u002Fdemos\u002Fhero.tsx:14      | (raw palette hex)  | should-be-token     | -> color.primary via CSS_VARS   |\n| src\u002Fdemos\u002Fchart.ts:31      | #7b3fe4            | one-off (documented)| keep; rationale comment added   |\n| src\u002Fmain.ts:8              | href=\"#dec\"        | false positive      | none                            |\n\ntoken-usage-lint: 3 findings (1 should-be-token, 1 one-off, 1 false positive) - NEEDS REMEDIATION\n```\n\nThe summary reads `CLEAN` when no hits remain or every remaining hit is a documented one-off; otherwise `NEEDS REMEDIATION` with the should-be-token count.\n\n## Reviewing Findings\n\nClassify every hit before acting on it.\n\n**False positive (leave as is):**\n- URL fragments and anchor ids caught by the hex regex (`href=\"#dec\"`), hex-like strings in comments, and hex-looking codes in non-styling logic\n\n**Legitimate one-off (document, leave in place):**\n- Data-visualization palette extensions where a chart needs more stops than `tokens.json` defines; record the rationale in a comment next to the value\n- Third-party integration overrides that require raw values by contract\n\n**Should-be-token (remediate):**\n- Any color, spacing, radius, or shadow that mirrors an existing token or will recur across components\n- Hex\u002Fpx values inside a `var()` fallback, for example `var(--color-text, \u003Cfallback>)`: the fallback duplicates the SSOT value and drifts silently on the next recompile. In the playground `tokens.css` is always loaded, so drop the fallback; keep fallbacks only in stylesheets consumed outside the compiled-token bundle, and document each one\n\nRemediation for should-be-token findings:\n\n1. Propose the token addition in `tokens.json` under the correct group (`color`, `typography`, `spacing`, `borderRadius`, `shadow`); theme-preset additions go under the reserved `themes` key and may override `color`\u002F`shadow` only — layout tokens are theme-invariant ([DESIGN-R2])\n2. visual-designer reviews and approves the addition (see Escalation)\n3. Recompile with `bun run tokens` from `playground\u002F` (or `bun scripts\u002Fcompile-tokens.ts` with explicit `--input`, `--output-css`, `--output-ts` flags)\n4. Replace the literal with the `CSS_VARS` entry (TS\u002FTSX) or the `var(--...)` custom property (CSS\u002FHTML)\n5. Re-run Steps 1 and 2 until the scan is clean or every remaining hit is a documented one-off\n\n## Escalation\n\nThe project's token-palette owner (the visual-designer agent where the role exists, otherwise the project design owner) approves additions or changes to `tokens.json`; never edit it unilaterally to make a lint hit go away. If a hardcoded value looks intentional but undocumented, ask the palette owner to classify it before dismissing the finding.\n\n## Related Skills\n\n- **ui-ux-design-intelligence**: designs the token system this lint enforces\n- **accessibility-audit**: validates contrast after any palette change that remediation triggers\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"relates_to":35,"description":39,"last_reviewed":40,"prerequisites":41},"pm","common","active","1.1.0",{"type":28,"triggers":29},"review",[30,31,32,33,34],"token lint","hardcoded color","design token compliance","raw hex values","hardcoded spacing",[36],{"type":37,"skill":38},"follows","ui-ux-design-intelligence","Lint procedure that scans project UI code for hardcoded design values (raw hex colors, rgb()\u002Fhsl() literals, raw px spacing) that bypass the tokens.json SSOT. Use when: reviewing generated UI code, auditing for hardcoded design values, or checking design token compliance in playground demos and handoff artifacts.\n",1788652800000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883",".hermes\u002Fskills\u002Ftoken-usage-lint",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill token-usage-lint",{"tool":56,"command":57},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill token-usage-lint",{"tool":59,"command":60},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill token-usage-lint","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.hermes\u002Fskills\u002Ftoken-usage-lint\u002FSKILL.md",true,[],[65,73,78,83,88,93],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":72},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":74,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":72},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":79,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":72},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":84,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":72},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":89,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":72},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":94,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":72},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]