1. 專案概述 (Project Overview) - What the project does, who it's for, the problem it solves
2. 技術架構 (Technical Architecture) - System design, data flow, key components and how they connect
3. 程式碼結構 (Codebase Structure) - Directory layout, important files, where to find things
4. 技術選型 (Technology Stack) - What's used and why we chose it over alternatives
5. 設計決策 (Design Decisions) - The "why" behind architectural choices, trade-offs considered
6. 學習心得 (Lessons Learned) - Bugs encountered, pitfalls to avoid, best practices discovered
7. 工程師思維 (How Good Engineers Think) - Patterns, mental models, debugging approaches used

• Engaging, not boring - Write like explaining to a curious friend, not a textbook
• Use analogies - Compare complex concepts to everyday things
• Include anecdotes - "We tried X, it broke because Y, so we did Z"
• Be specific - Real file names, real error messages, real solutions
• Show the journey - Include the mistakes, not just the final answer

+--------+     +--------+     +---------+     +--------+     +--------+
| Explore| --> |  Read  | --> | Analyze | --> |  Write | --> |  Save  |
+--------+     +--------+     +---------+     +--------+     +--------+

圖例：
- Explore = 探索程式碼結構
- Read = 閱讀核心檔案
- Analyze = 分析架構模式
- Write = 撰寫學習文件
- Save = 儲存到專案根目錄

1. 圖形內使用英文標籤（確保對齊）
2. 圖形下方附上中文圖例對照
3. 標籤簡短，詳細說明放圖例

1. Explore codebase structure (

   ls

   , file patterns)
2. Read key files (entry points, configs, core modules)
3. Identify architecture patterns and tech decisions
4. Note any documented bugs/issues in git history or comments
5. Write FOR[username].md with all sections in Taiwan Traditional Chinese
6. Save to project root

"Create a learning doc for this project" "Help me understand this codebase" "Write a FOR[myname].md explaining everything" "/learn-tw"

project/
├── src/           # 主要程式碼
│   ├── core/      # 核心邏輯
│   └── utils/     # 工具函式
├── tests/         # 測試
└── config/        # 設定檔

• src/main.ts

  - 進入點

• src/core/engine.ts

  - 核心引擎

• A：[方案 A]
• B：[方案 B]

• [實踐 1]
• [實踐 2]