SKILL.md

name	obsidian-scenario-vocabulary
description	Create story-and-dialogue-based English vocabulary notes for Obsidian or Markdown workspaces. Use when the user wants high-frequency English words learned through daily life, work, programming, or other real-world scenes, where words first appear naturally in a short scene or conversation before being explained.

Obsidian Scenario Vocabulary

Use this skill to create English vocabulary learning notes that bind words to real scenes, actions, conversations, and usage patterns. The default output language is Chinese unless the user asks otherwise.

By default, when creating a scenario vocabulary note, also create a matching English-definition companion note for the same target words. The companion note should use simple English definitions, keep the exact same word order and numbering, and be placed in a nearby folder such as 生活高频词汇英文释义 when the main notes live in 生活高频词汇.

Core Principle

Do not start from a simple English = Chinese list. Build this chain instead:

concrete scene -> short story/dialogue -> natural English sentences -> extracted words -> usage explanation

The story or dialogue is the learning anchor. Each word should answer:

• What happened in the scene before this word appeared?
• Where does this word appear in daily life or work?
• Why would someone say it in that scene?
• What words does it often appear with?
• What common misunderstanding should the learner avoid?

Workflow

1. Inspect the current workspace before writing files.

   • If it is an Obsidian vault or Markdown knowledge base, create or update Markdown notes in a sensible nearby knowledge area.
   • Do not hardcode a fixed destination. Choose a location from the repository structure and user intent.
   • Preserve existing notes and unrelated files.

2. Determine the vocabulary scope.

   • Use the user's requested count, level, and scenario if provided.
   • If the user only asks for common high-frequency vocabulary, choose a concrete everyday scene first, then select words that naturally fit that scene.
   • If the user has a profession or use case, include relevant scenario examples without turning the note into a technical glossary unless requested.

3. Design a concrete scene before writing detailed entries.

   • Pick one small event, not a broad category. Prefer scenes such as being late for the subway, ordering breakfast, missing a delivery, buying groceries, visiting a clinic, asking a coworker for help, or debugging a problem with a teammate.
   • Give the scene a short story title in Chinese, such as 迟到的地铁通勤, 咖啡店里的早晨, or 找不到钥匙的一天.
   • Use the story title, optionally with a numeric prefix, as the note filename. Avoid generic filenames such as 生活高频词, 英语词汇, or 30个单词.

4. Create a note with a clear structure.

   • Optional YAML frontmatter: title, created date, tags.
   • H1 title based on the story name.
   • A section near the top named 本文件词汇总览.
   • The complete word list before detailed entries.
   • In Obsidian-oriented notes, make every word in 本文件词汇总览 a section link to its detailed entry, using [[#N. word|word]] format, such as [[#1. open|open]].
   • A short learning principle explaining scene-first learning.
   • A 场景环境 section in Chinese that explains who is involved, where it happens, and what happens.
   • An 英文场景短文 section where the target words appear naturally in a short narrative.
   • An 英文对话 section when the scene plausibly includes people talking.
   • A 词汇拆解 section with one detailed entry per word.
   • A concise review method at the end.

5. Create a matching English-definition companion note unless the user explicitly asks for only the main scenario note.

   • Put it in a nearby sibling or child folder named clearly for English definitions, such as 生活高频词汇英文释义, English Definitions, or the closest naming convention already used in the vault.
   • Use the same numeric prefix and story title as the main note, adding a suffix such as -英文释义; for example, 09-楼下便利店买冰水-英文释义.md.
   • Link back to the source note near the top, such as Source note: [[生活高频词汇/09-楼下便利店买冰水.md|楼下便利店买冰水]].
   • Include a Target Words section whose links point to the companion note's own ## N. word sections.
   • Keep the target words, numbering, and order exactly the same as the main note.
   • Use simple English for definitions and usage notes. Avoid Chinese translations in this companion file unless the user asks for bilingual output.
   • Prefer short, learner-friendly English explanations over dictionary-style definitions.
   • Reuse the source scene sentence for each word when practical, so the English definition remains connected to the original scenario.

6. The story and dialogue must carry the vocabulary.

   • Do not list words first and then invent unrelated examples.
   • Make the target words appear in the story or dialogue before explaining them.
   • Bold the target words in the English story when useful for scanning.
   • Prefer ordinary spoken sentences over textbook examples.
   • Keep the English short enough that a beginner can reread it several times.

7. For each word in the main scenario note, use this entry template:

   ## N. word
   
   **在场景中出现：**
   
   > Natural sentence from the story or dialogue.
   
   解释这个词为什么在这个具体场景里出现，它表达了什么动作、状态、关系或感受。
   
   **核心感觉：** 一句话描述这个词背后的动作、状态或关系。
   
   **日常扩展：**
   
   - Natural English sentence. 中文场景说明。
   - Natural English sentence. 中文场景说明。
   - Natural English sentence. 中文场景说明。
   
   **常见搭配：**
   
   - phrase one：中文场景说明
   - phrase two：中文场景说明
   - phrase three：中文场景说明
   
   **注意：**
   
   说明一个容易误解的点，尤其是不要把这个词固定成单一中文释义。

8. For each word in the English-definition companion note, use this entry template:

   ## N. word
   
   **Simple English definition:** A short definition written with common words.
   
   **Use it when:** Explain the situation where people naturally use this word.
   
   **Common patterns:**
   
   - phrase one
   - phrase two
   - phrase three
   
   **Source scene sentence:**
   
   > Natural sentence from the main story or dialogue.
   
   **Quick check:** Give a short self-check prompt that asks the learner to make a new sentence in the same kind of situation.

9. Validate before finishing.

   • Count detailed entries and confirm they match the requested number.
   • Confirm 本文件词汇总览 contains every detailed entry word.
   • For Obsidian notes, confirm every word in 本文件词汇总览 is linked to the matching detailed entry heading, using the exact heading number and word, for example [[#12. wait|wait]].
   • Confirm the number of overview links matches the number of detailed entries, and that every link target exists as a ## N. word heading.
   • Confirm most or all target words appear in the story or dialogue before the detailed explanations.
   • Confirm the note is story/dialogue-based, not a translation table.
   • Confirm the file name is based on the story title, not a generic word-list name.
   • Confirm the file name and headings are readable in Obsidian or the Markdown workspace.
   • If a companion English-definition note is created, confirm it has the same number of target words, same numbering, same order, and a working link back to the source note.

Word Selection Guidance

For beginner daily-life notes, prefer high-frequency verbs and everyday action words:

• Movement and state: get, go, come, leave, stay, keep
• Handling things: take, put, bring, carry, hold, use
• Daily needs: need, want, have, buy, pay, eat, drink
• Perception and thinking: see, look, hear, know, think, feel
• Home actions: open, close, clean, wash, cook, sleep

For programmer or workplace notes, add work scenes only when relevant:

• read docs, get an error, run a command, fix a bug
• create a branch, make a commit, deploy a service
• send a request, receive a response, update a file

Keep the daily-life meaning primary unless the user specifically asks for technical English.

Output Style

• Write in Chinese for explanations by default.
• Keep English examples natural and short.
• Prefer common spoken sentences over textbook sentences.
• Use concrete scenes: waking up late, commuting, eating, shopping, cleaning, paying, messaging, asking for help, working, dealing with small problems.
• Start from one complete small event, then extract words from that event.
• Avoid long grammar lectures unless the user asks.
• Avoid dumping too many words into one note if it harms review quality; suggest splitting into numbered notes when appropriate.