archive

1# Archive Skill
2 
3Capture, index, and reuse project knowledge across sessions.
4 
5## When to Archive
6 
7- After completing a significant task (deploy, migration, major feature)
8- After resolving a tricky debugging session
9- When the user says "archive this"
10- After any multi-step process with learnings worth preserving
11 
12## When to Consult Archives
13 
14- Before debugging infrastructure, deploy, or CI issues
15- Before repeating a process done in a past session
16- When encountering an error that may have been solved before
17 
18**Search**: `grep -ri "keyword" .archive/`
19**Index**: `.archive/MEMORY.md`
20 
21## Archive Workflow
22 
231. Read `.archive/MEMORY.md` — check for related existing archives
242. Create `.archive/YYYY-MM-DD/` directory if needed
253. Write markdown file with YAML frontmatter (see `references/TEMPLATE.md`)
264. **Update `.archive/MEMORY.md`**: add one-line entry under the right category
275. If related archives exist, add `related` field in frontmatter
28 
29## Lookup Workflow
30 
311. Read `.archive/MEMORY.md` to find relevant entries
322. Read the specific archive file for detailed context
333. Apply learnings to current task
34 
35## Categories
36 
37- **infrastructure** — AWS, ECS, IAM, networking, secrets, CloudWatch
38- **release** — TestFlight, versioning, Git Flow, CHANGELOG
39- **debugging** — Bug fixes, error resolution, gotchas
40- **feature** — Feature design, implementation notes
41- **design** — UI/UX, icons, visual design
42 
43## Rules
44 
45- `.archive/` must be in `.gitignore` — local-only notes
46…