napkin
Skill48 starsChanged 8 days agoMITView on GitHub
Use at the start of every repository session to load and maintain concise notes about corrections, user preferences, successful patterns, failed approaches, and project facts that should change future behavior.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- tammai/bigin-skillstheir own version, first seen Oct 11, 2026
- 01sadra/napkintheir own version, first seen Aug 20, 2026
- ReaperOAK/ForgeOStheir own version, first seen Jun 8, 2026
- madeinlowcode/skills-claude-codetheir own version, first seen Apr 3, 2026
- seaneoliver/claude-code-startertheir own version, first seen Mar 17, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- github/awesome-copilot★ 41ksame name
- blader/napkin★ 591same name
- madeinlowcode/skills-claude-code★ 7same name
- 01sadra/napkin★ 2same name
- seaneoliver/claude-code-starter★ 2same name
- tammai/bigin-skills★ 1same name
- ReaperOAK/ForgeOS★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agySkill
- claudeSkill
- codexSkill
- datacheckSkill
- hallucinatorSkill
- plain-writingSkill
- vizSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use .claude/napkin.md as small project memory.
- Distinctive: line 10
Add an entry when:
- Distinctive: line 20
Keep the file easy to scan.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Napkin
Use .claude/napkin.md as small project memory. Read it before other work. If it does not exist, create it with sections for corrections, preferences, useful patterns, failed patterns, and project notes.
Add an entry when:
- the user corrects the agent;
- the agent catches its own mistake;
- a tool or project behaves unexpectedly;
- a method succeeds or fails in a way worth repeating;
- the user states a durable working preference.
Record the lesson and the behavior to use next time. Do not store a transcript, routine progress, credentials, private data, or facts already documented elsewhere.
Keep the file easy to scan. Merge duplicates, remove obsolete notes, and keep it under about 200 lines.
Example:
# Napkin
## Corrections
| Date | Source | What happened | Use next time |
|---|---|---|---|
## Preferences
- Keep review findings tied to exact files.
## Useful patterns
- Run the smallest relevant test before the full suite.
## Project notes
- Analysis entry point: `scripts/main.R`.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.