archive

Capture, index, and reuse project knowledge across sessions. Search : grep -ri "keyword" .archive/ Index : .archive/MEMORY.md - After completing a significant task (deploy, migration, major feature) - After resolving a tricky debugging session - When the user says "archive this" - After any multi-step process with learnings worth preserving - Before debugging infrastructure, deploy, or CI issues - Before repeating a process done in a past session - When encountering an error that may have been solved before - Read .archive/MEMORY.md — check for related existing archives - Create .archive/YYYY-MM-DD/ directory if needed - Write markdown file with YAML frontmatter (see references/TEMPLATE.md ) - Update .archive/MEMORY.md : add one-line entry under the right category - If related archives exist, add related field in frontmatter - Read .archive/MEMORY.md to find relevant entries - Read the specific archive file for detailed context - Apply learnings to current task - infrastructure — AWS, ECS, IAM, networking, secrets, CloudWatch - release — TestFlight, versioning, Git Flow, CHANGELOG - debugging — Bug fixes, error resolution, gotchas - feature — Feature design, implementation notes - design — UI/UX, icons, visual design - .archive/ must be in .gitignore — local-only notes - Keep entries concise but reproducible - Focus on problems, fixes, and exact commands - Always update...