PICO-Intelligent-Plugins

Use when creating or materially updating a PICO Spatial Android/Kotlin app from Figma, screenshot/mockup, PRD, intent, hybrid sources, or a bounded panel patch, and the task requires choosing or preserving container, window model, panel hierarchy, and layout regions. NOT for SDK upgrades, empty-dir bootstrap, legacy Android porting, pure code review/refactor, old-baseline D2C A/B evaluation, or performance diagnosis.

Generic pico-cli usage guide for command discovery, command-family selection, help/version/setup checks, output formats, device targeting, safe defaults, and deciding when to hand off to spatial-emulator-usage, spatial-app-perf-diagnose, spatial-app-onboarding, or lower-level adb escape hatches.

Verify-first environment workflow for environment-dependent PICO Spatial execution. Must run before tasks that actually execute pico-cli, query the pico-spatial-knowledge MCP server, install or update plugin/host integration, or start PICO emulator/device workflows, and whenever the user asks to verify, doctor, health-check, repair, set up, update, or reconnect the PICO Spatial agent environment. Reuse a successful result once per host session unless the environment may have changed. Repair commands require explicit user authorization or a task that clearly asks for setup/update/start behavior. Checks whether pico-cli exists and reports the installed version/channel state, discovers supported commands before using doctor-style checks, and explains host restart requirements.

Export an authorized Claude Code transcript and extract pico-spatial-agentic-tools skill/MCP usage records into a local support bundle.

Helps 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.

Runs an iterative PICO Spatial SDK feature-development workflow after spatial-app-onboarding handoff. Use for follow-up requirements in an existing Spatial app: inspect AGENTS.md, plan/implement one increment, build, install, launch in the PICO emulator/device, capture screenshots, check success criteria, watch for crashes/logcat, and self-repair until verified or clearly blocked.

Create, bootstrap, scaffold, or quickstart a first working PICO Spatial SDK Android/Kotlin project through `pico-cli project create`, letting the CLI own initial template selection. All generated 2D UI must be built entirely with SpatialUI (`com.pico.spatial.ui.*`) and wrapped in `PicoTheme`; Material/Material3 is forbidden. Use for empty directories, new Spatial apps, first runnable demos, 3D model starter apps, or any request to try/start/initialize a PICO Spatial project quickly.

Diagnose the performance status of Spatial App, identifying performance bottlenecks in the Android 2D drawing and PICO OS spatial engine 2D&3D rendering pipelines. Supports analyzing the entire chain from system clock, 2D drawing, 3D logic to spatial engine rendering threads, providing deep performance analysis, root cause diagnosis, and optimization suggestions based on Perfetto Trace.

Supplements pico-cli with detailed emulator and device operation guidance. Invoke when the user needs multi-step emulator, app, files, capture, or log workflows.

Day-to-day PICO Spatial SDK 3D development guide (Android/Kotlin + Spatial ECS). Covers Stage/WindowContainer, ECS entities/components/systems, resources, materials/lighting, animation, physics, interaction, coordinates/units, and performance budgets.

Plans realistic spatial layouts by measuring 3D asset bounding boxes and generating transform JSON/configuration. Use for bbox measurement, scale/position/rotation planning, or `.spatialsdk/scene_transforms.json` output.

Upgrades and migrates older PICO Spatial SDK projects to the latest PICO Spatial SDK (PICO OS 6 environment). Must be triggered whenever the user asks to "upgrade PICO SDK", "adapt to the newest Spatial SDK version", "handle Deprecated or missing spatial APIs", "fix legacy spatial container manager errors", "update PICO Gradle/AGP dependencies", or "migrate legacy Android MR/spatial apps". Do NOT trigger for general UI creation or simple bug fixes.

SpatialUI 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 questions and "not working" symptoms in any of these domains.

Hard-constraint skill for any application that uses SpatialUI in SpatialSDK to write Compose UI. Acts as the code-admission ruleset (lint-as-skill) for PicoTheme usage, theme-role routing (color / typography / disabled / hover / indication), built-in design component preference, custom-component parameter ordering, frosted-glass window background, and SpatialUI custom hover. ANY upstream skill that emits Compose code (spatial-app-onboarding, screenshot-to-spatial-app, anything-to-spatial-app, manual edits) MUST consult this skill before writing UI code. NOT for: 3D scene authoring, asset placement, performance diagnosis.