What problem does it solve?
Shared UI code in OpenChamber runs across web, Electron, VS Code, hosted-mobile, and Capacitor runtimes, and hardcoding URLs, credentials, or one runtime's transport assumptions breaks portability and security. This Skill provides the decision rules and reference maps needed to route every API call through the correct abstraction.
Core Features & Use Cases
- Call Classification: Routes official OpenCode endpoints through the
@opencode-ai/sdk/v2 client, OpenChamber HTTP routes through runtimeFetch, and runtime-owned capabilities through the RuntimeAPIs contract.
- Runtime Parity Guidance: Defines explicit behavior for web, Electron, VS Code, hosted-mobile, and Capacitor, including stable unsupported responses instead of silent fallbacks.
- Auth and URL Safety: Enforces scoped short-lived URL tokens for browser-owned assets and forbids long-lived credentials in URLs.
- Use Case: When adding a new shared UI feature that fetches data, use this Skill to decide whether the call belongs in the SDK client,
runtimeFetch, or a new RuntimeAPIs capability, then implement it consistently across all runtimes.
Quick Start
Ask the agent to add a new OpenChamber API route and wire it into the shared UI following the ui-api-decoupling rules.