Content Library
Admin is where you publish the agent content your organization wants every member to use. Content is versioned in the cloud and synced to the CLI/IDE cache — it is not checked into each git worktree by default.
What you can publish
| Type | Purpose |
|---|---|
| Skills | Packaged agent capabilities members can invoke |
| Commands | Slash-command prompt templates |
| Hooks | Event-driven agent hooks (command or prompt), with fail-closed options |
| Architecture rules | Standards the agent follows |
| Project / spec templates | Starters and Spec-Driven Development scaffolds |
Platform-provided items may appear as read-only until you fork (copy-on-write) them into your org. You can later reset an override to return to the platform default.
Visibility and deploy
Content can be scoped to:
- the whole organization
- selected projects
- a single project-owned item
Use visibility so the right teams get the right prompts and rules without flooding every repo.
Spec templates
Org spec templates feed Spec-Driven Development. Prefer publishing shared requirements/design/tasks scaffolds here so feature work stays consistent across teams.