Overview
Use Luhmann's Zettelkasten method to build and maintain a note system of "one card, one idea": atomic cards, rewritten in your own words, mandatory links, structure emerging from the link network. Applicable to any markdown note vault; Obsidian or plain directories both work.
This skill has two use cases:
- Standalone use — build a Zettelkasten from scratch, or process inspirations and literature material into permanent cards.
- Referenced by other skills — as a checklist standard for note-writing discipline.
llm-wikipage writes reference this skill's change checklist (atomicity, card splitting, links).
Discipline is the essence; the folder structure is only a default suggestion. When applying it to an existing note vault (e.g., a wiki maintained by llm-wiki), follow that vault's structure and conventions and apply only the discipline.
Input Contract
At least one of the following is required:
vault_path— note vault path (new or existing)- Material to process — inspirations, literature content, pasted text, or existing notes to check
Optional:
mode—init(initialize) /capture(collect) /process(process into permanent cards, default) /audit(inventory and health check)- Existing note vault conventions (frontmatter, link syntax) — when not provided, follow the conventions observed on site
Workflow
Note types
| Type | Purpose | Lifecycle |
|---|---|---|
| Fleeting note | Quick capture, unprocessed | Process within 1-2 days, do not keep |
| Literature note | What the source says (your own words + citation) | Kept permanently, for permanent cards to cite |
| Permanent note | The essence of the system. Concept cards (one claim) or entity cards (a person/event/organization/work/named method) | Continuously evolving |
| Structure note | Card maps, entry points, reading paths | Grows and updates with links |
Workflow
- Confirm conventions — before creating a new note vault, choosing note types, or applying to an existing knowledge base, read principles, note types, and conventions, including naming, frontmatter, complete card examples, and llm-wiki correspondence. Existing directories and syntax take precedence.
- Capture — inspirations go into inbox; when reading sources, write literature notes in your own words and mark the source. process mode must process material into permanent cards; it cannot merely accumulate literature notes.
- Process — search existing cards, then determine which independent ideas the material contains. If the same idea already exists, update it; write new ideas as new cards; when conflicting with an existing card, keep both, write a new card linking them, and mark the divergence according to the note vault's conventions. Use declarative-sentence titles for concept cards and entity names for entity cards; write facts, timelines, or steps as scannable structures.
- Split cards — before adding or modifying a card, fully read card-splitting criteria, operation steps, and check examples. A concept card focuses on one idea that can be understood and referenced independently; an entity card focuses on one entity. If it contains multiple independently valid claims, it should be split into different cards and links should be created. Length alone cannot determine whether to split; explanations, examples, and necessary context of the same idea can remain on the same card, but different ideas must not all be kept together on the grounds of preserving context. Split-out cards must supply the necessary background and stand on their own when read independently. When an entity card grows an independent argument, split it into a concept card according to the reference document.
- Links — Link in place where the body text mentions terms from existing cards; when necessary, use
[[目標卡|顯示文字]]Keep sentences fluent. At least 1-2 outgoing links; cards that are not naturally mentioned in the body text but have an important relationship (contrast, rebuttal) should be added at the end of the text with the relationship explained. Judge whether the linked card needs a backlink and whether related structural notes need updating. Structural notes can use link lists to arrange the reading flow, growing with card relationships, without preset outlines restricting where cards go. - Pre-write checklist — Every addition or modification executes the reference document's change checklistitem by item, and only writes after passing. Edits to linked cards triggered by backlinks only check links, and do not rerun the full checklist or recursively trigger the next layer of backlinks.
- Audit(audit mode) — First read the above card-splitting criteria and checklist, then check orphan cards, cards to be split, duplicate cards, asymmetric links (A→B with no backlink and no reasonable cause), and unprocessed inbox items, and propose paths and recommended actions.
Output Contract
cards_written— List of added and updated cards (including types).split_decisions— Actual splits and their basis, as well as reasons for not splitting that affect card boundaries.links_updated— Actual changes to links, backlinks, and structural notes; exceptions that affect understanding or subsequent processing must be explained, but there is no need to list every backlink not added item by item.audit_report— In audit mode, list orphan cards, cards to be split, duplicate cards, asymmetric links, and inbox backlog, with paths and recommended actions.
Quality Rules
- Permanent cards are written in your own words; literature notes mark the original source, and permanent cards cite literature notes. When applying llm-wiki, follow theexisting knowledge base correspondence to handle exceptions for sources and page types.
- The unit of atomicity is the idea, not the sentence. The complete card-splitting criteria and item-by-item checklist are maintained uniformly in the reference document, and are not replaced by the summary in this main file.
Quick Reference
- Principles, note types, and conventions: Read when creating or applying a note library, including the six principles, naming and frontmatter, four complete card examples, folder structure, and llm-wiki correspondence.
- Card-splitting criteria and change checklist: Read completely before adding, modifying, or auditing cards, including criteria for splitting and not splitting, entity card splitting, operation steps, the item-by-item checklist, and card-splitting/update cases.