Help us improve
Share bugs, ideas, or general feedback.
From grimoire
Builds a long-term knowledge base of atomic, linked notes that surfaces unexpected insights across domains. Use for research, learning, or writing projects that need to generate new ideas.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireHow this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:apply-zettelkastenThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Build a network of atomic, linked notes — one idea per note, connected by explicit links — that surfaces unexpected insights across domains over time.
Enforces Zettelkasten note-writing discipline: atomic claims, declarative titles, own-words prose, and typed link relationships. Use when capturing or refactoring evergreen notes.
Designs a personal knowledge management system using the CODE framework (Capture, Organize, Distill, Express) for capturing, organizing, and retrieving notes and ideas.
Share bugs, ideas, or general feedback.
Build a network of atomic, linked notes — one idea per note, connected by explicit links — that surfaces unexpected insights across domains over time.
Adopted by: Academic researchers, non-fiction writers, software architects, knowledge workers in law, philosophy, and science using tools like Obsidian, Roam, and Logseq Impact: Luhmann: used his Zettelkasten to produce 70 books and 400 academic articles over a 40-year career; Ahrens: linear note-taking produces archives you never re-read; Zettelkasten produces a thinking partner that generates connections you didn't plan
The core insight is that the value of notes is not in storage but in retrieval and collision. When each note is atomic (one idea, standalone) and explicitly linked to related notes, the act of placing a new note forces you to articulate how it relates to existing knowledge — and that articulation is where insight is generated.
Fleeting note: "Newport — deep work produces in hours what reactive work does in days — attention residue lasts 20 min"
Literature note: Newport (2016) argues that cognitive performance depends on extended uninterrupted focus because task-switching leaves attention residue that degrades subsequent work for up to 23 minutes. I partially disagree: this may vary by task type.
Permanent note (ID: 2025-06-03-attention-residue): "Attention residue: switching tasks leaves a cognitive echo of the previous task that impairs performance on the new one for 10–23 minutes (Mark 2008). This makes interruption cost asymmetric — the interrupter pays zero cost; the interrupted person pays 23 minutes." Links: → [2025-05-12-context-switching-cost], → [2025-04-20-deep-work-scheduling]