[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWFWRPPEBSCPV67P4KK93R":3,"skill-same:01M7EWFWRPPEBSCPV67P4KK93R":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EWFWRPPEBSCPV67P4KK93R","ams-zettelkasten",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-zettelkasten\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: zettelkasten\ndescription: Practice the Zettelkasten method: atomic notes, unique IDs, linking, and building a thinking partner from your notes. Use when doing research, writing, or long-term knowledge work.\ncategory: productivity\n---\n\n# Zettelkasten\n\n## Overview\n\nThe Zettelkasten ('slip box') is a note-taking method for thinking: atomic notes, densely linked, that surprise you with connections.\n\nDeveloped by sociologist Niklas Luhmann, who credited it for his extraordinary output — the box became a conversation partner.\n\nPrinciples: one idea per note, every note linkable, links that explain the relationship, and writing in your own words.\n\nTools don't matter much — index cards work. What matters is atomicity, linking discipline, and regular revisiting.\n\n## When to use\n\n- Academic research, thesis, or dissertation work\n- Writing books, long essays, or substantial articles\n- Building deep expertise in a field over years\n- Any knowledge work where ideas need to connect and compound\n- Moving beyond highlighting to genuine thinking in notes\n\n## Core concepts\n\n- **Atomicity.**\n  One idea per note. If a note contains two ideas, split it. Atomic notes link cleanly; compound notes link messily.\n- **Unique addresses.**\n  Every note gets a unique ID (timestamp, sequence). Links point to IDs, so notes can move and rename without breaking.\n- **Own words.**\n  Rewrite everything in your language. Copy-paste is collecting; restating is thinking. Luhmann's rule: the box contains your thoughts, not quotes.\n- **Link with context.**\n  Don't just link — say why: 'contradicts', 'extends', 'example of', 'prerequisite for'. The relationship is the knowledge.\n- **Fleeting -> literature -> permanent.**\n  Fleeting notes (raw capture) -> literature notes (source summaries) -> permanent notes (your ideas, atomic, linked). Only permanent notes live in the box.\n- **Branching, not filing.**\n  New notes attach to existing ones via links, forming branches of thought. No fixed hierarchy — structure emerges from connections.\n- **The box as partner.**\n  Revisit randomly and by following links. Serendipitous encounters with old notes generate new ideas — if notes are atomic and well-linked.\n- **Write from the box.**\n  Outlines assemble from linked note sequences. Writing becomes arranging existing thoughts, not generating from blank pages.\n\n## Practical workflow\n\n1. **Set up the box.**\n   Any tool with unique IDs and backlinks (Obsidian, plain files, even cards). One inbox for fleeting notes, one home for permanent notes.\n2. **Capture fleeting notes.**\n   Read with pen: jot raw reactions, quotes with page numbers, questions. Messy is fine — these are temporary.\n3. **Write literature notes.**\n   After reading: summarize the source's argument in your words, one note per idea-cluster, with full reference.\n4. **Create permanent notes.**\n   Convert: one idea per note, your words, unique ID, descriptive title. Link to 2-3 related notes with the relationship stated.\n5. **Link deliberately.**\n   Each new note: which existing notes does it contradict, extend, exemplify, or depend on? Write the link sentence explicitly.\n6. **Follow the branches.**\n   Weekly: pick a note, follow its links for 20 minutes. Add new links and notes as connections occur to you.\n7. **Harvest for writing.**\n   When writing: gather the branch, arrange note sequences into an outline, draft from the notes. Cite the box, not memory.\n8. **Maintain the garden.**\n   Monthly: merge duplicates, split compound notes, fix dead links, strengthen weak link-descriptions. The box improves with tending.\n\n## Common pitfalls\n\n- **Collecting without atomicity.**\n  Long multi-idea notes that can't link precisely. Split ruthlessly — atomicity is the whole game.\n- **Link-stuffing.**\n  Ten unexplained links per note. Links without stated relationships are noise, not knowledge.\n- **Skipping your own words.**\n  Boxes full of quotes and highlights. If it's not in your words, it's not your thought.\n- **No literature notes.**\n  Permanent notes without source grounding become unsourced opinions. Keep the chain: fleeting -> literature -> permanent.\n- **Filing instead of linking.**\n  Elaborate folder hierarchies with few links. The Zettelkasten's power is the graph, not the folders.\n- **Never revisiting.**\n  Writing notes and never returning. The serendipity engine needs regular visits — schedule them.\n- **Perfectionist IDs.**\n  Agonizing over numbering schemes. Timestamps work fine; the ID just needs uniqueness, not meaning.\n- **Tool-first adoption.**\n  Spending months configuring software before writing ten notes. Start with any tool; the method is the skill.\n","# Zettelkasten\n\n## Overview\n\nThe Zettelkasten ('slip box') is a note-taking method for thinking: atomic notes, densely linked, that surprise you with connections.\n\nDeveloped by sociologist Niklas Luhmann, who credited it for his extraordinary output — the box became a conversation partner.\n\nPrinciples: one idea per note, every note linkable, links that explain the relationship, and writing in your own words.\n\nTools don't matter much — index cards work. What matters is atomicity, linking discipline, and regular revisiting.\n\n## When to use\n\n- Academic research, thesis, or dissertation work\n- Writing books, long essays, or substantial articles\n- Building deep expertise in a field over years\n- Any knowledge work where ideas need to connect and compound\n- Moving beyond highlighting to genuine thinking in notes\n\n## Core concepts\n\n- **Atomicity.**\n  One idea per note. If a note contains two ideas, split it. Atomic notes link cleanly; compound notes link messily.\n- **Unique addresses.**\n  Every note gets a unique ID (timestamp, sequence). Links point to IDs, so notes can move and rename without breaking.\n- **Own words.**\n  Rewrite everything in your language. Copy-paste is collecting; restating is thinking. Luhmann's rule: the box contains your thoughts, not quotes.\n- **Link with context.**\n  Don't just link — say why: 'contradicts', 'extends', 'example of', 'prerequisite for'. The relationship is the knowledge.\n- **Fleeting -> literature -> permanent.**\n  Fleeting notes (raw capture) -> literature notes (source summaries) -> permanent notes (your ideas, atomic, linked). Only permanent notes live in the box.\n- **Branching, not filing.**\n  New notes attach to existing ones via links, forming branches of thought. No fixed hierarchy — structure emerges from connections.\n- **The box as partner.**\n  Revisit randomly and by following links. Serendipitous encounters with old notes generate new ideas — if notes are atomic and well-linked.\n- **Write from the box.**\n  Outlines assemble from linked note sequences. Writing becomes arranging existing thoughts, not generating from blank pages.\n\n## Practical workflow\n\n1. **Set up the box.**\n   Any tool with unique IDs and backlinks (Obsidian, plain files, even cards). One inbox for fleeting notes, one home for permanent notes.\n2. **Capture fleeting notes.**\n   Read with pen: jot raw reactions, quotes with page numbers, questions. Messy is fine — these are temporary.\n3. **Write literature notes.**\n   After reading: summarize the source's argument in your words, one note per idea-cluster, with full reference.\n4. **Create permanent notes.**\n   Convert: one idea per note, your words, unique ID, descriptive title. Link to 2-3 related notes with the relationship stated.\n5. **Link deliberately.**\n   Each new note: which existing notes does it contradict, extend, exemplify, or depend on? Write the link sentence explicitly.\n6. **Follow the branches.**\n   Weekly: pick a note, follow its links for 20 minutes. Add new links and notes as connections occur to you.\n7. **Harvest for writing.**\n   When writing: gather the branch, arrange note sequences into an outline, draft from the notes. Cite the box, not memory.\n8. **Maintain the garden.**\n   Monthly: merge duplicates, split compound notes, fix dead links, strengthen weak link-descriptions. The box improves with tending.\n\n## Common pitfalls\n\n- **Collecting without atomicity.**\n  Long multi-idea notes that can't link precisely. Split ruthlessly — atomicity is the whole game.\n- **Link-stuffing.**\n  Ten unexplained links per note. Links without stated relationships are noise, not knowledge.\n- **Skipping your own words.**\n  Boxes full of quotes and highlights. If it's not in your words, it's not your thought.\n- **No literature notes.**\n  Permanent notes without source grounding become unsourced opinions. Keep the chain: fleeting -> literature -> permanent.\n- **Filing instead of linking.**\n  Elaborate folder hierarchies with few links. The Zettelkasten's power is the graph, not the folders.\n- **Never revisiting.**\n  Writing notes and never returning. The serendipity engine needs regular visits — schedule them.\n- **Perfectionist IDs.**\n  Agonizing over numbering schemes. Timestamps work fine; the ID just needs uniqueness, not meaning.\n- **Tool-first adoption.**\n  Spending months configuring software before writing ten notes. Start with any tool; the method is the skill.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-zettelkasten",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-zettelkasten",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-zettelkasten",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-zettelkasten","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-zettelkasten\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]