livery-extensions-claude¶
What Claude Code reads in a workspace. A workspace turns it on by listing the extension:
fm sync then writes three things:
CLAUDE.md, committed: an import line for each guidance fragment in section order, the repository's ownfragments/after them, thenCLAUDE.project.md, the repository's own facts. EditCLAUDE.project.md, neverCLAUDE.md..workshop/fragments/, this checkout's alone: the guidance every listed extension ships or renders, for the agent..claude/, this checkout's alone: a link to each skill and hook every listed extension ships undercontent/skills/andcontent/hooks/, and a copy of the onesettings.json. A copy the agent's tooling edits is a local override, kept and named.
The settings wire Claude Code's hooks to the extension's verbs through
one shim, .claude/hooks/fm-hook.sh:
fm hooks.pre-bashrefuses a footman command piped intotailorhead, and a push of a branch that conflicts withorigin/main.fm hooks.post-editruns the gate's fixers over the edited file.fm hooks.stoprefuses to end a turn whose last command was a failedfmverdict, once.
A project born while the extension is listed starts with a
CLAUDE.project.md; fm new.project lists it only when asked. A
workspace that does not list it has no CLAUDE.md and no .claude/.