What problem does it solve? When a repository consumes the @rt-tools/agent-kit package, its laid-out rules files carry an rt-kit header and must never be edited in place. This Skill tells you where every kind of change actually belongs — package source, override, gate map, or config — so layouts, version bumps, and audits stop failing mysteriously. ## Core Features & Use Cases - Edit-location routing: Maps each kind of change (gate rules, ports, checks, overrides, drops, roles) to the exact file that owns it, such as .claude/rt-kit/gate-map.sh or .claude/rt-kit.json. - Layout and audit workflow: Covers agent-kit sync, sync --check, doctor, and adopt, including the all-or-nothing layout semantics and the push-gate audit. - Safe version bumps: Prescribes the three-step upgrade procedure — snapshot the old assets, install and lay out, then audit replaced override sections against the snapshot. - Use Case: You are about to edit a file carrying the header rt-kit v0.29.0 · ... · правится надстройкой, не здесь. Load this Skill to learn that the edit belongs in an override or the package source, not in the laid-out copy. ## Quick Start Load the agent-kit skill before editing any file that carries the rt-kit layout header, then follow its edit-location table to place the change in the correct override or config file.