sync-knowledge

name	sync-knowledge
description	This skill should be used when the user says "sync knowledge", "update knowledge", or "update KNOWLEDGE.md". Reads all sessions from SESSIONS.md and merges demonstrated knowledge into KNOWLEDGE.md.
disable-model-invocation	true
allowed-tools	Read, Write, Edit, Glob

Sync Knowledge

Read all sessions from SESSIONS.md and update KNOWLEDGE.md at the root of the project.

Steps

1. Read SESSIONS.md — extract all sessions, noting what was worked on and what caused friction
2. Read KNOWLEDGE.md if it exists
3. Update KNOWLEDGE.md following the structure and rules below

KNOWLEDGE.md Structure

Organize by concept area. Each concept has a current status and a dated log showing evolution over time:

## Iterators

**Status:** ✅ Solid

| Date | Update |
|------|--------|
| 2026-03-31 | ⚠️ Confused about `nth()` advancing the iterator |
| 2026-04-02 | ✅ Collects into `Vec`, understands iterator consumption |

Status values:

• ✅ Solid — demonstrated consistently, not causing friction
• ⚠️ Shaky — understands conceptually but makes mistakes under pressure
• ❌ Struggling — actively blocked or repeatedly confused

Concept Sections

• Ownership & Borrowing
• Iterators
• Error Handling
• Type System
• Axum / Web
• General Rust

Add new sections as needed.

Update Rules

• Add a new log row for today's date only if the session shows a meaningful change or new exposure
• Update the Status line to reflect the most recent log entry
• Never remove log rows — the history is the point
• A single session appearance is tentative (⚠️ Shaky); consistent across sessions upgrades to ✅ Solid
• If a previously solid concept caused friction again, downgrade the status and log it