Obsidian知识库搭建与维护指南
帮助新用户规划浅层目录、核心设置、模板及同步备份方案,逐步建立可持续使用的笔记库。
完整提示词
<context>
Obsidian stores notes as plain Markdown files in a folder (the vault), which makes notes portable but means the person is responsible for sync and backup. New users commonly lose weeks installing dozens of community plugins, building a dashboard and theming before they have 50 notes, then abandon the vault. Setups that last start with core features (links, backlinks, search, templates, daily notes, a graph they rarely use), a shallow folder structure, a fixed attachments folder, and "update links on rename" switched on, and add community plugins only to solve a specific felt problem. Settings names and plugin availability change between versions, so describe what each setting does and tell the person to check the current settings screen.
Use: {{use}}
{{#experience}}
Experience: {{experience}}
{{/experience}}
</context>
<task>
1. If the use is too vague to design for, ask one question about the main use and stop.
2. Propose a folder structure of at most about six top-level folders, explaining what goes where and what stays out of folders (handled by links or tags instead).
3. List the settings to change on day one, by what they do: where new notes and attachments go, keeping links updated when renaming, link format, and the template folder.
4. Recommend which core plugins to enable and why. Mention community plugins only if a stated need clearly requires one, and present them as optional with the advice to check maintenance status before installing.
5. Write two or three templates for the stated use, using only the core template placeholders for date and title, and say so.
6. Lay out sync and backup choices by type (the official paid sync service, a cloud drive folder, a git repository for technical users, manual copies), with trade-offs and the warning that a synced folder is not a backup.
7. Give a first-week build order that gets real notes in on day one.
</task>
<constraints>
- Do not claim exact menu labels or plugin names as current; describe the setting and say to search for it in settings.
- Do not recommend more than three community plugins, and none for beginners unless needed.
- Do not quote prices.
- Keep the structure shallow; justify any nesting beyond two levels.
</constraints>
<output_format>
## Folder structure
A code block showing the tree, then one line per folder.
## Settings to change
## Plugins
## Templates
Each in a fenced code block.
## Sync and backup
## First week
Day-by-day list.
</output_format>可替换内容
- {{use}}
- {{#experience}}
- {{experience}}
- {{/experience}}
分类与标签
办公效率、知识库搭建、笔记整理、Obsidian设置