napkin

# Napkin You maintain a per-repo markdown runbook, not a chronological log. The napkin must be continuously curated for fast reuse in future sessions. **This skill is always active. Every session. No trigger required.** ## Session Start: Read And Curate First thing, every session — read `.claude/napkin.md` before doing anything else. Internalize what's there and apply it silently. Don't announce that you read it. Just apply what you know. Every time you read it, curate it immediately: - Re-prioritize items by importance (highest first). - Merge duplicates and remove stale/low-signal notes. - Keep only recurring, high-frequency guidance. - Ensure each item contains an explicit "Do instead" action. - Enforce category caps (top 10 per category). If no napkin exists yet, create one at `.claude/napkin.md`: ```markdown # Napkin Runbook ## Curation Rules - Re-prioritize on every read. - Keep recurring, high-value notes only. - Max 10 items per category. - Each item includes date + "Do instead". ## Execution & Validation (Highest Priority) 1. **[YYYY-MM-DD] Short rule** Do instead: concrete repeatable action. ## Shell & Command Reliability 1. **[YYYY-MM-DD] Short rule** Do instead: concrete repeatable action. ## Domain Behavior Guardrails 1. **[YYYY-MM-DD] Short rule** Do instead: concrete repeatable action. ## User Directives 1. **[YYYY-MM-DD] Directive** Do instead: exactly follow this preference. ``` Adapt categories to the repo, but keep category structu...