Extraction Rules
Extract, don't summarize. Techniques, not recommendations. Verify prior state before recommending.
- Every output item is a TECHNIQUE — a specific pattern, code snippet, configuration, or approach.
- Quote or code-block the actual content — show exactly what was said/written.
- Map to LifeOS components — every technique connects to a specific file, skill, workflow, or system component.
- Verify Prior State (Thread 0 gate) — Before emitting ANY recommendation, confirm against Thread 0 inventory: is it already in Algorithm / PATTERNS.yaml / hooks / SKILL files / KNOWLEDGE / prior ISAs? Assign a Prior Status emoji and cite evidence. Items that are ✅ DONE go to Skipped, not Recommendations.
- Two mandatory description fields, ≤2 sentences each, concrete and specific:
- What It Is: the technique itself — what it does, how it works, what capability it provides
- How It Helps LifeOS: the specific benefit — which component improves, what gap it fills
- Provide implementation — show before/after code or specific steps.
- Skip, don't dilute — if content has no extractable technique, put it in Skipped Content with reason.
Source Type Labels:
| Label | Meaning |
|---|---|
GitHub: claude-code vX.Y.Z |
Specific version release notes |
YouTube: Creator @ MM:SS |
Video with timestamp |
Docs: Section Name |
Documentation section |
Blog: Post Title |
Blog post |