Course Learning and Obsidian Notes

Read references/course-note-workflow.md completely before handling the course material. It contains the user's full teaching workflow, final-note schema, formatting rules, and quality checks.

Operating modes

• When the user wants guided study, establish the lesson framework first, teach one module at a time, and wait for the user's answer after each learning check.
• When the user asks for a Markdown file, a complete summary, or a final Obsidian note, skip the interactive pauses and produce the complete standalone note directly.
• Inspect the entire source before drafting. Use the relevant presentation or PDF workflow when visual content, formulas, charts, or slide layout must be read.
• Save a real UTF-8 Markdown file in the requested Vault location when filesystem access permits. Preserve the user's existing folders and naming conventions.
• Do not invent missing metadata. Use unknown as required by the reference.

Concept-link invariant

• Before finalizing a lecture note, inspect the course's existing concept folder when it is available.
• In # 核心知识, add a wikilink at a concept's first occurrence when either the matching Concept note already exists or the concept is important, reusable, and worth becoming a future Concept note. Use aliases such as [[伪随机码|PRN 码]] when the displayed lecture term differs from the Concept filename.
• A missing Concept file is not a blocker: create the meaningful [[待建概念]] link and leave the note content for the user to add later. Do not automatically create the Concept file unless the user asks.
• Link only the first occurrence in # 核心知识; do not repeatedly link the same concept throughout that section.
• Keep the entire # 🔑 关键词 table as plain text. Do not place wikilinks in its keyword, explanation, or related-knowledge cells.

Collapsible answer invariant

Final notes must render reference answers as a collapsed Obsidian callout:

[!question]- 点击查看参考答案

基础题答案

1. 答案内容

Continue every answer line, blank separator, heading, and display-math line with the blockquote marker (>). Use valid LaTeX inside the callout; do not escape subscript underscores inside math. Reset numbering to 1 within each answer group.

Never use HTML details or summary tags for answer sections. Before delivery, verify that the note contains the collapsed question callout and contains no such HTML tags.