菜单
Complete an XR Blocks SDK change across implementation, runtime wiring, public exports, proof, build output, examples, and canonical documentation. Use when editing the XR Blocks repository rather than an application that consumes it.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/google/xrblocks --skill xb-contribute-sdk命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Build spatial UI in XR Blocks. Use when adding cards, overlays, panels, text, controls, model-viewer interfaces, layout, styling, themes, or UI placement with the built-in UI system.
Design and implement XR Blocks interactions. Use when adding selection, hover, direct touch, grab, gestures, event ownership, propagation, automatic manipulation, or physics-driven object behavior.
Add AI behavior to an XR Blocks application. Use when implementing Gemini or OpenAI queries, Gemini Live voice or vision, generated images, scene-grounded responses, or model-requested tools with an observable XR outcome.
基于 SOC 职业分类
正在显示 SKILL.md
| name | xb-contribute-sdk |
| description | Complete an XR Blocks SDK change across implementation, runtime wiring, public exports, proof, build output, examples, and canonical documentation. Use when editing the XR Blocks repository rather than an application that consumes it. |
Deliver a complete seam: every affected layer tells the same current story.
Read ../../AGENTS.md, record the current status and diff,
and treat existing changes as user-owned. Inspect the implementation, adjacent
tests, public entry, and nearest executable example.
Classify the change as internal, root-public, or addon-public. List the
affected configuration, runtime owner, lifecycle, cleanup, exports,
declarations, build output, tests, examples, and manual owner. Mark unused seam
elements not applicable.
Complete this step when the opening worktree is accounted for and every seam
element has an owner or an explicit not applicable decision.
Read references/seam-map.md for the selected branch.
Trace configuration to construction, registry resolution, lifecycle calls,
disposal, public entry, and emitted path. Treat
../../src/xrblocks.ts and addon public entries as
import authority. Do not expose an internal helper only because it exists.
Complete this step when every producer, prerequisite, consumer, lifecycle call, cleanup path, public entry, and emitted path is located.
Follow adjacent TypeScript and module-extension conventions. Use declared
dependencies and the registry for runtime services. Keep optional feature
defaults inert, configure permissions before XR startup, and initialize owners
before dependents. Edit source inputs and regenerate build output; do not edit
build/ by hand.
Complete this step when the production path satisfies the change contract and the diff contains no unrelated edits.
Add or adjust the smallest colocated test that fails without the change. Cover new conditions, disabled or unsupported behavior, failure behavior, cleanup, and boundary wiring when they can regress. Run the narrow test before wider checks.
Complete this step when every behavior in the contract has a named assertion through its real public or runtime boundary.
Read references/developer-surfaces.md.
Update the smallest executable sample or template when developers need a
copyable pattern. Update the one manual page that owns the concept. Update a
task skill only when the change alters that skill's process or branch choice.
Do not create a skill for a new capability alone.
Complete this step when a developer can discover one working public pattern and no affected authoritative surface teaches the previous behavior.
Run the repository checks required by AGENTS.md in proportion to the change.
Use npm run build:sdk for core SDK output and the full build when addon output
or complete packaging is affected. Build the docs when manuals, TypeDoc inputs,
sidebars, or docs components change. Inspect generated changes and compare the
final worktree to the opening snapshot.
Finish when all applicable checks pass, intended imports and declarations resolve from emitted paths, every contract row has proof, documentation matches the public implementation, and user-owned changes remain intact.
