Use cases

Illustrative examples with made-up names. They show the commands involved, not real customers.

Give every assistant the same rules

A team writes its coding rules once as an instruction asset in @example/team-rules and lists claude, codex and copilot on the root target. `wl render --dry-run` shows CLAUDE.md, AGENTS.md and .github/copilot-instructions.md; `wl sync --approve-local` then writes them.

Sample items

@example/team-rules@1.2.0
CLAUDE.md
AGENTS.md

Fail CI on drift

A pull request edits AGENTS.md by hand. The CI step `wl sync -w workloom.workspace.json --check` reports the file as modified and exits non-zero, so the change goes back into the package instead.

Sample items

wl sync --check
[MODIFIED] AGENTS.md
exit 1

Per-path providers in a monorepo

apps/web gets Copilot instructions and services/api gets Claude, each from its own target. One manifest, one render plan per target and provider.

Sample items

target-web / copilot
target-api / claude
services/api/CLAUDE.md

Set up a new laptop

A developer creates @example/home with `wl profile create`, pinning exact package versions, and on a new machine runs `wl home install @example/home` to review the diff, then again with --apply.

Sample items

@example/home@0.1.0
wl home install --apply
~/.claude/settings.json

Stop hand-editing four config files per repository

Keep one workspace manifest per repository, render it for every provider your team uses, and let CI tell you when a projection drifts.