Skip to content
Workloom
Menu

Use cases

Use cases

Illustrative setups. The package names, workspaces and teams are examples, not customers.

Set up a new laptop

A developer installs their personal package into the home workspace. Claude Code and Codex instructions land in the home directory, a hook is registered as a reversible settings effect, and a token comes from the keychain.

Sample items

  • wl install @example/my-ai-setup@2.0.0
  • wl doctor

Share a review skill with a team

A platform team publishes a review skill package. Each developer installs it; the plugin it names installs only after they approve it with --approve-plugin.

Sample items

  • wl push --draft --package review-kit.json
  • wl install @example/review-kit

Fail CI on drift

A repository’s workspace requires a sync check. The pipeline runs it on every change and reports the result, so the registry raises drift.detected when someone edits a generated file by hand.

Sample items

  • wl sync --check --workspace workloom.workspace.json --report

Start from a published workspace

A team forks a public workspace from the catalog, edits it locally, and publishes its own version, private by default.

Sample items

  • wl fork ws_example_shared --registry-url https://registry.example.com

Set up a new machine with one manifest

Keep your AI tool config in versioned packages, install it into every machine’s home directory, and let CI tell you when a repository drifts.