Use cases
Use cases
Illustrative setups. The package names, repositories and numbers are examples, not customers.
An organization-wide baseline
Publish one package of house rules and render it in every repository.
Sample items
- Package: @acme/frontend-baseline@1.4.0 on the stable channel
- Rendered as CLAUDE.md, AGENTS.md and .github/copilot-instructions.md
- A new version goes out by moving the stable channel
A monorepo with different tools per team
Give each part of a monorepo its own providers and packages.
Sample items
- Target .: claude, codex and copilot, the baseline package
- Target apps/web: claude, a front-end agent package
- Target services/api: codex, an API agent package
A drift gate in CI
Fail the build when someone edits a generated file by hand.
Sample items
- `wl ci setup` to generate the drift-check workflow
- `wl sync` as a pipeline step
- Exit code 1 when files have drifted from the desired state
A personal home workspace
Keep your own agent setup the same on every machine.
Sample items
- `wl init --home` to create a home binding
- A home package with an addMcpServer effect and a preflight check
- `wl restore --home` to roll back to the latest backup
Stop copying AI config between repositories
Publish your instructions, skills and hooks once, assign them to workspaces, and let CI tell you when anything drifts.