What problem does it solve?
AI assistants frequently hallucinate PICO XR APIs: inventing method names, using deprecated vibration and anchor APIs, mixing up return types, and missing mutual-exclusion constraints. This Skill anchors every PICO Unity SDK answer to the official v3.4.0 documentation so generated code compiles and runs on real devices.
Core Features & Use Cases
- Verified API Reference: Complete signature tables for the nine PXR_* core classes (PXR_Input, PXR_System, PXR_MixedReality, PXR_MotionTracking, PXR_HandTracking, PXR_Boundary, PXR_CameraImage, PXR_FoveationRendering, PXR_Enterprise) with Deprecated flags per method.
- Domain Workflows: Step-by-step integration guides for controller input, hand tracking, haptics, eye/face/body tracking, video seethrough, spatial anchors, scene capture, spatial mesh, and camera image access.
- Pitfall Blacklist: A dedicated anti-hallucination list covering deprecated APIs, semantic traps (e.g., TrackingStateCode int returns, right-handed coordinate conversion), mutual-exclusion constraints, and official documentation contradictions.
- Use Case: When asked to add haptic feedback to a PICO 4 app, the Skill directs you to PXR_Input.SendHapticImpulse/SendHapticBuffer instead of the deprecated SetControllerVibration family, with correct parameter ranges and stop semantics.
Quick Start
Ask the AI to write or review any PICO Unity SDK code, such as implementing spatial anchors or eye tracking, and it will verify every API against the v3.4.0 reference before answering.