session-notes

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Session Notes

会话笔记

Create and manage Obsidian notes using the Obsidian CLI for structured documentation.

使用Obsidian CLI创建和管理Obsidian笔记，实现结构化文档管理。

Workflow

工作流

target-vault --> select-type --> create-note --> populate
  --> preview --> confirm --> write --> link-related

Each note type has its own workflow. Use any type independently based on user needs.

target-vault --> select-type --> create-note --> populate
  --> preview --> confirm --> write --> link-related

每种笔记类型都有独立的工作流。可根据用户需求单独使用任意类型。

Context Loading Strategy

上下文加载策略

Load only the reference or guide matching the current trigger. Never load multiple simultaneously unless explicitly noted.

```
templates/*.md
```
are not loaded into context. The agent uses them as reference to compose note content.
Templates also live in the vault (
```
Templates/
```
) for manual use via Obsidian's Templates and Daily Notes plugins.

仅加载与当前触发词匹配的参考文档或指南。除非明确说明，否则切勿同时加载多个文档。

```
templates/*.md
```
不会加载到上下文中。Agent会将其作为参考来撰写笔记内容。
模板也存储在Vault的
```
Templates/
```
目录中，可通过Obsidian的Templates和Daily Notes插件手动使用。

Triggers

触发词

Trigger Pattern	Reference
Project, PRD, Design Doc, ADR, architecture	project.md
Company, job application, interview	company.md
Challenge, technical challenge, take-home, coding interview	challenge.md
Brag, achievement, accomplishment	brag.md
Daily, today, daily note, journal	daily.md
Conversation, session, save conversation, AI chat	conversation.md
Capture, save this, quick note, paste this	capture.md
Markdown, syntax, wikilink, callout, embed	markdown.md
Vault structure, organize vault	vault-structure.md

Notes:

```
markdown.md
```
and
```
vault-structure.md
```
are informational guides (no write operations).
All other references are note-creation workflows (compose, preview, confirm, write).

触发模式	参考文档
Project, PRD, Design Doc, ADR, architecture	project.md
Company, job application, interview	company.md
Challenge, technical challenge, take-home, coding interview	challenge.md
Brag, achievement, accomplishment	brag.md
Daily, today, daily note, journal	daily.md
Conversation, session, save conversation, AI chat	conversation.md
Capture, save this, quick note, paste this	capture.md
Markdown, syntax, wikilink, callout, embed	markdown.md
Vault structure, organize vault	vault-structure.md

注意事项：

```
markdown.md
```
和
```
vault-structure.md
```
是信息类指南（无写入操作）。
其他所有参考文档均为笔记创建工作流（撰写、预览、确认、写入）。

Cross-References

交叉引用

company --> challenge     (interview triggers challenge)
company --> brag          (interview learnings become achievements)
challenge --> brag        (completed challenge becomes achievement)
daily --> brag            (daily insights feed brag document)
project --> daily         (project work logged in daily notes)
conversation --> daily    (conversation insights logged in daily)
conversation --> brag     (conversation outcomes become achievements)

company --> challenge     (interview triggers challenge)
company --> brag          (interview learnings become achievements)
challenge --> brag        (completed challenge becomes achievement)
daily --> brag            (daily insights feed brag document)
project --> daily         (project work logged in daily notes)
conversation --> daily    (conversation insights logged in daily)
conversation --> brag     (conversation outcomes become achievements)

Guidelines

指南

DO:

Always verify vault with user before creating notes (
```
obsidian vaults verbose
```
)
Compose note content inline following
```
templates/*.md
```
structure
Preview the full note content and target path before writing, ask for confirmation
Check CLI availability with
```
which obsidian
```
; if unavailable, fall back to Write tool at vault path
Link related notes using Obsidian wiki-links
```
[[Note Name]]
```
Use Title Case for filenames (e.g.,
```
My Project.md
```
)
Ask user which vault when multiple vaults exist
Remember vault name after first confirmation to avoid repeated prompts
Use
```
obsidian search
```
to check if a note exists before creating
Run
```
obsidian help
```
or
```
obsidian help <command>
```
for up-to-date CLI reference
Use
```
silent
```
flag on
```
create
```
to avoid opening the note in Obsidian
For mid-file edits, resolve the absolute path with
```
obsidian vault info=path
```
combined with the note's relative path, then use the Edit tool directly
When templates in the skill are updated, remind user to sync vault copies (
```
Templates/
```
)

DON'T:

Overwrite or delete existing vault files -- always append, rename, or cancel
Assume vault location without confirmation
Create notes without user confirmation of content
Use templates for updates (templates are for new notes only)
Create duplicate notes - search first with
```
obsidian search query=<name>
```
Use absolute paths in wiki-links (always relative)

需要做：

在创建笔记前，始终与用户确认Vault（使用
```
obsidian vaults verbose
```
命令）
按照
```
templates/*.md
```
的结构在线撰写笔记内容
在写入前预览完整的笔记内容和目标路径，并请求用户确认
使用
```
which obsidian
```
检查CLI是否可用；若不可用，则回退到Write工具，在Vault路径下创建笔记
使用Obsidian的wiki链接
```
[[Note Name]]
```
关联相关笔记
文件名使用标题大小写（例如：
```
My Project.md
```
）
当存在多个Vault时，询问用户使用哪个Vault
首次确认后记住Vault名称，避免重复提示
创建前使用
```
obsidian search
```
检查笔记是否已存在
运行
```
obsidian help
```
或
```
obsidian help <command>
```
获取最新的CLI参考信息
在
```
create
```
命令中使用
```
silent
```
标志，避免在Obsidian中打开笔记
对于文件中部编辑，结合
```
obsidian vault info=path
```
和笔记的相对路径解析绝对路径，然后直接使用Edit工具
当skill中的模板更新时，提醒用户同步Vault中的副本（
```
Templates/
```
目录下的文件）

不要做：

覆盖或删除现有Vault文件——始终采用追加、重命名或取消操作
在未确认的情况下假设Vault位置
在未获得用户内容确认的情况下创建笔记
使用模板进行更新（模板仅用于新笔记）
创建重复笔记——先使用
```
obsidian search query=<name>
```
搜索
在wiki链接中使用绝对路径（始终使用相对路径）

Output

输出

Notes are created in the user's Obsidian vault:

Vault/
├── Projects/
├── Companies/
├── Challenges/
├── Brags/
├── Conversations/
├── Daily/
└── Templates/

笔记将创建在用户的Obsidian Vault中：

Vault/
├── Projects/
├── Companies/
├── Challenges/
├── Brags/
├── Conversations/
├── Daily/
└── Templates/

Error Handling

错误处理

Vault not found: ask user for correct vault name (
```
obsidian vaults verbose
```
)
Note already exists: ask to append, choose new name, or cancel
CLI not available for content: fall back to Write tool with content composed from templates
Obsidian CLI not available: fall back to Write tool to create the file directly at the vault path; ask user for vault path on first use
Empty required fields: prompt user for missing information

Vault未找到：询问用户正确的Vault名称（使用
```
obsidian vaults verbose
```
命令）
笔记已存在：询问用户是追加内容、选择新名称还是取消操作
CLI无法处理内容：回退到Write工具，使用模板撰写的内容创建笔记
Obsidian CLI不可用：回退到Write工具，直接在Vault路径下创建文件；首次使用时询问用户Vault路径
必填字段为空：提示用户补充缺失信息