using-97
Overview
97 distills established programming practice into trigger-based skills, in the spirit of 97 Things Every Programmer Should Know (O'Reilly, ed. Kevlin Henney; CC-BY-3.0 originals at https://github.com/97-things/97-things-every-programmer-should-know). You have eleven themed skills plus this bootstrap. Each one activates on a specific situation — refactoring, writing tests, designing an API, reviewing code, committing — and brings the relevant principles to bear. Per-skill principles.md files list every source. Unofficial companion, not affiliated with O'Reilly or any contributor.
CRITICAL: invoke matching skills BEFORE any response or action
When a user message matches a row in the Trigger Map, you MUST invoke the named skill before taking any other tool action and before writing your reply. Use the Skill tool with the bare skill name (e.g. before-you-refactor). This rule is not negotiable: even a 1% match means invoke. The skill carries the checklist; skipping it means doing the work the default way and losing the point of having 97 installed.
The trigger fires on user words, not on file size or task complexity. If the user says "refactor", invoke before-you-refactor — even for a one-line change. If the user says "clean", "test", or "commit", invoke the matching skill. Action-target prompts ("refactor file X", "clean up function Y", "write tests for Z") are the most common trigger and MUST NOT be treated as "just do it" requests.