定制轻量笔记模板与字段规范
按常用笔记类型生成适配应用的简洁模板,统一字段格式,并说明字段用途与删减理由。
完整提示词
<context>
Templates pay off for notes you create often and later want to compare or filter: people, projects, books, recipes, decisions, trips. The mistake is the 25-field template that takes five minutes to fill in, so half the fields stay empty forever and the person stops using it. A good template has a handful of structured fields you will actually filter or sort by (status, date, rating, type), a few prompts for the free text that matters, and nothing else. Field names should be consistent across templates (always "status", never "state" in one and "stage" in another) so searches work across note types.
Note types:
<types>
{{note_types}}
</types>
{{#examples}}
<examples>
{{examples}}
</examples>
{{/examples}}
{{#app}}
App: {{app}}
{{/app}}
</context>
<task>
1. If no note types are named, ask which notes the person writes most often and stop.
2. For each type, decide the structured fields from what the person says they want to find or compare. Use at most about six fields per template.
3. Use the same field names and value formats across all templates (dates as YYYY-MM-DD, status values from one shared list).
4. Add two to four free-text headings or prompts per template that capture what makes the note useful later.
5. If examples were given, match their wording and headings, and point out any useful detail they contain that the template should keep.
6. Format each template for the app: front matter properties for Obsidian, a property list for Notion databases, or plain headings if no app is given. Use only generic placeholders like [date] unless the app's template syntax is certain.
7. Write a field guide: each field, its allowed values and why it exists.
8. List fields you deliberately left out and why.
</task>
<constraints>
- Every structured field must trace back to something the person wants to find, sort or compare.
- Keep each template fillable in under a minute.
- Do not invent app-specific syntax or plugins; say "if your app supports properties".
</constraints>
<output_format>
## Templates
Each in a fenced code block under ### Type name.
## Field guide
Table: Field | Used in | Allowed values | Why
## What I left out
</output_format>可替换内容
- {{note_types}}
- {{#examples}}
- {{examples}}
- {{/examples}}
- {{#app}}
- {{app}}
- {{/app}}
- [date]
分类与标签
办公效率、笔记模板、字段规范、知识管理、笔记应用