refactor(vault): Phase 4 — 06_Metadata slimming 42 → 8
Keep (8 files, all wired to .obsidian): - Templates: Daily Note Template, Project Template, book-note, quick-note - Reference: PARA_METHOD, GIT_WORKFLOW, TROUBLESHOOTING - SECURITY_ROTATION_LOG_2026-02 Delete (27 files): upstream claudesidian remnants (CHANGELOG, CONTRIBUTING, CLAUDE-BOOTSTRAP, etc.), 4 workflow docs, review reports, improvement plans, Hermes templates, duplicate/unwired templates Archive to 04_Archive/Metadata-Docs (8 files): review reports, plugin manuals, DAILY_NOTE_GUIDE, Common Claude Code Prompts
This commit is contained in:
windyboy
@@ -0,0 +1,170 @@
|
||||
# Common Claude Code Prompts
|
||||
|
||||
A collection of useful prompts for working with Claude Code in your vault.
|
||||
|
||||
## Starting Work
|
||||
|
||||
### Beginning a Session
|
||||
```
|
||||
I'm starting work for today.
|
||||
Can you review what I was working on yesterday
|
||||
and help me pick up where I left off?
|
||||
```
|
||||
|
||||
### Setting the Mode
|
||||
```
|
||||
I'm in thinking mode, not writing mode.
|
||||
Please help me explore [topic] by asking questions
|
||||
and searching for relevant notes.
|
||||
```
|
||||
|
||||
## Research & Synthesis
|
||||
|
||||
### Finding Connections
|
||||
```
|
||||
Search my vault for anything related to [topic].
|
||||
What patterns or connections do you see?
|
||||
```
|
||||
|
||||
### Synthesizing a Project
|
||||
```
|
||||
Review all notes in [project folder].
|
||||
Create a synthesis of the key themes, insights, and open questions.
|
||||
```
|
||||
|
||||
### Weekly Review
|
||||
```
|
||||
Look at all notes created this week.
|
||||
What are the main themes?
|
||||
What connections exist between different projects?
|
||||
```
|
||||
|
||||
## Organization
|
||||
|
||||
### Processing Inbox
|
||||
```
|
||||
Review items in 00_Inbox.
|
||||
Suggest where each should be moved based on PARA method.
|
||||
Which items could be combined or linked?
|
||||
```
|
||||
|
||||
### Finding Orphans
|
||||
```
|
||||
Find notes that aren't linked to any other notes.
|
||||
Suggest potential connections.
|
||||
```
|
||||
|
||||
### Cleaning Attachments
|
||||
```
|
||||
Review files in 05_Attachments.
|
||||
Which ones aren't referenced in any notes?
|
||||
Which could be better named?
|
||||
```
|
||||
|
||||
## Writing & Creation
|
||||
|
||||
### Moving to Writing Mode
|
||||
```
|
||||
I'm ready to move from thinking to writing mode.
|
||||
Based on our research in [project],
|
||||
help me create an outline for [deliverable].
|
||||
```
|
||||
|
||||
### Improving a Draft
|
||||
```
|
||||
Review [document].
|
||||
Don't rewrite it, but give me specific feedback on:
|
||||
- Structure and flow
|
||||
- Gaps in logic or evidence
|
||||
- Areas that need clarification
|
||||
```
|
||||
|
||||
## Learning & Development
|
||||
|
||||
### Exploring a New Topic
|
||||
```
|
||||
I want to learn about [topic].
|
||||
Start by searching my vault for any existing knowledge.
|
||||
Then help me identify what I need to research.
|
||||
```
|
||||
|
||||
### Making an Argument
|
||||
```
|
||||
I'm trying to argue that [thesis].
|
||||
Search my notes for supporting evidence.
|
||||
What counterarguments should I address?
|
||||
```
|
||||
|
||||
## Project Management
|
||||
|
||||
### Project Status
|
||||
```
|
||||
Review the project in [folder].
|
||||
What's the current status?
|
||||
What are the next actions needed?
|
||||
```
|
||||
|
||||
### Creating a Retrospective
|
||||
```
|
||||
[Project] is now complete.
|
||||
Review all notes and create a retrospective covering:
|
||||
- What was accomplished
|
||||
- Key learnings
|
||||
- What to do differently next time
|
||||
```
|
||||
|
||||
## Daily Operations
|
||||
|
||||
### Morning Review
|
||||
```
|
||||
Good morning. Show me:
|
||||
- Any notes modified yesterday
|
||||
- Open tasks or questions
|
||||
- What should I focus on today?
|
||||
```
|
||||
|
||||
### End of Day Wrap-up
|
||||
```
|
||||
End of day review:
|
||||
- What did I accomplish today?
|
||||
- What questions or ideas emerged?
|
||||
- What should I prioritize tomorrow?
|
||||
```
|
||||
|
||||
## Advanced Techniques
|
||||
|
||||
### Cross-Project Analysis
|
||||
```
|
||||
Compare insights from [Project A] and [Project B].
|
||||
What patterns exist across both?
|
||||
What could each learn from the other?
|
||||
```
|
||||
|
||||
### Knowledge Gaps
|
||||
```
|
||||
Analyze my notes on [topic].
|
||||
What aspects am I missing?
|
||||
What questions haven't I asked?
|
||||
```
|
||||
|
||||
### Idea Development
|
||||
```
|
||||
I have this rough idea: [idea]
|
||||
Search for related concepts in my vault.
|
||||
Help me develop this into something more concrete.
|
||||
```
|
||||
|
||||
## Tips for Effective Prompts
|
||||
|
||||
1. **Be specific about mode** (thinking vs writing)
|
||||
2. **Reference specific folders** when relevant
|
||||
3. **Ask for questions**, not just answers
|
||||
4. **Request synthesis**, not just search
|
||||
5. **Iterate freely** - have a conversation
|
||||
|
||||
## Remember
|
||||
|
||||
- Claude Code has access to your entire vault
|
||||
- It can create, edit, and organize files
|
||||
- Use it as a thinking partner, not just a tool
|
||||
- The best prompts emerge from your specific needs
|
||||
@@ -0,0 +1,448 @@
|
||||
---
|
||||
created: 2026-01-06
|
||||
type: reference
|
||||
tags: [reference, daily-workflow, tutorial]
|
||||
---
|
||||
|
||||
# 每日日记完整指南
|
||||
|
||||
**快速创建每日笔记的三种方式**
|
||||
|
||||
---
|
||||
|
||||
## 📋 方式一：命令行创建（最快）
|
||||
|
||||
### 基础用法
|
||||
|
||||
```bash
|
||||
# 创建今日普通日记（文件名：YYYY-MM-DD.md）
|
||||
pnpm daily-note
|
||||
|
||||
# 创建带主题的日记（文件名：YYYY-MM-DD - 主题.md）
|
||||
pnpm daily-note "学习 Claude Code"
|
||||
pnpm daily-note "项目会议"
|
||||
pnpm daily-note "阅读笔记"
|
||||
```
|
||||
|
||||
### 适用场景
|
||||
- ✅ 习惯使用命令行
|
||||
- ✅ 需要快速捕获想法
|
||||
- ✅ 在终端工作
|
||||
- ✅ 配合 Git 提交流程
|
||||
|
||||
### 示例
|
||||
|
||||
```bash
|
||||
# 早上启动时
|
||||
git pull
|
||||
pnpm daily-note "今日工作计划"
|
||||
# 编辑文件，开始工作...
|
||||
|
||||
# 晚上结束时
|
||||
pnpm daily-note "今日总结"
|
||||
# 编辑文件，总结当天
|
||||
git add .
|
||||
git commit -m "daily: $(date +%Y-%m-%d)"
|
||||
git push
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 📱 方式二：Obsidian 插件（图形界面）
|
||||
|
||||
### Templater 插件 - 自动模板应用
|
||||
|
||||
**配置位置**：`.obsidian/plugins/templater-obsidian/data.json`
|
||||
|
||||
当前配置已启用：
|
||||
- 模板文件夹：`06_Metadata/Templates`
|
||||
- 在 `00_Inbox/` 创建文件时，自动应用 `Daily Note Template.md`
|
||||
- 在 `01_Projects/` 创建文件时，自动应用 `Project Template.md`
|
||||
|
||||
#### 使用步骤
|
||||
|
||||
1. **打开 Obsidian**
|
||||
2. **导航到 `00_Inbox/` 文件夹**
|
||||
3. **点击"创建笔记"图标**（或快捷键 `Ctrl+N`）
|
||||
4. **输入文件名**（建议格式：`YYYY-MM-DD - 主题`）
|
||||
5. **按 Enter 创建**
|
||||
6. **Templater 自动填充模板**
|
||||
|
||||
#### 模板对比
|
||||
|
||||
**英文模板**（自动应用）：
|
||||
```
|
||||
# 2026-01-06
|
||||
|
||||
## Capture
|
||||
-
|
||||
|
||||
## Questions
|
||||
-
|
||||
|
||||
## Insights
|
||||
-
|
||||
|
||||
## Connections
|
||||
-
|
||||
|
||||
## For Tomorrow
|
||||
-
|
||||
|
||||
---
|
||||
← [[2026-01-05]] | [[2026-01-07]] →
|
||||
```
|
||||
|
||||
**中文模板**（手动应用）：
|
||||
```
|
||||
---
|
||||
date: 2026-01-06
|
||||
day: Monday
|
||||
week: 2026-W02
|
||||
type: daily-note
|
||||
---
|
||||
|
||||
# 2026年01月06日 星期一
|
||||
|
||||
## 📋 今日任务
|
||||
- [ ]
|
||||
|
||||
## 📝 工作笔记
|
||||
|
||||
|
||||
## 💡 想法与灵感
|
||||
|
||||
|
||||
## 📚 学习记录
|
||||
|
||||
|
||||
## 🎯 重点事项
|
||||
|
||||
|
||||
## 📊 总结
|
||||
|
||||
|
||||
---
|
||||
← [[2026-01-05]] | [[2026-01-07]] →
|
||||
```
|
||||
|
||||
#### 手动应用模板
|
||||
|
||||
如果不想使用自动模板，可以：
|
||||
|
||||
1. **快捷键 `Ctrl+E`**（打开 Templater 命令面板）
|
||||
2. **选择模板**
|
||||
- `daily-note.md`（中文版本，带日期链接）
|
||||
- `Daily Note Template.md`（英文简单版）
|
||||
3. **模板插入到当前文件**
|
||||
|
||||
#### 创建快捷键
|
||||
|
||||
**在 Obsidian 设置中**：
|
||||
1. `设置` → `快捷键` → 搜索 "Templater"
|
||||
2. 找到 "Open Insert Template modal"
|
||||
3. 设置快捷键（例如：`Ctrl+Shift+T`）
|
||||
|
||||
### QuickAdd 插件 - 高级自动化
|
||||
|
||||
**当前配置**：QuickAdd 已安装但未配置任何 Choice（需要手动设置）
|
||||
|
||||
#### 配置 QuickAdd 创建日记
|
||||
|
||||
**步骤 1：在 Obsidian 中打开 QuickAdd 设置**
|
||||
- `设置` → `社区插件` → `QuickAdd` → `Manage`
|
||||
|
||||
**步骤 2：创建新 Choice**
|
||||
- 点击 `+ Create Choice`
|
||||
- 名称：`Daily Note`
|
||||
- 类型：`Template`
|
||||
|
||||
**步骤 3：配置 Template 选项**
|
||||
- **Template Path**: `06_Metadata/Templates/daily-note.md`
|
||||
- **File Name Format**: `{{DATE:YYYY-MM-DD}}`
|
||||
- **File Location**: `00_Inbox`
|
||||
- **Open**: `Create new tab`
|
||||
|
||||
**步骤 4：添加变量（可选）**
|
||||
在 Template 中使用 QuickAdd 变量：
|
||||
```markdown
|
||||
# {{DATE:YYYY年MM月DD日 dddd}}
|
||||
|
||||
## 📋 今日任务
|
||||
- [ ] {{VALUE:今天的主要任务?}}
|
||||
```
|
||||
|
||||
**步骤 5：设置快捷键**
|
||||
- 在设置中找到 "Daily Note" choice
|
||||
- 设置快捷键（例如：`Ctrl+Shift+D`）
|
||||
|
||||
#### 使用 QuickAdd 创建日记
|
||||
|
||||
配置完成后，按快捷键 `Ctrl+Shift+D` 即可：
|
||||
- ✅ 自动创建日记
|
||||
- ✅ 自动命名（带日期）
|
||||
- ✅ 自动保存到指定文件夹
|
||||
- ✅ 应用模板
|
||||
- ✅ 可选择输入变量值
|
||||
|
||||
---
|
||||
|
||||
## 🤖 方式三：Claude Code 智能命令
|
||||
|
||||
### /daily-review 命令
|
||||
|
||||
**功能**：每日结束时的智能回顾，自动分析当天活动
|
||||
|
||||
**使用方法**：
|
||||
```bash
|
||||
# 在 Claude Code 中
|
||||
/daily-review
|
||||
```
|
||||
|
||||
**命令会自动**：
|
||||
1. 🔍 查找今天修改/创建的所有笔记
|
||||
2. 📊 分析项目进度
|
||||
3. 💡 提取关键见解
|
||||
4. 🔗 发现笔记之间的连接
|
||||
5. 📝 生成每日总结
|
||||
6. 🎯 设定明天的优先级
|
||||
|
||||
**输出格式**（更新到每日笔记）：
|
||||
```markdown
|
||||
## Accomplished
|
||||
- ✓ [Completed item 1]
|
||||
- ✓ [Completed item 2]
|
||||
|
||||
## Progress Made
|
||||
- [Project]: [What moved forward]
|
||||
|
||||
## Insights
|
||||
- [Key realization]
|
||||
|
||||
## Discovered Questions
|
||||
- [New question]
|
||||
|
||||
## Tomorrow's Focus
|
||||
1. [Priority 1]
|
||||
2. [Priority 2]
|
||||
3. [Priority 3]
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 🔄 工作流推荐
|
||||
|
||||
### 每日例行流程
|
||||
|
||||
#### ☀️ 早晨（启动工作）
|
||||
|
||||
**命令行工作流**：
|
||||
```bash
|
||||
# 1. 同步代码
|
||||
git pull
|
||||
|
||||
# 2. 创建今日日记
|
||||
pnpm daily-note "今日工作"
|
||||
|
||||
# 3. 在编辑器中打开文件
|
||||
# 添加今日计划和任务
|
||||
```
|
||||
|
||||
**Obsidian 工作流**：
|
||||
```bash
|
||||
# 1. 打开 Obsidian
|
||||
# 2. 按 Ctrl+Shift+D（QuickAdd）
|
||||
# 3. 输入今日主题
|
||||
# 4. 开始记录
|
||||
```
|
||||
|
||||
#### 🌞 白天（工作过程）
|
||||
|
||||
**快速捕获**：
|
||||
- 命令行：`pnpm daily-note "快速想法"`
|
||||
- Obsidian：`00_Inbox/` 中创建临时笔记
|
||||
- Claude Code：`/thinking-partner` 记录对话
|
||||
|
||||
**关联笔记**：
|
||||
- 使用 `[[链接]]` 引用相关项目、资源
|
||||
- 标记重要发现到每日笔记
|
||||
|
||||
#### 🌙 晚上（结束工作）
|
||||
|
||||
**Claude Code 回顾**：
|
||||
```bash
|
||||
# 1. 运行每日回顾
|
||||
/daily-review
|
||||
|
||||
# 2. 审查生成的总结
|
||||
# 3. 补充遗漏的内容
|
||||
|
||||
# 4. 提交到 Git
|
||||
git add .
|
||||
git commit -m "daily: $(date +%Y-%m-%d)"
|
||||
git push
|
||||
```
|
||||
|
||||
**Obsidian 整理**：
|
||||
1. 检查 `00_Inbox/` 内容
|
||||
2. 移动笔记到正确的 PARA 位置
|
||||
3. 更新项目状态
|
||||
4. 链接相关笔记
|
||||
|
||||
---
|
||||
|
||||
## 📊 对比三种方式
|
||||
|
||||
| 特性 | 命令行 | Obsidian Templater | QuickAdd |
|
||||
|------|--------|-------------------|----------|
|
||||
| **速度** | ⚡ 最快 | 🚀 快 | ⚡ 快（配置后） |
|
||||
| **配置** | ✅ 无需配置 | ✅ 预配置 | ⚠️ 需手动配置 |
|
||||
| **灵活性** | ⚠️ 基础 | 🚀 高 | 🌟 极高 |
|
||||
| **自动化** | ⚠️ 有限 | 🚀 自动应用 | 🌟 高度自动化 |
|
||||
| **图形界面** | ❌ 无 | ✅ 有 | ✅ 有 |
|
||||
| **变量支持** | ❌ 无 | ✅ Templater 语法 | ✅ QuickAdd 语法 |
|
||||
| **适用场景** | 命令行爱好者 | Obsidian 用户 | 高级用户 |
|
||||
|
||||
---
|
||||
|
||||
## 🎯 推荐组合
|
||||
|
||||
### 初学者
|
||||
- **主要方式**：Obsidian Templater（自动模板）
|
||||
- **辅助方式**：命令行 `pnpm daily-note`
|
||||
|
||||
### 进阶用户
|
||||
- **主要方式**：QuickAdd（快捷键 `Ctrl+Shift+D`）
|
||||
- **辅助方式**：Claude Code `/daily-review`
|
||||
|
||||
### 高级用户
|
||||
- **早晨**：QuickAdd 创建日记
|
||||
- **白天**：命令行快速捕获
|
||||
- **晚上**：Claude Code 智能回顾
|
||||
- **整理**：Obsidian 图形界面链接
|
||||
|
||||
---
|
||||
|
||||
## 💡 技巧与最佳实践
|
||||
|
||||
### 1. 命名规范
|
||||
|
||||
**推荐格式**：
|
||||
```
|
||||
YYYY-MM-DD # 纯日期，普通日记
|
||||
YYYY-MM-DD - [主题] # 带主题，特定活动
|
||||
Meeting - [主题] - [日期] # 会议记录
|
||||
Idea - [简短描述] # 想法记录
|
||||
```
|
||||
|
||||
### 2. 模板自定义
|
||||
|
||||
**在 `06_Metadata/Templates/` 中创建自定义模板**：
|
||||
|
||||
```markdown
|
||||
# {{date:YYYY-MM-DD}}
|
||||
|
||||
## 🎯 今日目标
|
||||
- [ ]
|
||||
|
||||
## 📈 进度跟踪
|
||||
|
||||
## 🔍 问题与挑战
|
||||
|
||||
## 💡 学到的东西
|
||||
|
||||
## 📝 待跟进
|
||||
```
|
||||
|
||||
### 3. 日期链接
|
||||
|
||||
**中文模板支持前一天/后一天链接**：
|
||||
```markdown
|
||||
---
|
||||
← [[2026-01-05]] | [[2026-01-07]] →
|
||||
---
|
||||
```
|
||||
|
||||
在 Obsidian 中点击日期即可跳转
|
||||
|
||||
### 4. Git 提交钩子（可选）
|
||||
|
||||
**自动化每日提交**（在 `.git/hooks/post-commit`）：
|
||||
```bash
|
||||
#!/bin/bash
|
||||
# 自动提交到远程
|
||||
git push
|
||||
```
|
||||
|
||||
### 5. 每日提醒
|
||||
|
||||
**使用 Obsidian Calendar 插件**：
|
||||
- 安装 Calendar 插件（已安装）
|
||||
- 设置每日提醒创建日记
|
||||
- 可视化查看日记历史
|
||||
|
||||
---
|
||||
|
||||
## 🔧 故障排除
|
||||
|
||||
### 命令行方式失败
|
||||
|
||||
**问题**：`pnpm daily-note` 报错
|
||||
```
|
||||
'pnpm' is not recognized
|
||||
```
|
||||
|
||||
**解决**：
|
||||
```bash
|
||||
# 安装 pnpm
|
||||
npm install -g pnpm
|
||||
|
||||
# 或使用 npm
|
||||
npm run daily-note
|
||||
```
|
||||
|
||||
### Templater 模板不应用
|
||||
|
||||
**问题**：在 `00_Inbox/` 创建文件，模板未自动填充
|
||||
|
||||
**检查**：
|
||||
1. Templater 插件是否启用
|
||||
2. `trigger_on_file_creation` 是否为 `true`
|
||||
3. 文件夹模板配置是否正确
|
||||
4. 模板文件是否存在
|
||||
|
||||
### QuickAdd 无响应
|
||||
|
||||
**问题**：按快捷键没有反应
|
||||
|
||||
**解决**：
|
||||
1. 检查快捷键是否被其他插件占用
|
||||
2. 重新加载 Obsidian（禁用后启用 QuickAdd）
|
||||
3. 查看 Console 日志（`Ctrl+Shift+I`）
|
||||
|
||||
---
|
||||
|
||||
## 📚 相关文档
|
||||
|
||||
- [[QUICK_REFERENCE]] - 快速参考卡片
|
||||
- [[WEEKLY_REVIEW]] - 每周回顾流程
|
||||
- [[AGENTS]] - Claude Code 命令说明
|
||||
- [[README]] - 项目完整文档
|
||||
|
||||
---
|
||||
|
||||
## 🆘 需要帮助？
|
||||
|
||||
**获取即时帮助**：
|
||||
```bash
|
||||
# 在 Claude Code 中询问
|
||||
"如何自定义每日日记模板？"
|
||||
"如何设置 QuickAdd 自动创建日记？"
|
||||
"如何将日记链接到项目？"
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
**最后更新**：2026-01-06
|
||||
**作者**：Claude Code Assistant
|
||||
**版本**：1.0
|
||||
@@ -0,0 +1,29 @@
|
||||
---
|
||||
title: Dataview Validation 2026-02-25
|
||||
date: 2026-02-25
|
||||
type: validation-log
|
||||
status: done
|
||||
source: 06_Metadata/REVIEW_REPORT_2026-02-25.md
|
||||
---
|
||||
|
||||
# Dataview 修复验收
|
||||
|
||||
## 修复项
|
||||
|
||||
- 将 7 个 Area Hub 中 `from "200-area/..."` 全部修正为 `from "02_Areas/..."`。
|
||||
|
||||
## 验收结果（修复前/后）
|
||||
|
||||
- 修复前：7/7 Hub 查询为空（报告确认）。
|
||||
- 修复后：
|
||||
- `02_Areas/Finance`：3 条
|
||||
- `02_Areas/Blog`：6 条
|
||||
- `02_Areas/Health`：2 条
|
||||
- `02_Areas/House`：4 条
|
||||
- `02_Areas/Personal Development`：7 条
|
||||
- `02_Areas/Network & VPN`：1 条
|
||||
- `02_Areas/Productivity`：4 条
|
||||
|
||||
## 结论
|
||||
|
||||
Dataview 路径失效问题已恢复，查询可覆盖 Area 子目录并返回非空结果。
|
||||
@@ -0,0 +1,66 @@
|
||||
---
|
||||
created: 2026-04-11
|
||||
modified: 2026-04-11
|
||||
type: inbox-triage
|
||||
tags:
|
||||
- inbox
|
||||
- triage
|
||||
- hermes
|
||||
status: review
|
||||
---
|
||||
|
||||
# Inbox Triage - 2026-04-11
|
||||
|
||||
## Scope
|
||||
|
||||
- Folder reviewed: `00_Inbox/`
|
||||
- Notes reviewed: 8
|
||||
- Goal: identify low-risk cleanup and next moves without bulk reorganization
|
||||
|
||||
## Findings
|
||||
|
||||
### Keep in inbox for short-term follow-up
|
||||
|
||||
- [[00_Inbox/2026-01-07]]: useful daily capture with concrete follow-up actions across AI, Obsidian, GFW, and memory tooling
|
||||
- [[00_Inbox/2026-01-17]]: lightweight daily capture; likely should be moved or split after reviewing whether the Apple ID details are still needed
|
||||
|
||||
### Move to projects
|
||||
|
||||
- [[00_Inbox/IMPROVEMENT_PLAN_2026-02-03]] -> `01_Projects/AI-Development/Obsidian Agent/`
|
||||
- Reason: this is not inbox capture anymore; it is a structured implementation plan tied to vault/documentation improvement work
|
||||
|
||||
### Move to resources
|
||||
|
||||
- [[00_Inbox/Untitled]] -> likely `03_Resources/Development/AI-ML/` or `03_Resources/Community/`
|
||||
- Reason: after removing secrets, the remaining value is command/reference material for GitHub Copilot and Matrix APIs
|
||||
- [[Windows Shell 获取文件名和大小]] -> `03_Resources/Development/` or `03_Resources/Productivity/`
|
||||
- Reason: contains a reusable PowerShell snippet rather than a transient capture
|
||||
|
||||
### Archive candidates
|
||||
|
||||
- [[00_Inbox/Welcome]] -> `04_Archive/Inbox-Clippings/`
|
||||
- Reason: onboarding note, no longer active, already fulfilled its purpose
|
||||
|
||||
### Operational / special-case notes
|
||||
|
||||
- [[00_Inbox/CLAUDE]]: likely auto-generated context from tooling, not normal inbox content
|
||||
- Recommendation: leave in place unless you want to relocate agent-generated memory artifacts systematically
|
||||
|
||||
## Risks
|
||||
|
||||
- `Untitled.md` contained plaintext credentials/tokens before redaction
|
||||
- Any credentials previously stored there should be considered compromised and rotated
|
||||
- Broad renames or moves may break your existing mental model or links, so they were not applied automatically in this pass
|
||||
|
||||
## Recommended Next Actions
|
||||
|
||||
- [ ] Rotate any credentials previously stored in `00_Inbox/Untitled.md`
|
||||
- [ ] Rename `Untitled.md` to a descriptive title after deciding its permanent destination
|
||||
- [ ] Rename `未命名.md` after deciding whether it belongs under Development or Productivity resources
|
||||
- [ ] Move `IMPROVEMENT_PLAN_2026-02-03.md` into the active Obsidian Agent project area
|
||||
- [ ] Archive `Welcome.md`
|
||||
|
||||
## Minimal Safe Changes Applied
|
||||
|
||||
- Redacted plaintext secrets from [[00_Inbox/Untitled]]
|
||||
- Added metadata and follow-up guidance to that note
|
||||
File diff suppressed because it is too large
Load Diff
@@ -0,0 +1,106 @@
|
||||
# Obsidian 仓库评审报告（QMD 驱动）
|
||||
|
||||
**评审日期**: 2026-02-03
|
||||
**评审范围**: 结构、文档、工作流、模板、脚本、维护一致性
|
||||
**评审方法**: 使用 QMD 索引与检索，对核心说明文档与工作流进行抽样评审
|
||||
**索引概况**: 639 个 Markdown 文档（QMD index）
|
||||
|
||||
---
|
||||
|
||||
## 总体评分
|
||||
|
||||
**综合得分: 86 / 100（成熟度：可持续运作，局部一致性需收敛）**
|
||||
|
||||
### 评分维度
|
||||
|
||||
1. 信息架构与 PARA 落地（18/20）
|
||||
2. 文档清晰度与可执行性（16/20）
|
||||
3. 工作流设计与可持续性（16/20）
|
||||
4. 模板与元数据规范（14/15）
|
||||
5. 自动化与脚本可用性（11/15）
|
||||
6. 一致性与去重（11/15）
|
||||
|
||||
**加权说明**: 结构与可执行性优先，其次是自动化与一致性。
|
||||
|
||||
---
|
||||
|
||||
## 主要优点
|
||||
|
||||
1. **结构清晰且 PARA 有完整说明**
|
||||
README 对 PARA 与文件结构的解释完整，且与 `06_Metadata/WORKFLOWS.md` 形成“总览 + 细节”分层。
|
||||
核心目录（`00_Inbox` ~ `06_Metadata`）清晰，迁移与归档路径明确。
|
||||
|
||||
2. **工作流体系成熟，具备“简化版 + 过渡版 + 全量版”**
|
||||
`ULTRA_SIMPLE_WORKFLOW.md`、`WORKFLOW_TRANSITION_GUIDE.md`、`WEEKLY_REVIEW.md`形成明确层级，能覆盖不同熟练度与时间预算。
|
||||
|
||||
3. **元数据与模板库基础扎实**
|
||||
`06_Metadata/Templates` 与 `06_Metadata/WORKFLOWS.md` 给出通用 frontmatter 与模板结构，便于系统化扩展。
|
||||
|
||||
4. **附件管理有明确规则与脚本支持**
|
||||
`05_Attachments/README.md`与脚本（package.json scripts）形成闭环，降低手工成本。
|
||||
|
||||
---
|
||||
|
||||
## 关键问题与风险
|
||||
|
||||
1. **核心文档入口不一致**
|
||||
`README.md`、`QUICK_REFERENCE.md`、`06_Metadata/WORKFLOWS.md`对“入口/主线”的定义不一致，入口职责与跳转路径不明确。
|
||||
结果：新用户或助手会遇到“入口不清晰”的路径断裂。
|
||||
**证据**: `README.md` 仅提供概览与分散说明，未明确权威入口；`QUICK_REFERENCE.md` 以速查为主但缺少返回入口说明；`06_Metadata/WORKFLOWS.md` 作为详细参考但未说明与入口文档的关系。
|
||||
|
||||
2. **命令规范与示例存在冲突**
|
||||
文档示例中出现 `| wc -l`、`grep`、`find` 等复杂命令，但缺少“脚本允许、手动命令禁止”的清晰边界说明。
|
||||
结果：指导规则与示例出现冲突，影响一致性与可执行性。
|
||||
**证据**: `WEEKLY_REVIEW.md` 中 `ls 00_Inbox/ | wc -l`；`QUICK_REFERENCE.md` 中 `grep -r` 与 `find . -name`。
|
||||
|
||||
3. **文档层级存在“并行主线”**
|
||||
`README.md`、`QUICK_REFERENCE.md`、`06_Metadata/WORKFLOWS.md`均包含“顶层规范”，缺少明确的主线导航与分工说明。
|
||||
结果：对于“哪个是主入口”的认知不稳定，容易造成重复维护。
|
||||
**证据**: `README.md` 提供概览与流程，但未明确入口职责；`QUICK_REFERENCE.md` 自包含速查流程；`06_Metadata/WORKFLOWS.md` 标注“详细参考”但未说明与其他入口的关系。
|
||||
|
||||
4. **工具链命令调用不统一（pnpm vs npm）**
|
||||
README 仍出现 `npm run` 的写法，而 Quick Reference/WORKFLOWS 使用 `pnpm`。
|
||||
结果：新用户可能复制即失败，或以为存在两套脚本策略。
|
||||
**证据**: `README.md` 中 `npm run firecrawl:scrape` 与 `npm run firecrawl:batch`；`06_Metadata/WORKFLOWS.md` 中脚本示例为 `pnpm`。
|
||||
|
||||
---
|
||||
|
||||
## 建议（按优先级）
|
||||
|
||||
1. **补齐或明确 `CLAUDE.md` 的权威入口**
|
||||
选项 A：恢复并维护 `CLAUDE.md` 为唯一入口（推荐）
|
||||
选项 B：将 `CLAUDE-BOOTSTRAP.md` 重命名为 `CLAUDE.md`，并在 README/Quick Reference 全部指向该文件
|
||||
|
||||
2. **统一“命令规范”与脚本现实**
|
||||
如果希望禁用管道命令：
|
||||
- 将 `WEEKLY_REVIEW.md` 与脚本中管道命令替换为等价的简单命令
|
||||
如果仅限制“手动执行”而非脚本：
|
||||
- 在 `CLAUDE-BOOTSTRAP.md`中明确例外（脚本允许管道，交互指令禁止）
|
||||
|
||||
3. **统一工具调用方式**
|
||||
全部文档中统一为 `pnpm`，或新增一段“若未安装 pnpm 可用 npm run”的注释。
|
||||
|
||||
4. **建立“文档主线”导航**
|
||||
在 README 或 Quick Reference 中增加“权威文档入口”段落，并明确：
|
||||
- `CLAUDE.md` = 系统主入口
|
||||
- `QUICK_REFERENCE.md` = 速查
|
||||
- `WORKFLOWS.md` = 详细参考
|
||||
|
||||
---
|
||||
|
||||
## 结论
|
||||
|
||||
该仓库已经具备**成熟的知识管理与工作流体系**，文档覆盖广、结构清晰、脚本化良好。
|
||||
当前主要瓶颈是**入口一致性与规则冲突**，解决后可显著提升上手体验与可维护性。
|
||||
**评审日期与索引日期**: 本报告评审日期为 2026-02-03，索引统计日期与之保持一致。
|
||||
|
||||
---
|
||||
|
||||
## 评分依据（复核用）
|
||||
|
||||
- 结构与文档一致性是否可在 2-3 次跳转内定位主流程
|
||||
- 命令示例与规则是否一致、是否存在可执行冲突
|
||||
- 入口文档是否明确分工且互相可达
|
||||
- 关键流程是否有可追溯证据（文件路径 + 具体示例）
|
||||
|
||||
**建议：**优先完成“入口文档一致性”与“命令规则一致性”两件事，可将综合评分提升至 90+。
|
||||
@@ -0,0 +1,183 @@
|
||||
---
|
||||
title: Vault 专业审查报告
|
||||
date: 2026-02-25
|
||||
tags:
|
||||
- meta
|
||||
- review
|
||||
- vault-health
|
||||
type: review-report
|
||||
status: active
|
||||
---
|
||||
|
||||
# Vault 专业审查报告
|
||||
|
||||
**审查日期**：2026-02-25
|
||||
**审查方法**：文件结构全量扫描 + frontmatter 统计 + 内容抽样
|
||||
**索引概况（已校准）**：
|
||||
- 全仓 Markdown：590
|
||||
- 核心区（00_~06_）：541
|
||||
- 知识区（00_~05_）：518
|
||||
|
||||
---
|
||||
|
||||
## 总体评分
|
||||
|
||||
> [!success] 综合得分：80 / 100
|
||||
> PARA 框架落地良好，主要短板是 Dataview 失效、Inbox 积压、明文凭据风险和部分结构缺口。
|
||||
|
||||
| 维度 | 得分 |
|
||||
|------|------|
|
||||
| 信息架构与 PARA 落地 | 16/20 |
|
||||
| frontmatter 与元数据规范 | 12/15 |
|
||||
| 知识网络（双链密度） | 7/15 |
|
||||
| Inbox 处理与工作流可持续性 | 11/20 |
|
||||
| 安全与一致性 | 8/15 |
|
||||
| 插件生态 | 14/15 |
|
||||
|
||||
---
|
||||
|
||||
## 主要优点
|
||||
|
||||
1. **PARA 结构清晰**：`00_Inbox → 01_Projects → 02_Areas → 03_Resources → 04_Archive` 边界明确，迁移路径可预期。
|
||||
2. **Hub 文件模式良好**：`Finance.md`、`Blog.md` 等 Area Hub 使用 frontmatter + Dataview 查询的设计思路正确。
|
||||
3. **frontmatter 覆盖率中等**：核心区 541 篇中 280 篇（51.8%）有 frontmatter。
|
||||
4. **插件选择合理**：22 个已启用插件覆盖捕获（QuickAdd）、查询（Dataview）、可视化（Excalidraw、Kanban）等关键场景。
|
||||
|
||||
---
|
||||
|
||||
## 关键问题与风险
|
||||
|
||||
### 🔴 P0：安全隐患（需立即处理）
|
||||
|
||||
在多类技术笔记中发现**明文凭据/令牌模式**，且仓库已纳入 git 历史，存在系统性泄露风险：
|
||||
|
||||
> [!danger] 高风险文件示例（不限于此）
|
||||
> - **AI/ML 配置**：`03_Resources/Development/AI-ML/` 下 `Azure-config.md`、`Nvidia-config.md`
|
||||
> - **基础设施**：`01_Projects/Infrastructure/Services/` 下的 `Matrix-windy-pc.md`, `Dendrite.md`, `Matrix.md` (数据库密码、AccessToken、Shared Secret)
|
||||
> - **开发工具**：`03_Resources/Development/DevOps/Gitlab/rest api.md` (Private Token)
|
||||
> - **IoT**：`01_Projects/Home-Automation/esphome.md` (API Encryption Key)
|
||||
|
||||
**建议**：立即执行全库正则扫描（使用 `password|secret|key|token`），将凭据迁移至加密管理器，并在 git 中使用 BFG 或 filter-repo 清除历史记录。
|
||||
|
||||
---
|
||||
|
||||
### 🔴 P0：Dataview 查询路径全部失效
|
||||
|
||||
Area Hub 中存在 7 处旧路径 `200-area/...`，当前查询均返回空结果：
|
||||
|
||||
| 文件 | 错误路径 | 正确路径 |
|
||||
|------|----------|----------|
|
||||
| `02_Areas/Finance/Finance.md` | `"200-area/Finance"` | `"02_Areas/Finance"` |
|
||||
| `02_Areas/Blog/Blog.md` | `"200-area/Blog"` | `"02_Areas/Blog"` |
|
||||
| `02_Areas/Health/Health.md` | `"200-area/Health"` | `"02_Areas/Health"` |
|
||||
| `02_Areas/House/House.md` | `"200-area/House"` | `"02_Areas/House"` |
|
||||
| `02_Areas/Personal Development/Personal Development.md` | `"200-area/Personal Development"` | `"02_Areas/Personal Development"` |
|
||||
| `02_Areas/Network & VPN/Network & VPN.md` | `"200-area/Network & VPN"` | `"02_Areas/Network & VPN"` |
|
||||
| `02_Areas/Productivity/Productivity.md` | `"200-area/Productivity"` | `"02_Areas/Productivity"` |
|
||||
|
||||
---
|
||||
|
||||
### 🟠 P1：Inbox 积压严重
|
||||
|
||||
```
|
||||
00_Inbox/Clippings/2023/ 73 篇（积压 2-3 年）
|
||||
00_Inbox/Clippings/2024/ 127 篇（积压 1-2 年）
|
||||
00_Inbox/Clippings/2025/ 5 篇
|
||||
00_Inbox/Clippings/2026/ 11 篇
|
||||
```
|
||||
|
||||
> [!warning] Inbox 不是归档库
|
||||
> Capture 流程在正常运转，但 Process（处理→归档/删除）流程已断裂。216 篇未处理的 Clipping 正在消耗认知资源，同时使真正的 Inbox 条目淹没其中。
|
||||
|
||||
**建议**：对 2023-2024 年的 Clippings 执行批量决策——超过 90 天未处理即视为过期，直接移入 `04_Archive` 或删除。
|
||||
|
||||
---
|
||||
|
||||
### 🟠 P1：知识网络极度稀疏
|
||||
|
||||
| 指标 | 数值 |
|
||||
|------|------|
|
||||
| 总笔记数（核心区） | 541 篇 |
|
||||
| `[[wikilink]]` 总数 | 292 处 |
|
||||
| 平均每篇链接数 | **0.54 个** |
|
||||
|
||||
> [!note] 图谱基本是孤岛
|
||||
> Obsidian 的核心价值在于发现意料之外的知识连接。当前密度意味着图谱几乎是孤立节点的集合，Obsidian 相对普通文件夹的优势未能体现。
|
||||
>
|
||||
> 根本原因：大量笔记是技术配置的直接转储，缺少"阅读→思考→链接"的处理步骤。
|
||||
|
||||
---
|
||||
|
||||
### 🟡 P2：Vault 根目录污染
|
||||
|
||||
当前 vault 是“知识库 + 自动化脚本”混合仓库，根目录包含较多工程文件。对纯笔记视角属于噪音，对开发工作流则是必要资产。
|
||||
|
||||
**工程文件**（如仅用于 Obsidian，可考虑外移；如持续使用脚本则应保留）
|
||||
- `node_modules/`、`package.json`、`package-lock.json`、`pnpm-lock.yaml`
|
||||
|
||||
**元文档**（可按偏好统一归入 `06_Metadata/`）
|
||||
- `ULTRA_SIMPLE_WORKFLOW.md`
|
||||
- `WORKFLOW_TRANSITION_GUIDE.md`
|
||||
- `WORKFLOW_SIMPLIFICATION_ANALYSIS.md`
|
||||
- `WEEKLY_REVIEW.md`
|
||||
- `QUICK_REFERENCE.md`
|
||||
- `CHANGELOG.md`
|
||||
- `REFACTOR_SUMMARY.md`
|
||||
- `AGENTS.md`、`CONTRIBUTING.md`、`CLAUDE-BOOTSTRAP.md`
|
||||
|
||||
**孤立文件**：`2026-01-05.md`（位于根目录，未归入任何目录）
|
||||
|
||||
---
|
||||
|
||||
### 🟡 P2：内容重复与目录混乱
|
||||
|
||||
**重复内容**
|
||||
- `02_Areas/Lifestyle/Cooking/Pickled-Cucumber-Recipe.md` 与 `03_Resources/Cooking/Pickled-Cucumber-Recipe.md` 内容高度重复（前者多 frontmatter）
|
||||
- `03_Resources/Cooking/` 内部冗余：`Pickled-Cucumber.md` (说明) 与 `Pickled-Cucumber-Recipe.md` (记录) 建议合并
|
||||
- `02_Areas/Lifestyle/Cooking`、`02_Areas/Lifestyle/Gaming` 应为 Resources，不是 Areas（Areas = 持续的责任领域，菜谱是资源）
|
||||
|
||||
**重复目录**
|
||||
- `03_Resources/PKM/` 与 `03_Resources/Personal Knowledge Management/` — 同一概念两个入口
|
||||
|
||||
---
|
||||
|
||||
### 🟡 P2：插件使用与安装不匹配
|
||||
|
||||
- `dataview` 已安装，但 Hub 文件查询全部失效（见 P0）
|
||||
- `obsidian-tasks-plugin` 已安装，任务语法存在（约 105 行），但与插件能力相比使用深度有限
|
||||
- `calendar` 已安装，但日期笔记只有零散几篇，没有形成每日笔记习惯
|
||||
- `templater-obsidian` 与 `quickadd` 功能重叠，建议选一个作为主力
|
||||
- 已启用插件 22 个，但启用列表中有 2 个插件目录缺失：`obsidian-opencode`、`opencode-obsidian`
|
||||
|
||||
**缺失**：建议安装 `linter` 插件自动规范 frontmatter 格式，减少人工维护成本。
|
||||
|
||||
---
|
||||
|
||||
### 🟡 P2：结构缺口（新增）
|
||||
|
||||
- `02_Areas/GFW` 缺少同名 Hub 文件
|
||||
- `02_Areas/Job` 缺少同名 Hub 文件
|
||||
- `02_Areas/Lifestyle` 缺少同名 Hub 文件
|
||||
|
||||
---
|
||||
|
||||
## 行动清单
|
||||
|
||||
- [ ] 🔴 **全库凭据清理**：使用正则全量搜索并清除 `01_Projects` 和 `03_Resources` 中的明文密钥
|
||||
- [ ] 🔴 批量修复所有 Area Hub 的 Dataview 查询路径（需包含子目录层级）
|
||||
- [ ] 🟠 将根目录的元文档批量移入 `06_Metadata/`
|
||||
- [ ] 🟠 合并 `03_Resources/PKM` 与 `03_Resources/Personal Knowledge Management`
|
||||
- [ ] 🟠 合并 `03_Resources/Cooking/` 下的冗余笔记，并从 `02_Areas` 迁移内容
|
||||
- [ ] 🟡 对 2023-2024 年的 Inbox Clippings 执行批量归档/删除决策
|
||||
- [ ] 🟡 补齐 `02_Areas/GFW`、`02_Areas/Job`、`02_Areas/Lifestyle` 的 Hub 文件
|
||||
- [ ] 🟡 修复或移除已启用但缺失目录的插件配置（`obsidian-opencode`、`opencode-obsidian`）
|
||||
- [ ] 🟡 建立每周 Inbox 清零的处理习惯（建议固定时间，30 分钟内完成）
|
||||
- [ ] 🟢 为 Projects 和 Areas 笔记补充双向链接，逐步建立知识网络
|
||||
|
||||
---
|
||||
|
||||
## 参考（已校准）
|
||||
|
||||
- [[00_Inbox/IMPROVEMENT_PLAN_2026-02-03]] — 上次改进计划
|
||||
- [[06_Metadata/IMPROVEMENT_PLAN_2026-02-25]] — 本次修复计划（含执行阶段与计划审核）
|
||||
- [[REVIEW_REPORT_2026-02-03]] — 上次审查报告（评分 86/100）
|
||||
@@ -0,0 +1,250 @@
|
||||
---
|
||||
title: Templater 使用指南
|
||||
created: 2026-01-05
|
||||
updated: 2026-01-05
|
||||
tags:
|
||||
- obsidian
|
||||
- templater
|
||||
- guide
|
||||
- reference
|
||||
type: reference
|
||||
---
|
||||
|
||||
# Templater 使用指南
|
||||
|
||||
## 什么是 Templater？
|
||||
|
||||
Templater 是 Obsidian 最强大的模板插件，它允许你创建动态模板，使用变量、函数和命令来自动化你的笔记创建流程。
|
||||
|
||||
## 核心功能
|
||||
|
||||
### 1. 基本语法
|
||||
|
||||
Templater 使用 `<% %>` 标签来执行代码：
|
||||
|
||||
- `<% code %>` - 执行代码但不输出
|
||||
- `<%= value %>` - 执行代码并输出结果
|
||||
- `<%* async code %>` - 执行异步代码
|
||||
|
||||
### 2. 内置变量
|
||||
|
||||
#### 日期和时间
|
||||
```
|
||||
<% tp.date.now("YYYY-MM-DD") %> # 当前日期：2026-01-05
|
||||
<% tp.date.now("HH:mm") %> # 当前时间：14:30
|
||||
<% tp.date.now("YYYY-MM-DD HH:mm:ss") %> # 完整时间戳
|
||||
<% tp.date.tomorrow("YYYY-MM-DD") %> # 明天的日期
|
||||
<% tp.date.yesterday("YYYY-MM-DD") %> # 昨天的日期
|
||||
<% tp.date.weekday("YYYY-MM-DD", 0) %> # 本周日（0=周日）
|
||||
```
|
||||
|
||||
#### 文件信息
|
||||
```
|
||||
<% tp.file.title %> # 当前文件标题（不含扩展名）
|
||||
<% tp.file.creation_date() %> # 文件创建日期
|
||||
<% tp.file.folder() %> # 文件所在文件夹
|
||||
<% tp.file.path() %> # 文件完整路径
|
||||
```
|
||||
|
||||
#### 配置信息
|
||||
```
|
||||
<% tp.config.active_file.basename %> # 活动文件名
|
||||
<% tp.config.active_file.path %> # 活动文件路径
|
||||
```
|
||||
|
||||
### 3. 常用命令
|
||||
|
||||
#### 文件操作
|
||||
```javascript
|
||||
// 创建新笔记
|
||||
<%* await tp.file.create_new("模板名", "新文件名", false, "目标文件夹") %>
|
||||
|
||||
// 移动文件
|
||||
<%* await tp.file.move("新路径/新文件名") %>
|
||||
|
||||
// 重命名文件
|
||||
<%* await tp.file.rename("新文件名") %>
|
||||
|
||||
// 包含其他文件
|
||||
<% tp.file.include("[[其他笔记名称]]") %>
|
||||
```
|
||||
|
||||
#### 用户输入
|
||||
```javascript
|
||||
// 提示用户输入
|
||||
<% tp.system.prompt("请输入项目名称") %>
|
||||
|
||||
// 建议列表（下拉选择）
|
||||
<% tp.system.suggester(["选项1", "选项2", "选项3"], ["value1", "value2", "value3"]) %>
|
||||
```
|
||||
|
||||
### 4. 实用示例
|
||||
|
||||
#### 示例1：每日笔记模板
|
||||
```markdown
|
||||
---
|
||||
date: <% tp.date.now("YYYY-MM-DD") %>
|
||||
day: <% tp.date.now("dddd") %>
|
||||
week: <% tp.date.now("YYYY-[W]WW") %>
|
||||
---
|
||||
|
||||
# <% tp.date.now("YYYY-MM-DD dddd") %>
|
||||
|
||||
## 📋 今日任务
|
||||
- [ ]
|
||||
|
||||
## 📝 笔记
|
||||
|
||||
## 🎯 重点事项
|
||||
|
||||
## 💡 想法与灵感
|
||||
|
||||
---
|
||||
← [[<% tp.date.yesterday("YYYY-MM-DD") %>]] | [[<% tp.date.tomorrow("YYYY-MM-DD") %>]] →
|
||||
```
|
||||
|
||||
#### 示例2：项目笔记模板
|
||||
```markdown
|
||||
---
|
||||
type: project
|
||||
created: <% tp.date.now("YYYY-MM-DD") %>
|
||||
status: active
|
||||
---
|
||||
|
||||
# <% tp.system.prompt("项目名称") %>
|
||||
|
||||
## 📋 项目概述
|
||||
<% tp.system.prompt("项目简介") %>
|
||||
|
||||
## 🎯 目标
|
||||
-
|
||||
|
||||
## 📅 关键时间节点
|
||||
- 开始时间：<% tp.date.now("YYYY-MM-DD") %>
|
||||
- 截止时间：
|
||||
|
||||
## 👥 相关人员
|
||||
-
|
||||
|
||||
## 📎 相关资源
|
||||
-
|
||||
|
||||
## 📝 进展记录
|
||||
|
||||
### <% tp.date.now("YYYY-MM-DD") %>
|
||||
-
|
||||
```
|
||||
|
||||
#### 示例3：会议记录模板
|
||||
```markdown
|
||||
---
|
||||
type: meeting
|
||||
date: <% tp.date.now("YYYY-MM-DD HH:mm") %>
|
||||
participants:
|
||||
---
|
||||
|
||||
# 会议记录 - <% tp.system.prompt("会议主题") %>
|
||||
|
||||
**时间**：<% tp.date.now("YYYY-MM-DD HH:mm") %>
|
||||
**地点**：<% tp.system.prompt("会议地点") %>
|
||||
**参与者**：
|
||||
|
||||
## 📋 议程
|
||||
1.
|
||||
|
||||
## 📝 讨论内容
|
||||
|
||||
## ✅ 行动项
|
||||
- [ ]
|
||||
|
||||
## 🔗 相关资料
|
||||
```
|
||||
|
||||
## 如何使用
|
||||
|
||||
### 方法1：快捷键触发
|
||||
1. 打开设置 → 快捷键
|
||||
2. 搜索 "Templater: Insert Template"
|
||||
3. 设置一个快捷键（如 `Ctrl/Cmd + T`）
|
||||
4. 在笔记中按快捷键选择模板
|
||||
|
||||
### 方法2：命令面板
|
||||
1. 按 `Ctrl/Cmd + P` 打开命令面板
|
||||
2. 输入 "Templater"
|
||||
3. 选择 "Templater: Insert Template"
|
||||
4. 选择要插入的模板
|
||||
|
||||
### 方法3：创建新笔记时自动应用
|
||||
1. 在设置中配置 "Folder Templates"
|
||||
2. 为不同文件夹指定默认模板
|
||||
3. 在该文件夹创建新笔记时自动应用模板
|
||||
|
||||
## 配置建议
|
||||
|
||||
### 1. 创建模板文件夹
|
||||
建议在 `06_Metadata/Templates` 下创建所有模板文件
|
||||
|
||||
### 2. Templater 设置
|
||||
- **Template folder location**: `06_Metadata/Templates`
|
||||
- **Trigger Templater on new file creation**: ✓ 启用
|
||||
- **Enable folder templates**: ✓ 启用
|
||||
|
||||
### 3. 文件夹模板映射示例
|
||||
| 文件夹 | 模板 |
|
||||
|--------|------|
|
||||
| `00_Inbox` | `quick-note.md` |
|
||||
| `01_Projects` | `project.md` |
|
||||
| `02_Areas` | `area.md` |
|
||||
| `06_Metadata/Daily` | `daily-note.md` |
|
||||
|
||||
## 进阶技巧
|
||||
|
||||
### 1. JavaScript 代码块
|
||||
```javascript
|
||||
<%*
|
||||
// 可以写多行 JavaScript 代码
|
||||
const projectName = await tp.system.prompt("项目名称");
|
||||
const status = await tp.system.suggester(
|
||||
["进行中", "计划中", "已完成"],
|
||||
["active", "planned", "completed"]
|
||||
);
|
||||
tR += `项目：${projectName}\n状态：${status}`;
|
||||
%>
|
||||
```
|
||||
|
||||
### 2. 条件逻辑
|
||||
```javascript
|
||||
<%* if (tp.file.folder().includes("Projects")) { %>
|
||||
这是一个项目笔记
|
||||
<%* } else { %>
|
||||
这是一个普通笔记
|
||||
<%* } %>
|
||||
```
|
||||
|
||||
### 3. 循环生成内容
|
||||
```javascript
|
||||
<%* for (let i = 1; i <= 5; i++) { %>
|
||||
## 第 <%= i %> 部分
|
||||
<%* } %>
|
||||
```
|
||||
|
||||
## 常见问题
|
||||
|
||||
### Q: 模板不生效？
|
||||
A: 检查 Templater 设置中的模板文件夹路径是否正确
|
||||
|
||||
### Q: 如何在已有笔记中插入模板？
|
||||
A: 使用命令 "Templater: Insert Template" 或快捷键
|
||||
|
||||
### Q: 可以创建自定义函数吗？
|
||||
A: 可以！在 Templater 设置中配置 "User Scripts" 文件夹
|
||||
|
||||
## 相关资源
|
||||
|
||||
- 官方文档：https://silentvoid13.github.io/Templater/
|
||||
- 示例模板库：查看 `06_Metadata/Templates/` 文件夹
|
||||
|
||||
---
|
||||
|
||||
**标签**：#教程 #Templater #Obsidian #模板
|
||||
**创建日期**：<% tp.date.now("YYYY-MM-DD") %>
|
||||
Reference in New Issue
Block a user