pico-spatial-app-designerUse when the user asks to design, review, repair, or produce a PICO spatial app design package from requirements, prior design facts, or delivery specs, or when an upstream app-generation workflow needs a no-visual requirement converted into an accepted design package before code generation. NOT for
porting-android-appHelps migrate a traditional Android 2D application to a Spatial platform such as PICO OS, covering architecture preparation, Spatial SDK integration, container migration, UI adaptation, Spatial capabilities, and cross-platform compatibility.
spatial-accessibilityOperate PICO Spatial apps through published Accessibility semantics and author or audit their contracts. Use when requesting natural-language actions or supported business goals on 2D controls, 2.5D panels or 3D Entities. NOT for reactive gameplay or command discovery; use pico-cli for command disco
spatial-app-dev-workflowGuides PICO Spatial SDK app development from a new idea or an existing project through design, implementation, verification, and delivery. Use when building an app, adding features, repairing behavior, or continuing development; covers direct execution and an explicitly selected managed dev workflow
spatial-app-onboardingUse when creating or repairing the first runnable PICO Spatial SDK Android/Kotlin project, independently or as a caller's scaffold subtask. Covers project creation, configuration and initial build/install/launch evidence. NOT for full product delivery or post-scaffold feature work; use spatial-app-d
spatial-app-performance-analysisRouting Skill for PICO OS6 performance analysis, using SKILL.md as the routing protocol layer to select reference workflows such as Spatial, Binder, Memory, or CPU scheduling based on user symptoms and evidence. Applicable to performance issues like jank, dropped frames, Late/Miss/Discard Frame, bin
spatial-app-performance-workflowEntry Skill for PICO Spatial performance investigation, capture, Trace analysis, source repair, and end-to-end diagnosis. Use for jank, frame drops, high CPU/GPU load, performance input preparation, native pico-cli perf workflows, or the Craft adapter. Route deeper evidence interpretation to spatial
spatial-bundle-scene-readerRead an existing Spatial Editor .scenes.json and .bundle handoff on demand. Use when inspecting packed scenes, entry scenes, entity names, parent scopes, bounded subtrees, transforms, or manifest-to-runtime addressing. NOT for scene authoring or repackaging (spatial-editor), SDK component API guidan
spatial-design-to-appUse when a PICO Spatial app task needs UI design interpretation, Figma or screenshot extraction, container/window decisions, Compose restoration, or visual verification. Also supports the existing standalone UI workflow when explicitly selected. NOT for owning general application delivery; use spati
spatial-editorRun managed Spatial Editor workflows for scenes, assets, materials, review and packaging. Use only when the user's prompt or an upstream app agent's delegation prompt explicitly requests a Spatial Editor workflow (spatial-editor-workflow), or to continue an already authorized Run. NOT for requests m
spatial-sdk-guidelineFocused PICO Spatial SDK API and diagnostic guide (Android/Kotlin + Spatial ECS). Covers container choices, ECS concepts, resources, rendering, interaction, coordinates/units, and performance constraints; routes Kotlin Entity scene delivery to Scene Builder.
spatial-sdk-scene-builderImplements and repairs code-owned Entity scenes in a PICO Spatial Android/Kotlin app, including loading, hierarchy, transforms, placement, alignment, clipping, and validation. For app-level delivery, use spatial-app-dev-workflow as the development backbone and apply this skill to the current scene i
spatial-sdk-updateUpgrades existing PICO Spatial/MR projects to a newer PICO Spatial SDK and PICO OS 6-compatible toolchain. Trigger for SDK/BOM, Gradle/AGP/Kotlin/NDK, deprecated or missing Spatial APIs, legacy spatial container managers, or compatibility migration in a project that is already Spatial/MR. Do NOT tri
spatial-ui-abilitySpatialUI spatial-capability code assistant. Provides production-ready Kotlin snippets for spatial gestures, Vibrant materials, hover effects, windowConstraints, depth/3D layout, glass backgroundMaterial, Z-axis offsets, 3D transforms, and Augment/TabBar/Toolbar/Subwindow. Trigger for both API quest
spatial-ui-design-styleUse when any upstream workflow emits or edits SpatialUI Compose UI code and needs PicoTheme, SpatialUI built-in components, theme role routing, hover/haptics, glass background, Material bans, or design-style verifier admission. This is a mandatory Compose UI sub-contract, not a primary app-generatio
spatialml-debuggingDebug Kotlin PICO Spatial SDK SpatialML apps, pipelines, and operators using service logcat events and global tensor readback. Use for SecureMR/OpenMR runtime failures, blank inference output, zero or stale tensors, operator errors, debug.pico.spatialml.debug, verbose service logging, readback permi
spatialmlCreate, extend, author, and validate SpatialML features in Kotlin Spatial SDK apps; route Unity implementation to PICO Unity Agentic Tools. Use for SpatialML/SecureMR/OpenMR setup, custom pipelines/packages, Pipeline Zoo, operator selection, LiteRT/TFLite inference, camera-to-model graphs, tensor sy
threejs-to-spatialConvert native Three.js projects into PICO Spatial SDK spatial apps. Use when migrating Three.js, WebGL, or WebXR frontend projects. Do not use for React Three Fiber or existing Spatial app patches.