You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -275,7 +276,8 @@ Update `session.md` after each round:
275
276
When all concepts mastered or user ends session:
276
277
277
278
1. Update `session.md` with final state.
278
-
2. Update `.claude/skills/teach-me/records/learner-profile.md` (keep under 30 lines):
279
+
2.**Generate learner-facing notes** — write `{topic-slug}-notes.md` in the topic directory. This is a standalone reference document the learner can review later. See "Notes Generation" below for format.
280
+
3. Update `.claude/skills/teach-me/records/learner-profile.md` (keep under 30 lines):
279
281
280
282
```markdown
281
283
# Learner Profile
@@ -293,7 +295,48 @@ Updated: {timestamp}
293
295
- Python decorators (8/10 concepts, 2025-01-15)
294
296
```
295
297
296
-
3. Give a brief text summary of what was covered, key insights, and areas for further study.
298
+
4. Give a brief text summary of what was covered, key insights, and areas for further study.
299
+
300
+
## Notes Generation
301
+
302
+
At session end, generate a learner-facing notes file at `{topic-slug}/{topic-slug}-notes.md`. This file is **written for the learner to review later**, not for the tutor. It should be self-contained and organized as a quick-reference.
303
+
304
+
### Notes Structure
305
+
306
+
```markdown
307
+
# {Topic} 核心笔记
308
+
309
+
## 1. {Section Name}
310
+
{Key concept, mechanism, or principle}
311
+
***One-line summary**: {what it does / why it matters}
1.**Start with "what & why"** before "how". Each section should answer: what is this, why does it exist, what problem does it solve.
333
+
2.**Use analogies sparingly but effectively**. Only include an analogy if it clarifies a non-obvious mechanism (e.g., "PagedAttention is like OS virtual memory paging").
334
+
3.**Include trade-offs**. Every optimization or design choice has a cost. Always state it (e.g., "TP improves throughput but increases communication latency").
335
+
4.**Code / command examples should be minimal**. Under 10 lines, self-contained, with comments explaining the key flags.
336
+
5.**Organize by concept dependency**, not by chronological teaching order. Foundation concepts first, advanced ones last.
337
+
6.**No quiz questions, no misconceptions, no tutor-side notes**. This is a clean reference document.
338
+
7.**Language matches the session**. If the session was in Chinese, notes are in Chinese (technical terms can stay in English).
339
+
8.**Keep it under 150 lines**. If it gets too long, the learner won't review it. Be ruthless about cutting fluff.
0 commit comments