Karpathy's LLM Wiki: build/query interlinked markdown KB with Zettelkasten note discipline. Triggers: 知識庫, 建 wiki, wiki 筆記, 研究筆記, ingest sources, knowledge base.
Use when building, maintaining, or auditing a Zettelkasten (slip-box) note system, or when applying atomic-note discipline to an existing markdown knowledge base — atomicity checks, card-splitting decisions, linking rules, note-type workflow. Trigger on 卡片盒筆記法、卡片盒、Zettelkasten、原子筆記、永久筆記、文獻筆記、結構筆記、拆卡、筆記連結、smart notes、atomic notes、permanent notes、slip-box, or when another skill (e.g. llm-wiki) needs per-change note-discipline checks.
Use whenever the agent thinks at all — writing copy or reports, proposals, planning products or features, coding, debugging, or any other task — running ALL curated thinking frameworks in sequence (currently 邏輯推導 logical reasoning：MECE, 空雨傘, 魚骨圖; 創意發想 creative ideation：六頂思考帽, 腳本圖, 心智圖; 市場分析 market analysis：3C 分析, SWOT 分析, 4P與4C; 進度管理 progress management：惠特默模型, KPI 樹狀圖, PDCA; 權衡得失 weighing trade-offs：決策矩陣, PMI 表, 力場分析; 預測未來 predicting the future：S 型曲線, 鴻溝理論, 長尾模型; 辯論思考 debate thinking：需根解損, 判定立駁, 論點以主張-資料-推論三要素構建 Claim-Data-Warrant、以質詢拆解三問檢驗（事實為真？邏輯嚴密？有無其他可能？）; 思維模型 mental models：第一性原理, 反向思考法, 二階思考, 能力圈, 奧坎剃刀) to lock direction and key points before acting, screening all reasoning with a ~160-item 謬誤檢核清單 fallacy checklist. Theme grouping is navigation only — work through every theme, not just the ones that look relevant. Trigger on ultrathink, 深度思考, 想清楚再做, 思考框架, 抓重點, 言之有物, 沒抓到重點, any framework or tool name above, or whenever a task involves thinking, planning, writing, building, or debugging.
Use by default for any user-facing writing, including answers to users, emails, documents, formal correspondence, reports, proposals, landing-page copy, social posts, essays, commentary, explanations, summaries, product copy, internal updates, and other prose intended to be read by people. Apply it whenever the output contains human-readable text, unless another skill explicitly owns the writing style or the output is purely code, structured data, or a command. Supports Chinese and English.
Software engineering guidelines for any software change. Always load this skill before requirement clarification, architecture/design, implementation, refactoring, code review, testing, or shipping. Covers simplicity, surgical changes, TDD, and verifiable success criteria. Triggers on: 任何軟體規劃, 需求釐清, 架構設計, 寫 code, 改 code, 做功能, 修 bug, refactor, 開發, coding, development, 實作, 實現, 寫程式, 改程式, 加功能, 修問題, code review, 測試, 重構
Universal database engineering rules. Migration discipline, audit logging, soft delete, performance, data integrity. Triggers on: 任何資料庫相關工作, 建表, 改 schema, 寫 migration, DB design, database development, 設計資料庫, 改 DB 結構, 加欄位, 加索引, 改 table, SQL, 寫 trigger, 設計 API 的 DB 層, 查詢很慢, N+1, 效能優化, 資料完整性, CASCADE, 外鍵, 新增 table, 刪除資料, backup, 環境分離, dev prod 分開
Use when analyzing a group, business-unit, product-line, or brand portfolio with the BCG growth-share matrix, especially when the task involves relative market share, market growth, quadrant classification, capital allocation, portfolio prioritization, or deciding whether to invest, maintain, harvest, reposition, or exit.
Use when designing, evaluating, or refining a business model with nine elements, especially for new products, pivots, monetization, and go-to-market decisions. Starts with Epicenter Selection (震央選擇) — choosing one of four innovation starting points (資源／產品／顧客／財務導向) to anchor design before filling the nine boxes.