如何将 Obsidian 打造成永不崩溃的个人操作系统

1# Personal Operating System — CLAUDE.md
2
3## Identity
4
5Name: [YOUR NAME]
6
7Role: [YOUR PRIMARY ROLE]
8
9Location: [YOUR CITY]
10
11## Life Areas and Current Status
12
13Health: [BRIEF STATUS — e.g., "Training for half marathon,
14running 4x per week"]
15
16Finances: [BRIEF STATUS — e.g., "Saving for house deposit,
17target by December 2026"]
18
19Relationships: [BRIEF STATUS — e.g., "Partner: [name].
20Key friendships to maintain: [names]"]
21
22Learning: [BRIEF STATUS — e.g., "Currently studying:
23[topic]. Goal: [outcome]"]
24
25Career: [BRIEF STATUS — e.g., "Current role: [title].
26Working toward: [goal]"]
27
28## Active Projects
29
30[Repeat for every active project]
31
32## Current Priorities
33
341. [MOST IMPORTANT THING THIS WEEK]
352. [SECOND MOST IMPORTANT]
363. [THIRD MOST IMPORTANT]
37
38## Standards for Generated Content
39
40Voice: [HOW YOU WRITE AND COMMUNICATE]
41
42Format preferences: [YOUR PREFERENCES]
43
44What you never want: [SPECIFIC THINGS TO AVOID]
45
46## Operating Rules
47
48- Never delete files. Move to ARCHIVE with timestamp.
49- Never send communications without human review.
50- Always date-stamp generated files as YYYY-MM-DD.
51- Log every significant action in SYSTEM/logs/operations.md.
52- When uncertain about placement, use GENERATED and flag.
53
54## Update Schedule
55
56This file is reviewed and updated: [YOUR SCHEDULE —
57e.g., every Monday morning]

1Read CLAUDE.md for full life context.
2
3Generate a morning briefing covering:
4
5MOST IMPORTANT TODAY: The single highest-leverage action
6I can take today based on my current priorities.
7
8SCHEDULE: Any events in CALENDAR/events/ dated today.
9Prepare a one-sentence brief for each one.
10
11OPEN LOOPS: Any items prefixed with OPEN: in yesterday's
12daily note.
13
14PROJECT PULSE: For each active project in CLAUDE.md:
15one sentence on status, one sentence on next action.
16
17WEEKLY FOCUS: If today is Monday, read the previous week's
18daily notes and identify the most important thing to
19accomplish this week.
20
21Format for under 300 words. Start with MOST IMPORTANT TODAY.
22
23Save to: GENERATED/briefings/[DATE]-morning.md

1Read all files in the CAPTURE folder created today.
2
3For each captured item:
4
51. Identify what type it is:
6
7TASK: Something that requires action
8IDEA: Something to develop or research later
9REFERENCE: Information to store for later use
10NOTE: Context or observation about something active
11EVENT: Something time-bound to calendar
12
132. File it in the correct location:
14
15TASK → Create a task note in the relevant project or area
16IDEA → File in RESOURCES/research/ with the date
17REFERENCE → File in RESOURCES/references/ by topic
18NOTE → Append to the relevant project or daily note
19EVENT → Create an event file in CALENDAR/events/
20
213. For TASKS: extract the specific action, assign a due date
22if mentioned, and add to the relevant project task list.
23
244. After processing: move the original capture file to ARCHIVE.
25
26Log all processing actions in SYSTEM/logs/capture-log.md.

1Read all daily notes from the past 7 days.
2Read all project notes modified this week.
3Read CLAUDE.md for current life context and priorities.
4
5Generate the weekly review:
6
7WHAT MOVED FORWARD:
8Specific wins from the week. What caused each one.
9Be specific. Name the projects, the actions, the results.
10
11WHAT DID NOT MOVE:
12Honest assessment of what stalled.
13The most likely reason for each item that did not progress.
14
15THE WEEK'S PATTERN:
16One theme or insight that appeared repeatedly.
17Whether it signals something to change.
18
19NEXT WEEK'S PRIORITIES:
20Three specific priorities for next week ranked by impact.
21For each: why it matters, what the specific next action is.
22
23ONE DECISION:
24The most important decision sitting open right now.
25What information you have to make it.
26What the cost of delaying it another week is.
27
28Save to: GENERATED/summaries/[DATE]-weekly-review.md
29
30Update CLAUDE.md: Current Priorities section with next
31week's top 3.

1RESEARCH-stoic-philosophy-applications.md
2SUMMARIZE-project-meeting-notes.md
3DRAFT-email-to-landlord-about-repairs.md
4PLAN-trip-to-portugal-october.md
5DECIDE-whether-to-accept-new-client.md

1Check the QUEUE folder for any unprocessed files.
2
3For each file found:
4
51. Read the filename to identify the task type
62. Read the file content for specific instructions
73. Execute the task using the relevant skill from
8SYSTEM/skills/ if one exists
94. Save output to GENERATED/[task-type]/[DATE]-[topic].md
105. Move the queue file to ARCHIVE/queue-processed/
11
12Log all queue processing in SYSTEM/logs/queue-log.md.
13
14If the task requires information not available in the vault:
15Flag in the output as NEEDS HUMAN INPUT: [what is needed]

1Read CLAUDE.md for the list of active projects.
2Read the overview.md file in each active project folder.
3Read any project files modified in the last 7 days.
4
5For each project generate a health assessment:
6
7STATUS: On track / At risk / Stalled / Blocked
8EVIDENCE: What specifically indicates this status.
9Be concrete. Name files, dates, and specific observations.
10NEXT ACTION: The single most important thing this project
11needs in the next 48 hours.
12FLAG: Any project that has had no activity for more than
137 days. These need human attention.
14
15Save health report to:
16GENERATED/briefings/[DATE]-project-health.md
17
18For any FLAGGED projects: create a file in QUEUE named:
19REVIEW-[project-name].md with a summary of the situation.