Skip to content
T1KTheOneKit

kit-install-scope

Kit Install Scope — One Kit, One Scope

Section titled “Kit Install Scope — One Kit, One Scope”

Rule

Section titled “Rule”

A kit is installed in exactly one scope. core and model-router are global-scope (~/.claude/); every engine/domain kit (unity, designer, cocos, react-native, web, nakama, marketing) is per-project (./.claude/). Two copies is a misconfiguration, not a backup — only one is ever served (project-local shadows global), so the shadowed copy is dead weight that still updates and reports healthy while nothing loads it. SSOT: hooks/lib/kit-scope-policy.cjs; a kit may override via its own installScope in t1k-config-*.json.

core found local is warn-first with a dated ratchet; model-router found local is exempt (non-functional by construction). Ratchet state, evidence, and the exemption rationale: docs/kit-install-scope.md.

How to apply

Section titled “How to apply”
  1. Before installing, pick scope from the kit: core/model-router → t1k init --global; anything else → per-project.
  2. On a reported finding (doctor check #58), drop the copy that doesn’t belong. Uninstalling is destructive — run it yourself, never let an agent sweep it, even at confidence=high, which names what CAN be automated, not a standing instruction to automate it.
  3. Before dropping the project copy, run /t1k:sync-back first if it holds local edits — those edits live only in the copy you’re about to delete.
  4. inheritsFrom → global is the one legitimate overlap — check #58 reports it INFO only, never confidence=high.
Section titled “Related”

prefer-local-over-global-edits.md (which copy to EDIT, vs. this rule’s should-both-exist) · Doctor #48/#58/#55/#36 · skills/t1k-doctor/references/scope-remediation.md (removal HARD-GATE) · docs/kit-install-scope.md (exemption history, remediator mechanism, config plumbing).