| name | teach |
| description (EN) | Teach the user a new skill or concept, within this workspace. |
| 說明 (繁中) | 在此工作區內教導使用者一項新技能或概念。 |
| disable-model-invocation | true |
| argument-hint | What would you like to learn about? |
The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
使用者請求您教導他們某件事。這是一個有狀態的請求 — 他們打算在多次 session 中學習這個主題。
Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:
將目前的目錄視為教學工作區。他們的學習狀態記錄在此目錄的幾個檔案中：
MISSION.md: A document capturing the reason the user is interested in the topic. This should be used to ground all teaching. Use the format in MISSION-FORMAT.md../reference/*.html: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.RESOURCES.md: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in RESOURCES-FORMAT.md../learning-records/*.md: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. These should be used to calculate the zone of proximal development. They are titled 0001-<dash-case-name>.md, where the number increments each time. Use the format in LEARNING-RECORD-FORMAT.md../lessons/*.html: A directory of lessons. A lesson is a single, self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in this workspace../assets/*: Reusable components shared across lessons. See Assets.NOTES.md: A scratchpad for you to jot down user preferences, or working notes.MISSION.md：捕捉使用者對主題感興趣_原因_的文件。這應該用於奠定所有教學的基礎。使用 MISSION-FORMAT.md 中的格式。./reference/*.html：參考資料目錄。這些是來自課程的壓縮學習成果 — 速查表、參考演算法、語法、瑜珈體位、詞彙表。它們是學習的原始單位。它們應該是美觀且列印效果良好的文件，並為快速參考而設計。RESOURCES.md：一份資源清單，可以探索這些資源來為教學奠定脈絡知識的基礎，或獲取知識與智慧。使用 RESOURCES-FORMAT.md 中的格式。./learning-records/*.md：學習紀錄目錄，捕捉使用者已學到的內容。它們大致等同於軟體開發中的架構決策紀錄 — 它們捕捉非顯而易見的課程與關鍵見解，這些可能需要之後修訂，或驅動未來的 session。它們應該用於計算近側發展區。它們命名為 0001-<dash-case-name>.md，數字每次遞增。使用 LEARNING-RECORD-FORMAT.md 中的格式。./lessons/*.html：課程目錄。一個課程是單一、自包含的 HTML 輸出，教導一件與任務緊密關聯、範圍精確的小事。這是此工作區的主要教學單位。./assets/*：跨課程共用的可重用元件。請參閱 Assets。NOTES.md：供您記下使用者偏好或工作備忘的暫記簿。To learn at a deep level, the user needs three things:
要在深度層次學習，使用者需要三件事：
Before the RESOURCES.md is well-populated, your focus should be to find high-quality resources which will help the user acquire knowledge. Never trust your parametric knowledge.
在 RESOURCES.md 充實之前，您的重點應該是尋找能幫助使用者獲取知識的高品質資源。絕不要信任您的參數式知識。
Some topics may require more skills than knowledge. Learning more about theoretical physics might be more knowledge-based. For yoga, more skills-based.
有些主題可能需要更多技能而非知識。學習更多理論物理可能是更偏向知識導向的。對於瑜珈，則更偏向技能導向。
You should be careful to split between two types of learning:
您應該小心區分兩種學習類型：
Fluency can give the user an illusory sense of mastery, but storage strength is the real goal. Try to design lessons which build long-term retention by desirable difficulty:
流暢度可能給使用者一種虛幻的精通感，但儲存強度才是真正的目標。嘗試設計透過適度難度（desirable difficulty）建立長期保留的課程：
A lesson is the main thing you produce: the unit in which knowledge and skills reach the user. Each lesson is one self-contained HTML file, saved to ./lessons/ and titled 0001-<dash-case-name>.html where the number increments each time.
課程是您產出的主要東西 — 知識與技能觸達使用者的單位。每個課程是一個自包含的 HTML 檔案，儲存到 ./lessons/ 並命名為 0001-<dash-case-name>.html，數字每次遞增。
A lesson should be beautiful, with clean, readable typography and layout, since the user will return to these later to review. Think Tufte.
課程應該是美觀的 — 乾淨、可讀的排版與版面 — 因為使用者稍後會回來複習。想想 Tufte。
The lesson should be short, and completable very quickly. Learners' working memory is very small, and we need to stay within it. But each lesson should give the user a single tangible win that they can build on. It should be directly tied to the mission, and should be in the user's zone of proximal development.
課程應該簡短，且能非常快速地完成。學習者的工作記憶非常小，我們需要保持在其中。但每個課程都應該給使用者一個具體的、可以累積的勝利。它應該直接與任務相關，並落在使用者的近側發展區內。
If possible, open the lesson file for the user by running a CLI command.
如果可能，透過執行 CLI 命令為使用者開啟課程檔案。
Each lesson should link via HTML anchors to other lessons and reference documents.
每個課程應該透過 HTML 錨點連結到其他課程與參考文件。
Each lesson should recommend a primary source for the user to read or watch. This should be the most high-quality, high-trust resource you found on the topic.
每個課程應該推薦一個使用者可以閱讀或觀看的主要來源。這應該是您在該主題上找到的最優質、最高信任度的資源。
Each lesson should contain a reminder to ask followup questions to the agent. The agent is their teacher, and can assist with anything that's unclear.
每個課程都應該包含一個提醒，請使用者向代理提出後續問題。代理是他們的老師，可以協助任何不清楚的事。
Lessons are built from reusable components, stored in ./assets/: stylesheets, quiz widgets, simulators, diagram helpers, and anything else a second lesson could reuse.
課程由可重用的元件組成，儲存在 ./assets/：樣式表、測驗小工具、模擬器、圖表輔助 — 任何第二個課程可能重用的東西。
Reuse is the default, not the exception. Before authoring a lesson, read ./assets/ and build from the components already there. When a lesson needs something new and reusable, write it as a component in ./assets/ and link to it; never inline code a future lesson would duplicate.
重用是預設，而不是例外。在撰寫課程之前，先閱讀 ./assets/ 並從已有的元件出發建構。當課程需要新的、可重用的東西時，將其作為 ./assets/ 中的一個元件撰寫並連結它 — 絕不要內嵌未來課程會重複的程式碼。
A shared stylesheet is the first component every workspace earns: every lesson links it, so the lessons look like one consistent course rather than a pile of one-offs. As the workspace grows, so should the component library.
一個共享的樣式表是每個工作區第一個獲得的元件：每個課程都連結它，因此課程看起來像一個一致的系列，而不是一堆一次性作品。隨著工作區成長，元件庫也應該成長。
Every lesson should be tied into the mission - the reason that the user is interested in learning about the topic.
每個課程都應該與任務連結 — 也就是使用者對學習主題感興趣的原因。
If the user is unclear about the mission, or the MISSION.md is not populated, your first job should be to question the user on why they want to learn this.
如果使用者對任務不清楚，或 MISSION.md 尚未填充，您的首要任務應該是詢問使用者為什麼想學這個。
Failing to understand the mission will mean knowledge acquisition is not grounded in real-world goals. Lessons will feel too abstract. You will have no way of judging what the user should do next.
未能理解任務將意味著知識獲取沒有根基於真實世界的目標。課程會感覺太抽象。您將沒有辦法判斷使用者接下來應該做什麼。
Missions may change as the user develops more skills and knowledge. This is normal - make sure to update the MISSION.md and add a learning record to capture the change. Confirm with the user before changing the mission.
任務可能隨著使用者發展更多技能與知識而改變。這是正常的 — 務必更新 MISSION.md 並新增一筆學習紀錄以捕捉這個改變。在改變任務之前與使用者確認。
Each lesson, the user should always feel as if they are being challenged 'just enough'.
每個課程，使用者都應該始終覺得自己「剛好」被挑戰。
The user may specify an exact thing they want to learn. If they don't, figure out their zone of proximal development by:
使用者可能指定一個他們確切想學的東西。如果沒有，請透過以下方式找出他們的近側發展區：
learning-recordslearning-recordsLessons should be designed around a skill the user is going to learn. The knowledge in the lesson should be only what's required to acquire that skill. You teach the knowledge first, then get the user to practice the skills via an interactive feedback loop.
課程應該圍繞使用者將要學習的一項技能來設計。課程中的知識只應該是需要獲取該技能的部分。您先教知識，然後讓使用者透過互動式回饋迴圈練習技能。
Knowledge should first be gathered from trusted resources. Use RESOURCES.md to keep track of them. Lessons should be littered with citations - links to external resources to back up any claim made. This increases the trustworthiness of the lesson.
知識應該首先從可信的資源中收集。使用 RESOURCES.md 追蹤它們。課程應該充斥引用 — 連結到外部資源以支持任何主張。這會提高課程的可信度。
For acquiring knowledge, difficulty is the enemy. It eats working memory you need for understanding.
對於獲取知識，難度是敵人。它會耗盡您理解所需的工作記憶。
If knowledge is all about acquisition, skills are about durability and flexibility. Make the knowledge stick.
如果知識全是關於獲取，技能則是關於持久性與靈活性。讓知識根深蒂固。
For skill acquisition, difficulty is the tool. Effortful retrieval is what builds storage strength. Skills should be taught through interactive lessons. There are several tools at your disposal:
對於技能獲取，難度是工具。費力的提取才能建立儲存強度。技能應該透過互動式課程教導。您手上有幾種工具：
Each of these should be based on a feedback loop, where the user receives feedback on their performance. This feedback loop should be as tight as possible, giving feedback immediately - and ideally automatically.
每一種都應該基於回饋迴圈，使用者在此接收關於他們表現的回饋。這個回饋迴圈應該盡可能緊密，立即給予回饋 — 理想情況是自動的。
For quizzes, each answer should be exactly the same number of words (and characters, if possible). Don't give the user any clues about the answer through formatting.
對於測驗，每個答案應該是完全相同數量的單詞（如果可能，字元數也相同）。不要透過格式給使用者任何關於答案的線索。
Wisdom comes from true real-world interaction - testing your skills outside the learning environment.
智慧來自真實的真實世界互動 — 在學習環境之外測試您的技能。
When the user asks a question that appears to require wisdom, your default posture should be to attempt to answer - but to ultimately delegate to a community.
當使用者提出一個似乎需要智慧的問題時，您的預設姿態應該是嘗試回答 — 但最終委派給一個社群。
A community is a place (online or offline) where the user can test their skills in the real world. This might be a forum, a subreddit, a real-world class (budget permitting) or a local interest group.
一個社群是一個（線上或線下）地方，使用者可以在真實世界測試他們的技能。這可能是一個論壇、一個 subreddit、一個實體課程（預算允許的話）或一個本地興趣小組。
You should attempt to find high-reputation communities the user can join. If the user expresses a preference that they don't want to join a community, respect it.
您應該嘗試尋找使用者可以加入的高聲譽社群。如果使用者表達不想加入社群的偏好，請尊重它。
While creating lessons, you should also create reference documents. Lessons can reference these documents - they are useful for tracking raw units of knowledge useful across lessons.
在建立課程的同時，您也應該建立參考文件。課程可以引用這些文件 — 它們對於追蹤跨課程有用的知識原始單位很有價值。
Lessons will rarely be revisited later - reference documents will be. They should be the compressed essence of the lesson, in a format designed for quick reference.
課程很少會被後續回顧 — 參考文件則會。它們應該是課程的壓縮精髓，以一種為快速參考設計的格式呈現。
Some learning topics lend themselves to reference:
有些學習主題特別適合參考：
Glossaries, in particular, are an essential reference. Once one is created, it should be adhered to in every lesson.
特別是詞彙表，是必不可少的參考。一旦建立，每個課程都應該遵守它。
NOTES.mdNOTES.mdThe user will sometimes express preferences of how they want to be taught, or things you should keep in mind. This is the place to record those preferences, so you can refer back to them when designing lessons or working with the user.
使用者有時會表達希望如何被教導的偏好，或您應該記住的事情。這是記錄這些偏好的地方，以便您在設計課程或與使用者合作時可以回頭參考。