Lecture Notes Master

Generate structured Obsidian lecture notes with recursive atomic decomposition:

• - 主笔记 (Main Note): Hub note with overview, core sections, summary, review questions
• 原子笔记 (Atomic Notes): Deep concept notes in ≥3 layers, each layer with rich structure
• 原子概念 (Glossary): Unlimited bilingual term definitions

When to Apply

Triggers:

• - User provides: URL, video link, PDF, transcript, PPT, slides, article
• User says: "总结", "summarize", "create notes", "lecture notes", "笔记", "做笔记"
• User mentions: Obsidian, atomic notes, wikilinks, PARA, MOC
• User provides content for note-taking or analysis
• Exam prep / study materials

Example prompts:

• - "总结一下这个视频 https://youtu.be/xxx"
• "Create lecture notes for this article"
• "帮我做笔记 https://www.example.com/article"
• "Summarize this into Obsidian notes"

---

User Profile

Configured in config.json:

• - Name: Schaefer (Zonghan Jia)
• University: Heidelberg University (ZITI), Computer Engineering
• Obsidian Vault: See config.json → INLINECODE2
• Output Directory: 00-Inbox/{Topic}/ (main note + glossary + numbered L1 subdirectories)
• Language: Bilingual — English primary, Chinese secondary
• Term format: INLINECODE4

---

Core Principles

Recursive Atomic Decomposition

Every source material is decomposed into a tree of notes, organized into numbered subdirectories by L1 topic:

CODEBLOCK0

Directory Organization Rules

Location	Contains	Example
INLINECODE5 root	Main note only	INLINECODE6
INLINECODE7

L1 note + its L2 children + their L3 children | 01-Installation-and-Setup/ | | glossary/ | All glossary entries | glossary/TUI（终端用户界面）.md | | assets/ | Generated charts/images | assets/performance-chart.png |

Numbering Rules:

1. 1. L1 subdirectories use two-digit prefix: 01-, 02-, 03-, ...
2. No atomic notes in the topic root — only the main hub note lives there
3. Within each L1 folder, all notes are flat (L1 + L2 + L3 together, no further nesting)
4. Numbering follows the order of L1 concepts as they appear in the main note
5. Wiki-links use filename only (no path prefix) — Obsidian resolves them automatically

Decomposition Rules

Layer 1 (顶层概念):

• - Source material's major themes, sections, or arguments
• Each L1 note covers ONE major concept branch
• Number: determined by content (typically 3-7, NOT fixed)

Layer 2 (子概念):

• - Sub-concepts, mechanisms, or components within each L1 concept
• Each L2 explains a specific aspect of its parent L1
• Number: typically 2-4 per L1 parent

Layer 3+ (细分解):

• - Specific mechanisms, case studies, comparisons, or evidence
• Finest granularity of analysis
• Number: as many as the content demands

Stop Decomposing When:

• - A concept can be fully explained in ≤500 words with one diagram
• Further splitting would break logical coherence
• The concept is better served as a glossary entry (pure definition)

Glossary vs Atomic Note:

Use Glossary	Use Atomic Note
Term needing a bilingual definition (1-3 sentences)	Concept requiring explanation, examples, diagrams
No deep analysis needed

Has sub-components worth exploring |
| Pure noun/term | Has "why", "how", comparison dimensions |

Minimum Requirement

Every set of notes MUST produce:

• - 1 main note (主笔记)
• ≥3 layers of atomic notes (L1 → L2 → L3 minimum)
• Glossary entries for ALL technical terms mentioned

Every Atomic Note Must Be Rich

ALL atomic notes (L1, L2, L3) use the same rich template structure:

1. 1. 定义 — One-paragraph definition with inline wikilinks
2. Why Do We Need This? — Motivation with concrete scenario
3. Core Concept — Idea + example + Mermaid diagram + step-by-step breakdown
4. Comparison — Table comparing with/without, or vs alternatives
5. Common Pitfalls — 2-3 mistakes and fixes (omit only if truly not applicable)
6. Key Takeaway — One flashcard-worthy sentence
7. Review Questions — 3 levels: recall, understanding, application
8. Related Notes — Parent (UP), children (DOWN), siblings (ACROSS)

See templates/atomic-note.md for the full template.

Writing Style: Runoob Tutorial（菜鸟教程风格）

Rule	Description
Step-by-step	"Why do we need this?" → "What is it?" → "How does it work?" → "Watch out for..."
Example-driven

Example FIRST, then explain the principle. Never start with pure theory | | Visual-rich | Every concept gets at least one Mermaid diagram OR table | | Table comparison | Similar concepts → comparison table | | Bilingual terms | English Term（中文）, English is primary | | Atomic | Each note covers exactly ONE concept | | Review questions | 3 per note: recall, understanding, application |

---

Prerequisites

CODEBLOCK1

Optional: summarize CLI for URL/video content extraction.

---

Workflow

Step 1: Analyze User Input

Identify: input type (URL, video, PDF, transcript, raw text), topic name, key themes.

URL & Video Content Extraction

When user provides a URL or video link, use summarize CLI:

CODEBLOCK2

Useful flags: --extract-only (raw text), --youtube auto, --firecrawl auto (JS-heavy sites), INLINECODE23

If summarize is not available: Use the agent's built-in web fetching tools as fallback.

Step 2: Plan Decomposition Tree

⚠️ MANDATORY: You MUST complete this step BEFORE writing ANY content.
⚠️ MANDATORY: You MUST create ALL directories with mkdir -p BEFORE writing ANY files.
⚠️ ZERO TOLERANCE: No atomic notes are allowed in the topic root directory. ONLY the main hub note lives there.

Plan the COMPLETE file tree with numbered directories, then create them immediately.

2a. Plan the tree (output to user for confirmation)

CODEBLOCK3

2b. Create ALL directories FIRST (before writing any files)

CODEBLOCK4

2c. Verify directory structure before proceeding

CODEBLOCK5

Only proceed to Step 3 after directories exist.

Step 3: Search Existing Resources

CODEBLOCK6

Step 4: Generate Notes (in order)

⚠️ CRITICAL: Every file MUST be written to its correct subdirectory. Double-check the output path before every Write/Edit call.

Order	Note Type	Write To	Example Path
1	Main note (hub)	INLINECODE26 root — ONLY file here	INLINECODE27
2

L1 atomic notes | {Topic}/NN-{L1-Concept}/ | Lazygit/01-Installation-and-Setup/Installation-and-Setup.md | | 3 | L2 atomic notes | Same dir as parent L1 | Lazygit/03-Basic-Git-Operations/Staging-and-Committing.md | | 4 | L3 atomic notes | Same dir as parent L1 | Lazygit/03-Basic-Git-Operations/Staging-Modes.md | | 5 | Glossary entries | {Topic}/glossary/ | Lazygit/glossary/Stage（暂存）.md | | 6 | Visualizations | {Topic}/assets/ | Lazygit/assets/workflow-chart.png |

Self-check before each file write:

• - Is this the main hub note? → Write to {Topic}/ root
• Is this an atomic note (L1/L2/L3)? → Write to INLINECODE37
• Is this a glossary entry? → Write to INLINECODE38
• NEVER write atomic notes directly to {Topic}/ root

Script Usage

CODEBLOCK7

Note: <SKILL_DIR> = the directory where this skill is installed. NN = two-digit L1 index (01, 02, ...).

Step 5: Generate Visualizations (as needed)

For data-driven charts that Mermaid cannot handle:

CODEBLOCK8

Available chart types: bar, line, scatter, timeline, heatmap, comparison, pie, radar

---

Output Format Templates

All templates are in the templates/ directory:

Type	Template File	Description
Main Note (主笔记)	INLINECODE51	Hub note with overview, N sections, summary, review questions
Atomic Note (原子笔记)

templates/atomic-note.md | Rich concept note — used for ALL layers (L1, L2, L3) |
| Glossary Entry (原子概念) | templates/glossary-entry.md | Short bilingual term definition |
| Course MOC | templates/course-moc.md | Map of Content with lecture index, concept clusters |

Main Note (主笔记) Key Requirements

• - YAML frontmatter: title, date, course/topic, tags, source_files, status, aliases
• Core Idea（核心思想）blockquote with inline INLINECODE55
• Source links
• Overview section (with image embed if available)
• N numbered sections (one per L1 concept, NOT limited to 3), each with:

- → 详见 [[L1-Atomic-Note]] link - Sub-sections: Why → What → How - Mermaid diagrams, comparison tables, key insight blockquotes

• - Summary section: concept map (Mermaid) + data summary table + key quote
• Review Questions: recall + understanding + application + critical thinking
• Related Notes linking to all L1 atomic notes

Atomic Note (原子笔记) Key Requirements

Same rich structure for ALL layers (L1, L2, L3):

• - YAML frontmatter: title (bilingual), date, tags, aliases
• One-paragraph 定义 with inline wikilinks
• Why Do We Need This? — motivation + concrete example
• Core Concept — idea + example/code + Mermaid diagram + step-by-step
• Comparison — table comparing alternatives or with/without
• Common Pitfalls — mistakes and how to avoid
• Key Takeaway — one flashcard-worthy sentence
• Review Questions — recall, understanding, application
• Related Notes — parent (UP) + children (DOWN) + siblings (ACROSS)

Glossary Entry (原子概念) Key Requirements

• - YAML frontmatter: title (bilingual), date, tags: [glossary, {topic-tag}], aliases
• One blockquote 定义 (1-3 sentences, bilingual)
• Related Notes linking to relevant atomic notes + main note

Cross-Reference Rules (CRITICAL)

All notes link in THREE directions:

Note Type	Links UP to	Links DOWN to	Links ACROSS to
Main Note	—	All L1 notes	—
L1 Atomic

Main Note | Its L2 children | Sibling L1 notes |
| L2 Atomic | Parent L1 | Its L3 children | Sibling L2 notes |
| L3 Atomic | Parent L2 | — | Sibling L3 notes |
| Glossary | Related atomic notes | — | Related glossary terms |

Inline wikilinks: All glossary terms MUST be linked inline on first mention in every note using [[Term（术语）]] syntax.

---

Wiki-Link Naming Convention (CRITICAL)

Wiki-link targets MUST match filenames (without .md). Spaces → hyphens in atomic notes, but glossary keeps parenthetical Chinese.

Note Type	File Name Pattern	Wiki-Link
Main Note	INLINECODE59	INLINECODE60
Atomic Note

{Concept-Name}.md | [[{Concept-Name}]] |
| Glossary Entry | {English Term（中文术语）}.md | [[{English Term（中文术语）}]] |

Rules:

1. 1. Before generating any notes, list ALL file names AND their target directories
2. NEVER leave wiki-links empty ([[]]) or with placeholder text ([[TODO]])
3. If a target note doesn't exist yet, use the correct future filename — Obsidian creates it on click
4. Glossary filenames include both English and Chinese: INLINECODE67
5. Wiki-links use filename only (no path) — Obsidian resolves across subdirectories automatically

---

Mermaid Diagram Guidelines

Diagram Type	Use For	Example
INLINECODE68	Hierarchies, flows, architectures	Concept trees, process chains
INLINECODE69

Time-ordered interactions | Data transfers, API calls |
| stateDiagram-v2 | State transitions | Lifecycle, mode changes |
| classDiagram | Object relationships | Class hierarchy |
| gantt | Timelines, parallel tasks | Project phases, pipeline |
| pie | Proportions | Distribution breakdown |
| xychart-beta | Data trends | Performance scaling |
| mindmap | Topic overview | Concept clustering |

Rules:

1. 1. NEVER use ASCII art — always Mermaid
2. Every diagram must have a title and labeled edges
3. Max 15-20 nodes per diagram
4. Use classDef for consistent colors
5. Use subgraphs for grouping

Color theme:

%%{init: {'theme': 'base', 'themeVariables': {'primaryColor': '#4CAF50', 'primaryTextColor': '#fff', 'primaryBorderColor': '#388E3C', 'lineColor': '#666', 'secondaryColor': '#FF9800', 'tertiaryColor': '#2196F3'}}}%%

---

Matplotlib Visualization

Use when Mermaid cannot express the data: performance bars, scaling curves, heatmaps, radar charts.

Rules: PNG at dpi=150, consistent colors (#4CAF50, #FF9800, #2196F3, #F44336), always include axis labels and title, reference as ![[filename.png]].

---

Search Reference

Domain	Use For	Example Keywords
INLINECODE83	Find existing bilingual terms	cuda, memory, 内存, 术语
INLINECODE84

Find diagram templates | flow, sequence, hierarchy, 图表 |
| writing | Get writing style rules | introduction, comparison, 规则 |
| questions | Get review question templates | recall, application, 考试 |

---

Quality Checklist

Content

• - [ ] WHY → WHAT → HOW structure for every concept (all layers)
• [ ] Example appears BEFORE theory in every concept note
• [ ] All terms bilingual: INLINECODE87
• [ ] Each atomic note covers exactly ONE concept

Decomposition

• - [ ] Decomposition tree planned BEFORE writing
• [ ] ALL file names AND target directories listed before generation
• [ ] ≥3 layers of atomic notes produced (L1 → L2 → L3 minimum)
• [ ] L1 covers major themes, L2 breaks down sub-concepts, L3 provides finest analysis
• [ ] Glossary entries for ALL technical terms mentioned

Visualization

• - [ ] NO ASCII art — use Mermaid
• [ ] Every concept has at least one diagram or table
• [ ] Similar concepts have comparison tables
• [ ] Diagrams have titles and labeled edges

Structure

• - [ ] YAML frontmatter complete (title, date, tags, aliases)
• [ ] [[wiki-links]] for all cross-references (inline + Related Notes)
• [ ] 3 review questions per atomic note: recall, understanding, application
• [ ] Related Notes with UP / DOWN / ACROSS links
• [ ] File naming: Concept-Name.md (hyphens for atomic notes)

Directory Organization

• - [ ] Main note in topic root (00-Inbox/{Topic}/)
• [ ] Atomic notes organized into numbered L1 subdirectories (01-xxx/, 02-xxx/)
• [ ] L2 and L3 notes placed inside their parent L1 subdirectory (flat, no further nesting)
• [ ] Glossary entries in glossary/ subdirectory
• [ ] No atomic notes left loose in topic root

Obsidian Compatibility

• - [ ] [[wiki-links]] syntax (not markdown links)
• [ ] Standard `mermaid fencing
• [ ] Images: INLINECODE97
• [ ] Tags: lowercase with hyphens

---

Tips

1. 1. Provide source material: URL, video link, PDF, transcript → better notes
2. Video links: Paste YouTube/Bilibili URLs directly; transcript auto-extracted
3. Be specific about topic: "这个视频的AI经济分析" > "总结一下"
4. Search glossary first: Reuse existing terms for cross-course consistency
5. Iterate: Generate base notes, then ask for deeper decomposition on specific branches
6. Cross-reference: Link related concepts across different note sets