Turn Repeated Setup Advice Into Maintained Instructions

Your notebook has become a small application, and every new session needs the same explanation: where the tests live, how to run them and which generated files to leave alone.

/init can draft a starter CLAUDE.md from the repository. Inspect that draft against the real build scripts and team conventions. A generated instruction can be wrong or quickly become stale.

Add the constraints the code does not explain, then commit the shared file so the team can review and maintain it. Use /context to confirm the intended instructions loaded in a session; the memory guide explains loading behavior.

When a rule matters to correctness, give it an executable check as well. A maintained instruction file helps a colleague or agent find the workflow. It does not guarantee they followed it.