What problem does it solve? Shipping a Jac full-stack app to end users normally requires a running server or a heavy Electron wrapper. This Skill explains how to compile the same cl/sv source into a single native binary that embeds CPython and renders the UI in the OS-native webview, with no Rust toolchain, no Electron, and no separate backend process. ## Core Features & Use Cases - Desktop build target: Use jac build --client desktop and jac start --client desktop to produce a relocatable binary plus dist/ bundle, with a --dev HMR mode for iterating against the real desktop window. - Window and app configuration: Set binary name, identifier, version, and window geometry through the [desktop] table in jac.toml. - OS capability plugins: Call filesystem, dialogs, clipboard, notifications, window control, shell, and path APIs from cl code via the typed @jac/desktop SDK, with per-plugin security gating in [desktop.plugins]. - Use Case: You have a Jac web app and want to ship it to Linux, macOS, and Windows users as a downloadable desktop app that can save files locally and send OS notifications. ## Quick Start Ask the assistant to package your existing Jac full-stack app as a desktop binary and add a save-file dialog using the @jac/desktop fs and dialog plugins.