Templates
Minimal starting points for building on Cowork Studio — the same seven scaffolds the IDE's Create dialog offers, documented. Open any template for its explanation, preview, and the code it actually creates; then create it in Cowork, edit the files and make it yours, the way you'd copy a component from a component library.
Three building blocks: Apps (.jsx frontends rendered in the sidebar, workbench tabs, or modals), Routines (.ts backend scripts run by the local daemon, optionally driving the Cowork Browser), and Skills (SKILL.md instructions the workspace's AI agents load).
Apps
Skills
Installation
Templates live inside Cowork Studio's Create dialog. In your workspace, open
Manage Workspace, click a tab's
Add button (Add Component, Add Database, …), pick a
template and give it a name — the files land in your workspace, wired into
.cowork/project.json, ready to edit.
Apps land under Cowork/<name>/, routines under
Cowork/Routines/, skills under
Skills/<name>/. Everything is plain files —
open them, change them, make them yours.
Team Servers
When your customized template is worth sharing, publish it to a team server. A team server is the sharing boundary: its admins publish apps, routines, and workspaces to its store, and anyone who joins can install them in a click — and gets told when a newer version ships.
cowork publish --team-server my-teamPackaging turns your files into an installable bundle; publishing pushes it to the team server's store. Start from any template, customize it, and ship it back to your members the same way you installed it.