working-with-lacquerlisted

# Working With Lacquer Lacquer renders shared content — CLAUDE.md regions, skills, commands, lint configs, git hooks, CI workflows — from one repo into every project. A project declares its shape in `.lacquer.toml`; `lacquer sync` writes the content; `lacquer audit` checks the project against it and is wired into CI. The rule that explains every mechanism below: **a lacquer-managed file is identical to the lacquer's copy, or it is excluded. There is no third state.** A quietly-edited copy is how one project's pre-commit hook ends up weaker than its CI while looking healthy. ## Is this file mine? ```sh lacquer audit # classifies every managed unit, lists the ones that aren't clean lacquer status # each CLAUDE region's stamped version vs the lacquer's latest ``` If `audit` lists it, the lacquer owns it. Typically: `.swiftlint.yml`, `.swiftformat`, `biome.json`, `deno.jsonc`, `.pre-commit-config.yaml`, `lefthook.yml`, `.github/workflows/<profile>-*.yml`, `.claude/skills/**`, `.claude/commands/**`, and the `<!-- lacquer:… -->` regions inside `CLAUDE.md` / `AGENTS.md`. Text *outside* those markers in a CLAUDE.md is the project's and is preserved. ## Exit codes | Code | Means | Fix | |---|---|---| | 0 | clean | — | | 1 | the command failed (bad manifest, I/O, missing profile) | read the message | | 2 | usage error | — | | 3 | a managed file was edited locally; sync would clobber it | see below | | 4 | a project baseline is not met | meet it, or time-box a relaxation | |