meditationlisted

# Meditation Transform session insights into durable knowledge. Most sessions don't need it; some have a pattern worth keeping. ## When to Fire - User says "let's meditate", "consolidate", or invokes `/meditate` - End of a significant work session - After solving a hard problem with a reusable insight - Before a long break from a project **Skip when**: the session was routine execution of patterns already encoded. Meditation on every session produces noise; the discipline is to write only what's new and portable. ## The Five Steps ### 1. Review Scan the session honestly: - What problems did we solve? - What mistakes did we make? - What patterns emerged that weren't already encoded? - What would help future sessions? ### 2. Extract Separate signal from noise. For each candidate pattern, ask: *"Is this already covered by an existing skill, instruction, or memory?"* If yes, skip. If no, route by type: | If pattern is... | Create / update | |---|---| | Reusable domain knowledge | Skill (`.github/skills/<name>/SKILL.md`) | | Always-on behavior or rule | Instruction (`.github/instructions/<name>.instructions.md`) | | Repeatable workflow / slash command | Prompt (`.github/prompts/<name>.prompt.md`) | | Automatable mechanical task (skill-owned) | Skill script (`.github/skills/<name>/scripts/*.cjs`) | | Automatable mechanical task (cross-cutting) | Repo script (`scripts/<name>.cjs`) | | User preference (cross-project) | User memory (`/memories/<name>.md`) | | Project / repo