develop-wework-plugin

# Develop a Wework plugin Treat the Wework package as the outer delivery unit. It may declare a nested Codex plugin through `wework.codexPlugin`; the Codex plugin must never own or gate the Wework plugin. ## Use the bundled development kit This Skill includes the complete public Wework extension catalog, one exhaustive smoke-test plugin, three focused API references, and three product-oriented showcase plugins: - Read [references/extension-points.md](references/extension-points.md) before choosing a UI surface. It documents descriptor fields, component props, and the browser-module boundary. - Inspect [assets/ui-extension-demo](assets/ui-extension-demo) before writing a low-level UI contribution. - Inspect [assets/reference-plugins](assets/reference-plugins) for runnable, independently installable examples of Composer augmentation, persistent workflow UI, website navigation, and typed desktop-host integration. For a left-navigation button that opens a website in the Wework built-in browser, start from `sidebar-browser-panel-demo`. Copy only the closest example into the user's writable project, then delete every contribution the plugin does not need. - Start with [assets/showcase-plugins](assets/showcase-plugins) when the user wants a product-quality example. Workspace Copilot, Test Explorer, and Dev Environments represent popular AI-assistant, testing, and development-environment categories with deliberately different interaction models. - Never ...