菜单
Add or modify a browser-side runtime under templates/components/ (XR scene runtimes, LivePanel shared components) — injection path, load order, bundling, and the required tests. Use when touching any JS/CSS under templates/components/ or wiring a new component asset.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/aMonteSl/CodeXR --skill runtime-component命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Add or adjust supported-language coverage in CodeXR — the Python metric contract, TS language metadata, dependency-graph support, fixtures, and the analysis test matrix. Use when adding a language, changing per-language metric capabilities, or investigating language-count discrepancies.
Verify a CodeXR change before declaring it done — route to the narrowest test script for the touched area, run the npm test gate, and drive the F5/browser flow when a runtime surface changed. Use whenever a code change is about to be reported as working.
Capture the launch screenshots for the README and the website (LivePanel pages, XR scenes, guide.html) by driving a real running analysis with Playwright, reviewing every shot before keeping it. Use when asked to produce, retake or optimize any asset listed in media/SHOTLIST.md.
基于 SOC 职业分类
正在显示 SKILL.md
| name | runtime-component |
| description | Add or modify a browser-side runtime under templates/components/ (XR scene runtimes, LivePanel shared components) — injection path, load order, bundling, and the required tests. Use when touching any JS/CSS under templates/components/ or wiring a new component asset. |
templates/components/)These files are injected into user-facing generated pages — treat them like shipping frontend code. TypeScript (extension host) and runtime JS (browser) never share code; the contract is injected globals, entity attributes, and JSON data files.
templates/components/COMPONENTS.md — the authoritative inventory and recommended load order. Adding or reordering a runtime without updating it is a bug..claude/docs/XR_COMPONENTS.md for the generation pipeline (template → placeholder processing → runtime injection → per-session server).XR scenes: each runtime is inlined into generated HTML by a matching
src/code_analysis/engine/components/customComponents/*ComponentAsset.ts.
A new XR runtime needs: the JS under templates/components/codexr/<component>/, a component asset TS file that reads it, wiring where assets are injected, and a row in COMPONENTS.md at the right load position.
LivePanel shared components: files under templates/components/livepanel/ are bundled by LivePanelParser.processTemplateFiles — shared JS is concatenated ahead of the template's own script into main.js, shared CSS ahead of the template stylesheet into style.css. No component-asset file involved. Anything you put there reaches every LivePanel template (file and directory) automatically.
? characters (see V1.2.0_STATUS.md) — after bulk edits, sanity-check with node --check <file>.test/analysis/*.test.cjs that executes the browser JS directly (vm-based DOM harness for LivePanel, direct execution for XR runtimes) — follow the pattern in directoryLivePanelUi.test.cjs or codexrCommonRuntime.test.cjs.npm run test:xr-harness (Playwright). Project evolution: npm run test:project-evolution-harness.verify skill flow (npm test + npm run compile + F5 when feasible).dist/ (build-time copies of templates/).