What problem does it solve? When editing a session-entry hook or the turn map it serves, it is easy to break silent behaviors: serving an unreadable handover, exiting with a non-zero code, or letting the map drift out of sync with the governing rule. This Skill encodes the pattern for keeping the map, the hook, and the consistency check correct. ## Core Features & Use Cases - Content separation guidance: Defines which lines belong in the turn map (what to do) versus the rule (why), with a concrete selection table. - Hook serving order and safety: Prescribes serving the handover before the map, using -r readability checks, branch-derived handover filenames, and a mandatory exit 0. - Verification workflow: Runs node tools/check-turn-map.mjs to compare map states against the rule both ways, plus a four-case live trial of the hook (both parts, missing handover, missing map, missing both). - Use Case: After adding a new state to the work-conduct rule, use this Skill to update the turn map, re-run the consistency check, and verify the entry hook stays silent with a zero exit code when files are absent. ## Quick Start Ask the assistant to apply the turn-entry-map pattern to update the turn map and verify the entry hook after adding a new state to the work-conduct rule.