Use cases
Use cases
Illustrative setups. The package names, workspaces and numbers are examples, not customers.
An organization-wide baseline
Publish one package of house rules and select it in every workspace.
Sample items
- Package: @acme/base-instructions, version 2.1.0 on the stable channel
- Every workspace target selects it with the constraint ^2.0.0
- Rendered as CLAUDE.md, AGENTS.md and GEMINI.md at each target
A monorepo with several targets
Give each part of a monorepo its own packages and providers.
Sample items
- Target .: claude, codex and gemini, the baseline package
- Target apps/web: claude, a front-end skills package
- Target services/api: codex, pinned with a workspace override to ~1.4.0
A drift gate in CI
Fail the build when a rendered file no longer matches the declared revision.
Sample items
- A checked-in workloom.workspace.json binding for the repo
- `wl sync --check` as a pipeline step
- A workspace.drift_detected webhook to the team’s endpoint
A team home profile
Give every teammate the same personal agent setup, attributed and removable.
Sample items
- A workspace target with root home and the package @acme/dev-env
- `wl home diff`, then `wl home apply` on each laptop
- `wl home remove` takes every owned file back out
One desired state for every repo and every laptop
Publish your organization’s AI workflow content once, declare where it goes, and let `wl sync --check` tell you when anything drifts.