What problem does it solve? Working on the CODM desktop app requires navigating a strict architecture: generated Tauri config, sidecar supervision, typed Rust commands, and a decorator-free DI layer in the React console. This Skill encodes all of those rules so changes to the shell, sidecars, or OS capabilities (folder picker, notifications, badge, secrets, autostart) follow the established contracts instead of drifting. ## Core Features & Use Cases - Generated config discipline: Explains that tauri.conf.json, capabilities JSON, and shell-env.json are rendered by bun desktop:generate from packages/app/tauri/config/ and must never be hand-edited, with drift gated by tests. - Capability addition workflow: Provides the step-by-step shape for adding a native capability — port, token, Tauri/Browser/Fake service implementations, declarative registry entries, and the CAPABILITIES + CAPABILITY_PERMISSIONS map. - Sidecar and boot-failure handling: Documents port candidate resolution, readiness gates, boot-error splash behavior, and macOS signing/TCC requirements. - Use Case: When asked to add a new OS integration (e.g., a file watcher) to the desktop console, use this Skill to correctly wire the port, both platform services, the DI registry, and the generated Tauri permissions. ## Quick Start Ask the agent to add a new OS capability to the desktop console or to modify the Tauri shell, and it will follow the port-plus-platform-services pattern with generated config.