What problem does it solve? When a repository lays out a shared rules package, the shipped text, gate mappings, and guard checks often do not match the tree's own names, paths, and conventions. Editing laid-out files in place is silently lost on the next sync, so teams need a safe, repeatable way to layer their own overrides, gate branches, guard profiles, and custom rules on top of the package. ## Core Features & Use Cases - Section-based text overrides: Place override files under overrides/ that merge by heading — replacing, appending, or lifting package sections — with guidance on pitfalls like headings inside code fences. - Gate and guard customization: Add your own skill_for branches and profile functions (docs pairing, lint targets, branch forms) that run before the package default while still delegating to _default. - Signs, checks, and custom laws: Declare uniformity signals as mergeable JSON data, and author your own laws and rules linked through frontmatter with a consistency audit. - Use Case: A repo's gate demands the wrong rule for *.stories.ts files. Add a specific branch before the general one in skill_for, call skill_for_default for everything else, then verify with the package gate scenarios and sync --check. ## Quick Start Ask the assistant to add an override for the package rule file whose text does not match this repository, then run sync and sync --check to verify the layout.
