kit-wide-fix-discipline
Kit-Wide Fix Discipline — Fix at the Kit Source, Not Locally
Section titled “Kit-Wide Fix Discipline — Fix at the Kit Source, Not Locally”Every improvement, bug fix, doc correction, or behavior change to kit-owned content (anything under .claude/ shipped by a theonekit-* kit) MUST land in the kit source repo, NOT just locally in the consumer project where the symptom was found.
A local-only patch is a regression in disguise: global ($HOME/.claude/) copies are overwritten on the next t1k modules update (fix disappears), and project-local (<consumer>/.claude/) copies survive locally but never reach other consumers (same bug, every other install). The kit source is the only place where one fix reaches everyone.
Step-by-step procedure and the anti-pattern catalogue: docs/kit-wide-fix-discipline.md. /t1k:sync-back automates the identify-owning-kit → edit → PR flow from a consumer project.
Acceptable stopgap pattern
Section titled “Acceptable stopgap pattern”A local patch is acceptable ONLY when:
- The fix is needed immediately to unblock current work, AND
- A
/t1k:sync-backPR (or direct kit-source PR) is opened in the same session, AND - The kit PR is tracked to merge before the work is declared done
The stopgap path becomes a violation when the session ends without a corresponding kit PR.
Related
Section titled “Related”prefer-local-over-global-edits.md— within a project, prefer project-local over global (complementary)kit-pr-workflow-boundary.md— kit-PR babysitting belongs to the kit-maintainer sessionskills/t1k-sync-back/SKILL.md— the automated mechanism for the kit-wide-fix floworchestration-rules.md—/t1k:sync-backand/t1k:issueare the canonical kit-targeting workflowsCLAUDE.mdCore Requirement #12 — origin of this rule