conventionslisted

# conventions Manage the named conventions that ship in vault-root `CLAUDE.md` files — install, remove, check status, or propagate to many vaults at once. A "convention" is a self-contained `## H2` section of `CLAUDE.md` (e.g. `## Source provenance — \`source_type\` frontmatter`) that tells Claude how to behave for that vault. The router ships a library of these as markdown snippets; this skill is the installer / detector / synchronizer. ## Pre-conditions 1. Target vault(s) are online — call `list_vaults` first. 2. The plugin install ships the convention snippets at `<plugin-root>/skills/conventions/snippets/*.md`. You'll need to read these to know what's available. ## When to use - *"install source-type on this vault"* / *"installe la convention source-type ici"* - *"list conventions"* / *"quelles conventions sont disponibles"* - *"what's installed on vault X"* / *"quelles conventions sont actives sur X"* - *"sync source-type to all vaults"* / *"propage source-type partout"* - *"remove bilingual from vault Y"* / *"retire bilingual de Y"* ## When NOT to use - The user wants to write a CUSTOM convention not in the snippet library → file it as a regular snippet first (see "Add a new convention" below). - The user wants to overwrite the entire CLAUDE.md → use `wiki` skill (re-scaffold) instead. - The user wants to remove a section they hand-wrote (not from the library) → it's their content, don't touch via this skill. ## How a convention is identified Each convention sn