Before calling any skill in this module: if you are about to call a skill with parameters guessed from its name or description, STOP — read this file (or fetch its schema via
GET /skills/recommend?includeSchema=true) first. If you already have the parameter definitions from recommend/schema, you may proceed straight to dryRun.
Triggers
- Writing or reviewing PICO Unity Integration SDK (
PXR_*/Pico.Platform) code - Setting up a PICO XR project or choosing the Unity OpenXR plugin route
- Video seethrough / spatial anchors / spatial mesh / SecureMR / platform services
- Migrating from SDK 2.x or an older 3.x version
- Write or review PICO Unity SDK code, configure a PICO project or the OpenXR route, passthrough/anchors/mesh/SecureMR/platform services, 2.x→3.x version migration
Advisory module. All rules are distilled from PICO official documentation v3.4.0(full crawl on 2026-08-13: 203 guide pages + 32 API reference pages + 14 version release notes + API snapshot diffs for 8 versions). The SDK is closed-source, and anchoring is done viaofficial documentation URLs—every rule is clickable for verification. The body text is in Chinese; API names remain in English.
Mode: Documentation only—no REST skills to gate on; can be loaded freely under any mode: Approval / Auto / Bypass.
Why this module is needed
PICO knowledge in AI training corpora largely remains at SDK 2.x / early 3.x: old haptics interfaces, the three-part AnchorEntity event pattern,PXR_SDK > menu,PXR_EyeTracking class... these were deprecated or renamed in 3.4.0. A single version, 3.2.0, deprecated 30 members of PXR_Input and 27 members of PXR_MotionTracking. Writing PICO code from memory = high probability of hallucination.Before generating any PICO code, load the corresponding sub-document of this module first.
Critical Rule Summary (cross-domain highest priority; remember these even before reading sub-documents in detail)
| # | Rule | See |
|---|---|---|
| 1 | PICO XR plugin and Unity OpenXR pluginchoose one of the two: if both are checked, only PICO XR takes effect; on the OpenXR route, checking other vendors' plugins will prevent the app from running | SETUP.md |
| 2 | PXR_Manager must be attachedevery scene(including loading scenes); SDK 3.1.0 and later support only 64-bit (IL2CPP + ARM64 only), and the Unity menu is PICO not PXR_SDK |
SETUP.md |
| 3 | PXR_MotionTracking family methods return an int status code(0 for success), not bool;SetFoveationLevel takes two parameters and None = -1 |
API_REFERENCE.md |
| 4 | the entire old haptics interface group (SetControllerVibration / StartVibrateBy* / CreateHapticStream etc.) was deprecated in 3.2.0 → current SendHapticImpulse |
VERSIONS.md |
| 5 | the entire MR family (anchors/scene calibration/plane detection) requires StartSenseDataProviderbefore operations; anchor handles become invalid after restart, so across sessions you can only store UUID; to delete an anchor, UnPersist first, then Destroy |
MR.md |
| 6 | Four prerequisites for video passthrough: disable post-processing, disable HDR under Vulkan, Clear Flags=Solid Color, background RGBA all 0;EnableVideoSeeThrough takes effect with a delay and must be called again after resume |
MR.md |
| 7 | Controllers and bare handscannot be tracked simultaneously(Controller And Hands is automatic switching); full-body motion capture and motion trackers are independently tracked and mutually exclusive | INTERACTION.md |
| 8 | Platform services:CoreService.AsyncInitialize check two layers (IsError + Success/AlreadyInitialized); rooms/matching/leaderboards/achievements also require GameInitialize |
PLATFORM.md |
| 9 | Face tracking in v3.4.0 is anofficial contradiction zone: the API taught in the guide is already marked Deprecated in the same version, and the corpus has no replacement class—it can still be used but its status should be noted,do not invent new APIs | PITFALLS.md |
| 10 | Rendering mutual-exclusion matrix: AppSW×BufferDiscards=tearing, AppSW×content protection=ghosting, LateLatching×composition layer=jitter, supersampling×sharpening on the same Buffer only supersampling takes effect | RENDERING.md |
Sub-doc Routing
| Sub-document | When to read |
|---|---|
| SETUP.md | Environment setup, dual-plugin route selection, project settings, AndroidManifest, Project Validation, Building Blocks, AR Foundation, tools and samples index |
| RENDERING.md | FFR/ETFR, super resolution/sharpen, composition layers (Overlay/Underlay), multiview, adaptive resolution, AppSW, Late Latching, URP, spatial audio, performance targets |
| INTERACTION.md | Controller input mapping, haptic feedback, hand/eye/face/body tracking, motion trackers, system keyboard, relationship with XRI |
| MR.md | Video see-through, spatial anchors (including shared), spatial mesh, scene calibration, plane detection, MR safety protection, spatial data permissions, dual camera image routes, 2.5→3.x MR migration |
| SECUREMR.md | SecureMR framework (3.2.0+): Tensor/Operator/Pipeline concepts, gltf rendering, Dynamic Texture, Readback, JavaScript Operator |
| PLATFORM.md | Platform services essentials: initialization, accounts/friends, achievements, leaderboards, IAP, DLC, cloud saves, rooms & matchmaking, RTC, content protection, enterprise services overview |
| API_REFERENCE.md | XR Core 9 categories method-by-method signature table (including Deprecated markers),PXR_Enterprise method domain list, Legacy API disposition |
| VERSIONS.md | Version timeline (v2.0.1→v3.4.0), per-version method-level API addition/removal/deprecation table, 2.x→3.x migration points——the deprecation list uses this file as the single source of truth |
| PITFALLS.md | Hallucination trap master switch: deprecated API blacklist, signature semantic traps, mutual exclusion matrix, build traps, list of contradictions in the official documentation itself, capability boundaries |
Routing to Other Modules
- General XR Interaction Toolkit interaction (rig/grab/teleport/XR UI) → xr(this module only covers PICO-specific parts)
- Architecture and lifecycle decisions → architecture / patterns / async
- Performance review hot paths → performance
- URP asset and render pipeline operations → urp / graphics feature modules
Version Scope
Anchored to v3.4.0(launched 2026-02-27, captured 2026-08-13). The documentation site supports version switching: 3.4.0 / 3.3.2 / 3.3.0 / 3.2.0 / 3.1.0 / 3.0.5 / 3.0.0 / 2.5.0; release notes cover up to v2.0.1. Key watersheds:
- 3.0.0: MR interfaces fully refactored (AnchorEntity event-based →
*Async+ SenseDataProvider） - 3.1.0: menu
PXR_SDK→PICO; only supports 64-bit apps - 3.2.0: the largest deprecation wave in history (PXR_Input 30 members, PXR_MotionTracking 27 members, PXR_System face/brightness group); SecureMR debuts
- 3.3.0：
PXR_Over Lay→PXR_Composition Layer; some APIs moved across classes to PXR_Enterprise - 3.4.0: plane detection,
PXR_CameraImage(user device camera data), SecureMR JavaScript Operator
For how to update the corpus after a new SDK version is released, see memory:temp/pico-crawl/ just rerun the script.
Iron rules for use
- Before writing PICO code, first read the corresponding sub-document;for APIs not found in the corpus, rather declare "not documented in the official documentation" than fill them in from memory。
- The official documentation itself has contradictions (face tracking, XRI version wording, SecureMR dual naming)——for handling contradiction areas see PITFALLS.md Section 5, do not trust a single page only.
- For version migration questions, always first check VERSIONS.md the method-level addition/removal table before answering.