napkin

A repository runbook provides immediate access to recurring guidance and execution guardrails at the start of every session, reducing onboarding time and avoiding repeated mistakes by keeping prioritized notes in a .claude/napkin.md file.

Structure actionable developer notes by enforcing a maximum of ten high-value items per category, prioritizing by category order, and requiring each entry to include a date and an explicit "Do instead" instruction for direct execution.

Yes, you can read and apply a curated runbook before making code changes to surface top-priority guardrails, environment quirks, and common fixes, ensuring you review the top three action items for the session.

The best way to curate repository documentation is through continuous curation that merges duplicates, prunes low-signal notes, and reprioritizes entries to enforce a maximum of ten high-value items per category for fast onboarding.

Limiting a runbook to ten items per category requires aggressive pruning of low-signal notes and merging duplicates to maintain high-value operational guidance, which may discard historical context if not carefully curated.