Aitk governance
Governance rules and stack definitions. Source `.md` files install as path-scoped Claude rules in `.claude/rules/`. Use for adding rules, editing stacks, or install and sync.From its SKILL.md
npx -y skills add erclx/aitk --skill aitk-governanceAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.5 KB, as published. Nobody here has run it
Governance
Read .claude/context/governance/overview.md for the system overview and .claude/context/governance/stacks.md for stack structure before editing.
Rules
- Read
.claude/context/governance/rules.mdfor the numbering ranges before picking a number for a new rule. - Follow
.claude/standards/rule.mdfor frontmatter, heading style, and bullet conventions when writing a new rule file. rule_subdiris all that is left inscripts/lib/gov.sh. Frontmatter stripping issrc/frontmatter.ts. Do not duplicate either.- Every verb is TypeScript and
scripts/gov/is gone. The sync engine issrc/sync/engine.ts, the gov adapter issrc/gov/adapter.ts, the payload builder issrc/gov/payload.ts, the stack resolver issrc/gov/stacks.ts, and the catalog behindlistissrc/gov/list.ts. - Changing what counts as a change, or where a rule's source lives, belongs in the adapter. Changing the scan report, the prompt, or the apply loop belongs in the engine, where snippets and standards will inherit it.
Install path
aitk gov install <stack> <target>writes.claude/rules/<subdir>/<rule>.mdas a passthrough copy. Source files carry the Claude shape directly, so the install copies the.mdfile as-is and preserves subdirectories.aitk gov syncdiffs.claude/rules/against source. It also removes any stale.claude/GOV.mdleft over from the retired build.aitk gov buildproduces a single concatenated paste-payload at.claude/.tmp/gov/rules.mdfrom.claude/rules/.
Stacks
- New stack: create a
.tomlingovernance/stacks/, setextends, list rule names without.md
Sync checklist
When adding a rule:
- Add it to the relevant
rulesarray ingovernance/stacks/*.tomlif it belongs to a stack
When adding a stack:
- Create
.tomlingovernance/stacks/, setextends, list rules
Rule audit
After writing or revising a rule, audit each bullet against the checklist. Trigger phrases: "audit this rule", "review the governance rule", "is this rule worth keeping".
- Read
.claude/skills/aitk-governance/references/rule-audit.mdfor the criteria and output shape.
Reference
.claude/context/governance/index.md: the domain catalog, with the overview, rules and their numbering, stacks, and install and sync as sub-areas.claude/standards/rule.md: conventions for writing rule files