Skip to content

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: a local-only patch regresses on the next t1k modules update or never reaches other consumers. /t1k:sync-back is the mechanism. Stopgap: a local patch ONLY when it unblocks current work AND a sync-back (or kit-source) PR opens in the same session AND is tracked to merge before the work is declared done; no merged kit PR by session end → violation.

Manual correction implies a skill gap — fix the artifact, not the brief

Section titled “Manual correction implies a skill gap — fix the artifact, not the brief”

Knowledge injected into a teammate brief, spawn prompt or correction that should already live in a skill, agent or rule: STOP and fix the artifact before the next teammate spawns, or every future spawn pays the same tax (strict form of development-principles.md § “Update Skills After Every Error”: fires on a correction applied successfully; edit during the work, not at wrap-up). Triggers: the same warning in 2+ briefs · a constraint re-explained · a recurring correction of a teammate’s output · a teammate’s [t1k:skill-bug …]/[t1k:lesson …]. Exceptions: a single-use session decision · a per-project fact · the skill IS the artifact you are already editing.

Procedure and anti-patterns: docs/kit-wide-fix-discipline.md · docs/manual-correction-implies-skill-gap.md.