Save Knowledge

Each unit of work should teach the system something so subsequent work gets easier, not harder. Bug fixes eliminate future bug categories. Patterns become tools. Decisions become searchable context.

Quick Start

1. Determine the knowledge type from context (see heuristics below).
2. If the type is not clear, ask the user which type to use.
3. Choose a short slug and date prefix for the filename.
4. Create ./knowledge/<type>/ in the repo root if it does not exist.
5. Verify the target file does not already exist. If it does, change the slug or add a numeric suffix.
6. Read the type template from resources/<type>.md using the Read tool, then write the content to ./knowledge/<type>/YYYY-MM-DD-<short-slug>.md using the Write tool. Do NOT use shell commands like cp or mkdir.
7. Fill in the placeholders in the new file.