Back to Details

filing

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Filing

归档

Help with file organization: where things belong and keeping inboxes clear.
协助文件管理：确定文件归属位置，保持收件箱整洁。

When to Use

适用场景

  • "Where should this file go?"
  • Weekly review (filing portion)
  • Moving files between zones
  • Deciding Projects vs Areas vs Resources
  • "这个文件该放哪里？"
  • 每周回顾（归档环节）
  • 在不同区域间移动文件
  • 区分项目、职责领域与资源

When NOT to Use

不适用场景

  • Pattern reflection (use todoist-gtd)
  • Todoist organization (use todoist-gtd)
  • Code/repo organization (different rules apply)
  • 模式反思（使用todoist-gtd）
  • Todoist 管理（使用todoist-gtd）
  • 代码/仓库管理（遵循不同规则）

Core Principle: Filing = Processing + Organizing

核心原则：归档 = 处理 + 整理

You can't file what you haven't processed.
Moving files without reading them isn't filing — it's relocating the problem. Proper filing means:
  1. Processing — Read content, extract what matters (actions, waiting-fors, calendar items)
  2. Organizing — Move to the right location with the right name
If you skip processing, actions get lost, waiting-fors vanish, and meeting notes become information graves.
The test: Before moving a file, can you answer: "What's in this and does anything need to happen?"
未处理的文件无法完成归档。
不阅读就移动文件不是归档——只是转移问题。规范的归档流程包括：
  1. 处理 — 读取内容，提取关键信息（行动项、待跟进事项、日历项）
  2. 整理 — 将文件移动到正确位置并重命名
如果跳过处理步骤，行动项会丢失，待跟进事项会石沉大海，会议记录会变成信息坟墓。
检验标准： 在移动文件前，你能否回答："这个文件里有什么内容？有哪些需要跟进的事项？"

Work Folder Structure

工作文件夹结构

Location: 
~/Library/CloudStorage/GoogleDrive-*/My Drive/Work
To find exact path: 
ls -d ~/Library/CloudStorage/GoogleDrive-*/My\ Drive/Work
Work/
├── Projects/           # Active outcome folders
├── Areas/              # Ongoing responsibilities
├── Resources/          # Reference material (Larder, GTD Resources)
├── Archive/            # Completed/dormant
└── Meeting Notes/      # By year (2015-2025)
位置：
~/Library/CloudStorage/GoogleDrive-*/My Drive/Work
查看准确路径：
ls -d ~/Library/CloudStorage/GoogleDrive-*/My\ Drive/Work
Work/
├── Projects/           # 进行中的项目文件夹
├── Areas/              # 持续的职责领域
├── Resources/          # 参考资料（Larder、GTD 资源）
├── Archive/            # 已完成/暂停的项目
└── Meeting Notes/      # 按年份分类（2015-2025）

Projects/

Projects/

Active work with defined end states. Folders named: 
{Area} - {Outcome statement}
Examples:
  • Industry Influencing - Marketing Week Articles
  • Product Development - Launched new dashboard...
When complete: Move to Archive/
有明确结束状态的活跃工作。文件夹命名格式：
{职责领域} - {成果描述}
示例：
  • Industry Influencing - Marketing Week Articles
  • Product Development - Launched new dashboard...
完成后： 移动到 Archive/

Areas/

Areas/

Ongoing responsibilities (no completion date):
  • Budget and Finance
  • Cross-Broadcaster Measurement
  • Desired Outcomes Planning
  • Industry Advisory Roles
  • Industry Influencing
  • Internal Stakeholders
  • Managing Myself
  • Processes and Systems
  • Team Development
持续的职责（无明确完成日期）：
  • 预算与财务
  • 跨广播方衡量
  • 预期成果规划
  • 行业顾问角色
  • 行业影响力建设
  • 内部利益相关方
  • 自我管理
  • 流程与系统
  • 团队发展

Resources/

Resources/

Reference material that supports work:
  • Larder/ - 100+ research PDFs
  • GTD Resources (Common)/ - GTD reference docs
支持工作的参考资料：
  • Larder/ - 100+ 研究PDF
  • GTD Resources (Common)/ - GTD 参考文档

Archive/

Archive/

Completed projects and dormant materials. Preserves history.
已完成项目和暂停的资料，用于保留历史记录。

Meeting Notes/

Meeting Notes/

Organized by year:
Meeting Notes/
├── 2024/
└── 2025/
    └── 2025-12-11 Alex Maguire (Netflix) - EMEA measurement landscape.md
Naming: 
{date} {Person/Topic} - {Brief description}.md
按年份 chronological 组织：
Meeting Notes/
├── 2024/
└── 2025/
    └── 2025-12-11 Alex Maguire (Netflix) - EMEA measurement landscape.md
命名格式：
{日期} {人员/主题} - {简要描述}.md

PARA Quick Reference

PARA 快速参考

CategoryDefinitionCompletion
ProjectsActive work with end stateFinite - move to Archive when done
AreasOngoing responsibilitiesInfinite - never "done"
ResourcesReference materialSupports work, isn't the work
ArchiveInactive itemsSuperseded or completed
Key distinction: Areas ≠ Projects. "Team Development" is an Area (infinite). "Hire data scientist" is a Project (finite).
分类定义完成状态
Projects有明确结束状态的活跃工作有限期 - 完成后移动到 Archive
Areas持续的职责领域无限期 - 永远不会“完成”
Resources参考资料支持工作，但不是工作本身
Archive非活跃项目已被取代或完成
关键区别： Areas ≠ Projects。“团队发展”是Area（无限期）。“招聘数据科学家”是Project（有限期）。

How This Differs from Strict PARA

与标准PARA的差异

Strict PARA has 4 equal categories (Projects, Areas, Resources, Archive).
This structure adds:
  • Meeting Notes/ - Chronological organization by year (not in PARA)
  • Areas are predefined (not emergent as in strict PARA)
Core PARA principle remains: Projects complete, Areas don't.
Why the additions: Meeting notes benefit from chronological access. Areas reflect actual work responsibilities.
标准PARA包含4个平等的分类（Projects、Areas、Resources、Archive）。
本结构新增：
  • Meeting Notes/ - 按年份 chronological 组织（标准PARA中没有）
  • Areas 是预定义的（而非标准PARA中的自然形成）
PARA核心原则保留： Projects会完成，Areas不会。
新增原因： 会议记录按时间顺序访问更高效。Areas反映实际工作职责。

Weekly Cleanup Zones

每周清理区域

Nine locations where clutter accumulates:
九个容易堆积杂乱的位置：

1. Local Downloads

1. 本地下载文件夹

Path: 
~/Downloads
Typical contents: PDFs, screenshots, installers, random files from web.
Action: File to Work/ or delete.
路径： 
~/Downloads
典型内容：PDF、截图、安装程序、网页下载的随机文件。
行动： 归档到Work/或删除。

2. iCloud Downloads

2. iCloud下载文件夹

Path: 
~/Library/Mobile Documents/com~apple~CloudDocs/Downloads
Typical contents: Screenshots (iOS sync), files from iOS apps.
Action: File to Work/ or delete. Check for screenshots that should go to projects.
路径： 
~/Library/Mobile Documents/com~apple~CloudDocs/Downloads
典型内容：截图（iOS同步）、iOS应用导出的文件。
行动： 归档到Work/或删除。检查是否有需要归档到项目的截图。

3. iA Writer Strays

3. iA Writer 零散文件

Path: 
~/Library/Mobile Documents/27N4MQEA55~pro~writer/Documents
Structure:
Documents/
└── Diary/          # Structured diary entries (leave alone)
└── [stray files]   # Waifs outside Diary folder
Action: Anything outside 
Diary/
is a stray. File or delete.
路径： 
~/Library/Mobile Documents/27N4MQEA55~pro~writer/Documents
结构：
Documents/
└── Diary/          # 结构化日记条目（保留）
└── [stray files]   # Diary文件夹外的零散文件
行动： 所有
Diary/
外的文件都是零散文件，归档或删除。

4. Desktop (iCloud-synced)

4. 桌面（iCloud同步）

Path: 
~/Desktop
iCloud Desktop & Documents sync enabled. Files may be cloud-only (evicted from local storage).
Typical contents: Screenshots, drag-dropped files, temporary staging.
Action: File to Work/ or delete. Most Desktop items are transient.
iCloud voodoo: Files can appear as stubs (cloud-only, download on access). When bulk processing, may trigger downloads. The 
.localized
file is system-managed - leave it.
路径： 
~/Desktop
已启用iCloud桌面与文档同步。文件可能仅存于云端（已从本地存储移除）。
典型内容：截图、拖放的文件、临时暂存文件。
行动： 归档到Work/或删除。大多数桌面文件都是临时文件。
iCloud特殊说明： 文件可能显示为占位符（仅云端存在，访问时下载）。批量处理时可能触发下载。
.localized
文件由系统管理 - 保留。

5. Work Folder Root

5. Work文件夹根目录

Path: 
~/Library/CloudStorage/GoogleDrive-*/My Drive/Work
Should only contain CLAUDE.md (project instructions) - nothing else belongs at root level.
Typical contents: Stray files that missed proper subfolder, CLAUDE.md.
Action: CLAUDE.md stays. Everything else gets filed into Projects/, Areas/, Resources/, or Archive/.
路径： 
~/Library/CloudStorage/GoogleDrive-*/My Drive/Work
仅应包含CLAUDE.md（项目说明）- 其他任何文件都不应在根目录。
典型内容：未归档到子文件夹的零散文件、CLAUDE.md。
行动： CLAUDE.md保留。其他所有文件归档到Projects/、Areas/、Resources/或Archive/。

6. My Drive Root (Inbox)

6. My Drive根目录（收件箱）

Path: 
~/Library/CloudStorage/GoogleDrive-*/My Drive
True inbox per PARA. Where 
doc.new
creates files, where shared docs land, where quick-captured items accumulate.
Typical contents: New Google Docs, shared files, unsorted captures.
Action: Triage into Work/ subfolders or delete. This is the primary inbox to keep clear.
路径： 
~/Library/CloudStorage/GoogleDrive-*/My Drive
符合PARA标准的收件箱。
doc.new
创建的文件、共享文档、快速捕获的项目都会聚集在这里。
典型内容：新Google文档、共享文件、未分类的捕获内容。
行动： 分类归档到Work/子文件夹或删除。这是需要保持整洁的主要收件箱。

7. My Drive Temp (Claude Staging)

7. My Drive Temp（Claude暂存区）

Path: 
~/Library/CloudStorage/GoogleDrive-*/My Drive/Temp
Nominated temp folder for Claude operations — file uploads, MCP staging, transient outputs.
Typical contents: PDFs uploaded for analysis, intermediate files, staged outputs.
Action: Delete everything. If something needs keeping, it should have been filed properly after the session that created it. This folder should be empty between sessions.
路径： 
~/Library/CloudStorage/GoogleDrive-*/My Drive/Temp
为Claude操作指定的临时文件夹——文件上传、MCP暂存、临时输出。
典型内容：上传分析的PDF、中间文件、暂存输出。
行动： 删除所有内容。如果有需要保留的内容，应在创建它的会话后已正确归档。此文件夹在会话之间应保持为空。

8. Work Inbox (iCloud)

8. Work收件箱（iCloud）

Path: 
~/Library/Mobile Documents/com~apple~CloudDocs/Work Inbox/
Quick capture landing zone from iOS Shortcuts. Subfolders organize by type:
Work Inbox/
├── Voice Transcripts/   ← Whisper output from JPR recordings
├── Meeting Notes/       ← iOS Shortcut meeting captures
└── Quick Notes/         ← General quick capture
Naming: 
YYYY-MM-DD [HH-MM] Title.md
Action per subfolder:
SubfolderTriage
Voice Transcripts/Review, extract actions, file to Meeting Notes/ or delete
Meeting Notes/Copy to Google Drive Meeting Notes/{year}/, keep original
Quick Notes/File to PARA, extract to Todoist, or delete
路径： 
~/Library/Mobile Documents/com~apple~CloudDocs/Work Inbox/
来自iOS快捷指令的快速捕获落地区。按类型分文件夹：
Work Inbox/
├── Voice Transcripts/   ← JPR录音的Whisper转录输出
├── Meeting Notes/       ← iOS快捷指令捕获的会议记录
└── Quick Notes/         ← 通用快速捕获内容
命名格式：
YYYY-MM-DD [HH-MM] Title.md
各子文件夹行动：
子文件夹分类操作
Voice Transcripts/回顾、提取行动项、归档到Meeting Notes/或删除
Meeting Notes/复制到Google Drive Meeting Notes/{year}/，保留原件
Quick Notes/归档到PARA结构、提取到Todoist或删除

9. JPR Voice Recordings

9. JPR语音录音

Path: 
~/Library/Mobile Documents/iCloud~com~openplanetsoftware~just-press-record/Documents/
Just Press Record voice memos (m4a/mp3). Organized by date: 
YYYY-MM-DD/HH-MM-SS.m4a
Action:
  1. Transcribe with 
    ~/.claude/scripts/transcribe-jpr.sh --new
  2. Review transcript in Work Inbox/Voice Transcripts/
  3. Audio moves to 
    Processed/
    subfolder automatically
路径： 
~/Library/Mobile Documents/iCloud~com~openplanetsoftware~just-press-record/Documents/
Just Press Record语音备忘录（m4a/mp3）。按日期组织：
YYYY-MM-DD/HH-MM-SS.m4a
行动：
  1. 使用
    ~/.claude/scripts/transcribe-jpr.sh --new
    转录
  2. 在Work Inbox/Voice Transcripts/中回顾转录内容
  3. 音频自动移动到
    Processed/
    子文件夹

When Filing Signals Deeper Patterns

归档信号反映深层模式

File organization chaos often symptoms deeper behavioral patterns. Surface these signals during weekly review:
SignalPatternResponse
Downloads >100 files OR >2 weeks neglectExecution-Without-Reflection"This backlog suggests rushing through tasks without processing. Want to check patterns?"
Multiple "temporary" folders >1 month oldScope Creep"These temp folders suggest projects expanding beyond original scope."
Coordination pattern: Filing is Phase 1 of weekly review. After tidying, todoist-gtd skill handles pattern reflection (Phase 3).
Don't skip the pattern check just because you tidied the files.
文件组织混乱通常是更深层行为模式的症状。在每周回顾时发现这些信号：
信号模式应对措施
下载文件夹有>100个文件 或 超过2周未清理执行不反思"这个积压表明你在匆忙完成任务而没有处理。要不要检查一下模式？"
多个“临时”文件夹存在超过1个月范围蔓延"这些临时文件夹表明项目超出了最初的范围。"
协作模式： 归档是每周回顾的第一阶段。整理完成后，todoist-gtd技能处理模式反思（第三阶段）。
不要因为整理了文件就跳过模式检查。

Processing (Before You File)

处理（归档前）

Processing means reading and extracting — not just moving.
处理意味着读取和提取——而不仅仅是移动。

Processing Checklist (Meeting Notes)

会议记录处理清单

Before filing ANY meeting note:
  • Read the content — Don't just look at the title
  • Extract actions (mine) — Concrete next steps I need to take
  • Extract waiting-fors — 
    NAME: What they owe me
    format
  • Note calendar items — Dates to add to calendar
  • Quality check: empty? — Delete (with confirmation)
  • Quality check: misnamed? — Rename to match content
  • THEN move to destination
Mandatory extraction: Cannot file meeting notes until actions are extracted. This is not optional.
在归档任何会议记录前：
  • 阅读内容 — 不要只看标题
  • 提取行动项（我的） — 我需要执行的具体下一步
  • 提取待跟进事项 — 
    姓名: 他们欠我的内容
    格式
  • 记录日历项 — 需要添加到日历的日期
  • 质量检查：空文件？ — 删除（需确认）
  • 质量检查：命名错误？ — 重命名以匹配内容
  • 然后移动到目标位置
强制提取： 必须提取行动项后才能归档会议记录，这是硬性要求。

Processing Other File Types

其他文件类型的处理

File TypeProcessing Required
Meeting notesFull checklist above
Quick notesCheck for actions, then file or delete
Voice transcriptsRead transcript, extract actions, then file or delete
PDFs/docsUnderstand content for proper filing location
ScreenshotsDetermine project context, file or delete
文件类型处理要求
会议记录完成上述完整清单
快速笔记检查是否有行动项，然后归档或删除
语音转录阅读转录内容，提取行动项，然后归档或删除
PDF/文档理解内容以确定正确归档位置
截图确定项目上下文，归档或删除

Action Extraction Workflow (Sublime Loop)

行动项提取工作流（Sublime循环）

When processing multiple meeting notes with actions:
处理多个包含行动项的会议记录时：

1. Extract to Temp File

1. 提取到临时文件

Create structured sections:
markdown
undefined
创建结构化章节：
markdown
undefined

Waiting For

待跟进

NAME: What they owe me
姓名: 他们欠我的内容

Ping

待办

Quick actions for me to do
我需要执行的快速行动

Calendar

日历

Date - Event to add
undefined
日期 - 需要添加的事件
undefined

2. Open for Review

2. 打开供回顾

bash
open -a "Sublime Text" /tmp/meeting-actions.md
bash
open -a "Sublime Text" /tmp/meeting-actions.md

3. Tell User

3. 告知用户

"Edit, save, let me know when ready"
User fixes:
  • Names (Susie → Susan)
  • Stale/irrelevant items (delete)
  • Vague actions (clarify)
"编辑、保存，完成后告诉我"
用户修改：
  • 姓名（Susie → Susan）
  • 过时/无关项（删除）
  • 模糊行动项（明确）

4. After Save

4. 保存后

Read file, add to Todoist via todoist-gtd skill.
Why this works:
  • User sees all actions at once
  • Catches errors before they hit Todoist
  • Disambiguation happens in familiar editor
  • Claude processes clean, user-approved list
读取文件，通过todoist-gtd技能添加到Todoist。
为什么有效：
  • 用户可以一次性查看所有行动项
  • 在进入Todoist前发现错误
  • 在熟悉的编辑器中消除歧义
  • Claude处理经过用户批准的清晰列表

Meeting Source Discovery

会议源文件发现

At weekly review start, check beyond the 9 zones.
每周回顾开始时，检查9个区域之外的内容。

Standing Docs (Always Check)

固定文档（必查）

Prompt first: "Any changes to this standing docs list? (Add/remove as your meetings evolve)"
DocID
MIT: Start the Week
19NqCEPMSOdIdouFqVaHZVA-GyJmkmPjLGyNknTJpU3M
Client Reference
1owM77DjcTwHjrTfHs9zEfQfNyeFfmtheokBGvkPD8II
Supplier Reference
1b2vaWpGx-fUj48vuQ0KmIirDu5loodC7F4j3XGV4_DU
Notes – WEEKLY senior team catch up
1B5X-MrSzldgFElppNlk4s_PDgpIJ0H5Sul74uqQnTs8
TVA/MP/ITV Status
1tCuph3QWiObYImjb-7nfPPI2Q-D2RjAtou-dceHa45c
首先提示： "这个固定文档列表有变化吗？（根据你的会议调整添加/删除）"
文档ID
MIT: Start the Week
19NqCEPMSOdIdouFqVaHZVA-GyJmkmPjLGyNknTJpU3M
Client Reference
1owM77DjcTwHjrTfHs9zEfQfNyeFfmtheokBGvkPD8II
Supplier Reference
1b2vaWpGx-fUj48vuQ0KmIirDu5loodC7F4j3XGV4_DU
Notes – WEEKLY senior team catch up
1B5X-MrSzldgFElppNlk4s_PDgpIJ0H5Sul74uqQnTs8
TVA/MP/ITV Status
1tCuph3QWiObYImjb-7nfPPI2Q-D2RjAtou-dceHa45c

Calendar-Linked Docs

日历关联文档

Prompt: "What recurring meetings had sessions this week? Any have running docs I should check?"
(Future: mise calendar integration to auto-discover — see mise-en-space backlog)
提示： "这周有哪些 recurring 会议？有没有需要检查的持续更新文档？"
（未来：集成mise日历自动发现——查看mise-en-space待办）

Filing Decisions

归档决策

"Where does this go?"

"这个文件该放哪里？"

If it's...Put it in...
Active project artifactProjects/{relevant project}/
Meeting notesMeeting Notes/{year}/
Reference PDF/docResources/Larder/ or relevant Resources subfolder
Completed projectArchive/
Ongoing area docAreas/{relevant area}/
Screenshot for projectProjects/{project}/ or delete
Random downloadDelete or file if valuable
如果是...放到...
活跃项目工件Projects/{相关项目}/
会议记录Meeting Notes/{年份}/
参考PDF/文档Resources/Larder/ 或相关Resources子文件夹
已完成项目Archive/
持续领域文档Areas/{相关领域}/
项目截图Projects/{项目}/ 或删除
随机下载文件删除或如果有价值则归档

Personal Documents Zone

个人文档区域

Path: 
~/Documents/Personal/
Personal documents with PARA structure (no numbering, aligned with Work folder):
Personal/
├── Projects/     # Active personal projects
├── Areas/        # Ongoing personal responsibilities (e.g., Ash)
├── Archive/      # Completed/dormant
└── CLAUDE.md     # Project instructions
Note: No Resources folder - personal "resources" live in Areas as active things.
Action: Personal admin docs (scanned letters, etc.) go to appropriate Area.
路径： 
~/Documents/Personal/
采用PARA结构的个人文档（无编号，与Work文件夹对齐）：
Personal/
├── Projects/     # 活跃的个人项目
├── Areas/        # 持续的个人职责（例如：Ash）
├── Archive/      # 已完成/暂停的项目
└── CLAUDE.md     # 项目说明
注意： 没有Resources文件夹 - 个人“资源”作为活跃内容存放在Areas中。
行动： 个人管理文档（扫描的信件等）放到对应的Area。

Team Shared Drives

团队共享驱动器

Detection: 
ls "$GDRIVE/Shared drives/"
Team shared content lives in Shared Drives (not personal My Drive):
Team Shared Drive/
├── Team Reference/      # Team-specific reference material
├── Shared Reference/    # Cross-team reference material
└── External Reference/  # External/industry reference
Action: Team reference materials (shared tools, analytics) go here, not personal Drive.
检测： 
ls "$GDRIVE/Shared drives/"
团队共享内容存放在共享驱动器（而非个人My Drive）：
Team Shared Drive/
├── Team Reference/      # 团队专属参考资料
├── Shared Reference/    # 跨团队参考资料
└── External Reference/  # 外部/行业参考资料
行动： 团队参考资料（共享工具、分析）放到这里，而非个人Drive。

Filing Workflow

归档工作流

Zone Check (Do This First)

区域检查（首先执行）

At session start, explicitly check ALL zones - don't skip any:
bash
GDRIVE=$(ls -d ~/Library/CloudStorage/GoogleDrive-* 2>/dev/null | head -1)
echo "=== 1. Downloads ===" && ls ~/Downloads | head -5
echo "=== 2. iCloud Downloads ===" && ls ~/Library/Mobile\ Documents/com~apple~CloudDocs/Downloads 2>/dev/null | head -5
echo "=== 3. iA Writer ===" && ls ~/Library/Mobile\ Documents/27N4MQEA55~pro~writer/Documents 2>/dev/null | grep -v Diary | head -5
echo "=== 4. Desktop ===" && ls ~/Desktop 2>/dev/null | head -5
echo "=== 5. Work root ===" && ls "$GDRIVE/My Drive/Work" 2>/dev/null | grep -v "^CLAUDE.md$" | head -5
echo "=== 6. My Drive root ===" && find "$GDRIVE/My Drive" -maxdepth 1 -type f ! -name ".DS_Store" 2>/dev/null | head -5
echo "=== 7. My Drive Temp ===" && ls "$GDRIVE/My Drive/Temp" 2>/dev/null | head -5
echo "=== 8. Work Inbox ===" && find ~/Library/Mobile\ Documents/com~apple~CloudDocs/Work\ Inbox -type f ! -name ".DS_Store" 2>/dev/null | head -5
echo "=== 9. JPR Voice ===" && find ~/Library/Mobile\ Documents/iCloud~com~openplanetsoftware~just-press-record/Documents -name "*.m4a" -o -name "*.mp3" 2>/dev/null | grep -v "/Processed/" | head -5
Report which zones have content before starting. Don't skip zones that look empty - verify each one.
会话开始时，明确检查所有区域 - 不要跳过任何一个：
bash
GDRIVE=$(ls -d ~/Library/CloudStorage/GoogleDrive-* 2>/dev/null | head -1)
echo "=== 1. Downloads ===" && ls ~/Downloads | head -5
echo "=== 2. iCloud Downloads ===" && ls ~/Library/Mobile\ Documents/com~apple~CloudDocs/Downloads 2>/dev/null | head -5
echo "=== 3. iA Writer ===" && ls ~/Library/Mobile\ Documents/27N4MQEA55~pro~writer/Documents 2>/dev/null | grep -v Diary | head -5
echo "=== 4. Desktop ===" && ls ~/Desktop 2>/dev/null | head -5
echo "=== 5. Work root ===" && ls "$GDRIVE/My Drive/Work" 2>/dev/null | grep -v "^CLAUDE.md$" | head -5
echo "=== 6. My Drive root ===" && find "$GDRIVE/My Drive" -maxdepth 1 -type f ! -name ".DS_Store" 2>/dev/null | head -5
echo "=== 7. My Drive Temp ===" && ls "$GDRIVE/My Drive/Temp" 2>/dev/null | head -5
echo "=== 8. Work Inbox ===" && find ~/Library/Mobile\ Documents/com~apple~CloudDocs/Work\ Inbox -type f ! -name ".DS_Store" 2>/dev/null | head -5
echo "=== 9. JPR Voice ===" && find ~/Library/Mobile\ Documents/iCloud~com~openplanetsoftware~just-press-record/Documents -name "*.m4a" -o -name "*.mp3" 2>/dev/null | grep -v "/Processed/" | head -5
在开始前报告哪些区域有内容。不要跳过看起来为空的区域 - 逐一验证。

Per-File Process (5 Steps)

单文件处理（5步骤）

When triaging files, follow this 5-step process:
  1. Process - Read content, extract what matters
    • For meeting notes: extract actions, waiting-fors, calendar items (see Processing section)
    • For other files: understand content for proper filing
    • Use Sublime Loop for batch processing multiple notes
    • For text files: Claude reads directly
    • For binary/GUI files: 
      open -a "Sublime Text" file.md
      or 
      open file.pdf
    • Office files in Google Drive (.docx, .xlsx, .pptx): These open in native apps (Word, Excel, PowerPoint), not browser. To open in Google Docs instead, fetch the Drive URL via mise and open that:
      bash
      # Don't do this (opens in Word):
open "My Drive/document.docx"

# Do this instead (opens in browser):
# 1. Get file ID via mise search
# 2. open "https://docs.google.com/document/d/FILE_ID"
      Or flag to user: "These .docx files will open in Word — want Drive URLs instead?"
  2. Rename - Adjust filename to match actual content
    • Generic names like "Untitled" or "Copy of..." need proper names
    • Use descriptive names: 
      Simon McCarthy - Pricing Power Proposal
  3. Split - If multiple topics in one file, separate them
    • Open in GUI for user review
    • Create new files for distinct topics
  4. Capture - Outstanding actions → Todoist
    • Before adding: Search for existing/completed tasks to avoid duplicates
    • Use todoist-gtd skill (invoke with 
      Skill(todoist-gtd)
      ) for Todoist operations
    • Link description to filed document
  5. File - Move to correct location (or delete)
    • See "Filing Decisions" section for where things go
    • After filing Meeting Notes: Extract to memory for searchability
      bash
      # Re-scan to pick up the filed document
cd ~/Repos/claude-mem && uv run mem scan --source local_md

# Extract entities from the filed document
SOURCE_ID="local_md:$(basename "$DEST_PATH")"
cd ~/Repos/claude-mem && uv run mem extract "$SOURCE_ID" 2>/dev/null || true
分类文件时，遵循以下5步流程：
  1. 处理 - 读取内容，提取关键信息
    • 会议记录：提取行动项、待跟进事项、日历项（见处理部分）
    • 其他文件：理解内容以确定正确归档位置
    • 批量处理多个笔记时使用Sublime循环
    • 文本文件：Claude直接读取
    • 二进制/GUI文件：
      open -a "Sublime Text" file.md
      或 
      open file.pdf
    • Google Drive中的Office文件（.docx, .xlsx, .pptx）： 这些会在原生应用（Word、Excel、PowerPoint）中打开，而非浏览器。要在Google Docs中打开，通过mise获取Drive URL并打开：
      bash
      # 不要这样做（会在Word中打开）：
open "My Drive/document.docx"

# 应该这样做（在浏览器中打开）：
# 1. 通过mise搜索获取文件ID
# 2. open "https://docs.google.com/document/d/FILE_ID"
      或告知用户："这些.docx文件会在Word中打开——需要Drive链接吗？"
  2. 重命名 - 调整文件名以匹配实际内容
    • 通用名称如"Untitled"或"Copy of..."需要重命名为合适的名称
    • 使用描述性名称：
      Simon McCarthy - Pricing Power Proposal
  3. 拆分 - 如果一个文件包含多个主题，拆分它们
    • 在GUI中打开供用户回顾
    • 为不同主题创建新文件
  4. 捕获 - 未完成的行动项 → Todoist
    • 添加前： 搜索现有/已完成任务以避免重复
    • 使用todoist-gtd技能（通过
      Skill(todoist-gtd)
      调用）进行Todoist操作
    • 在描述中链接到归档的文档
  5. 归档 - 移动到正确位置（或删除）
    • 查看“归档决策”部分确定存放位置
    • 归档会议记录后： 提取到内存以支持搜索
      bash
      # 重新扫描以识别归档的文档
cd ~/Repos/claude-mem && uv run mem scan --source local_md

# 从归档的文档中提取实体
SOURCE_ID="local_md:$(basename "$DEST_PATH")"
cd ~/Repos/claude-mem && uv run mem extract "$SOURCE_ID" 2>/dev/null || true

Archive vs Reference

Archive vs Reference

The test: "Will I search for this to USE it, or just to REMEMBER it?"
AnswerLocationExamples
USE itResources/Methodology docs, templates, how-to guides
REMEMBER itArchive/Completed project artifacts, old meeting notes
Reference = I'll need this again to do work
  • Research PDFs that inform decisions
  • Templates I reuse
  • Product specs, methodology docs
Archive = This was a thing, now it's done
  • Completed project artifacts
  • Superseded versions
  • Historical records
检验标准： "我搜索这个是为了使用它，还是仅仅为了回忆它？"
答案位置示例
使用它Resources/方法论文档、模板、操作指南
回忆它Archive/已完成项目工件、旧会议记录
Reference = 我会再次需要它来完成工作
  • 指导决策的研究PDF
  • 我重复使用的模板
  • 产品规格、方法论文档
Archive = 曾经存在，现在已结束
  • 已完成项目工件
  • 已被取代的版本
  • 历史记录

Common Filing Patterns

常见归档模式

External doc → Google Doc → Project folder

外部文档 → Google Doc → 项目文件夹

When filing a document that needs to live in a Project:
  1. Read content (use docx skill for Word docs)
  2. Create Project folder if needed: 
    {Area} - {Outcome statement}
  3. Convert to Google Doc: 
    mcp__mise__create
  4. Delete original file
  5. Update any Todoist task that references it with new link
归档需要存放在项目中的文档时：
  1. 阅读内容（使用docx技能处理Word文档）
  2. 如有需要创建项目文件夹：
    {区域} - {成果描述}
  3. 转换为Google Doc：
    mcp__mise__create
  4. 删除原文件
  5. 更新Todoist中引用该文件的任务，添加新链接

Todoist task linking

Todoist任务链接

When a filed document relates to a Todoist task, use the todoist-gtd skill to search and link. Canonical document location should be in Todoist task description.
当归档的文档与Todoist任务相关时，使用todoist-gtd技能搜索并链接。文档的标准位置应在Todoist任务描述中。

Weekly Review Integration

每周回顾集成

Note: Weekly review is a three-phase workflow orchestrated by todoist-gtd skill:
  1. Filing (this skill) — Clear cleanup zones
  2. Outcomes Review (todoist-gtd) — Check outcome health
  3. Pattern Reflection (todoist-gtd) — Freedom score, pattern interrupts
During weekly review, check all 9 cleanup zones:
  1. ~/Downloads - File or delete
  2. iCloud Downloads - File or delete
  3. iA Writer strays - File or delete
  4. ~/Desktop - File or delete (mind iCloud stubs)
  5. Work/ root - Only CLAUDE.md should remain
  6. My Drive root - Triage into Work/ or delete
  7. My Drive Temp - Delete everything (Claude staging folder)
  8. Work Inbox - Triage subfolders (Voice Transcripts, Meeting Notes, Quick Notes)
  9. JPR Voice - Transcribe new recordings, review transcripts
注意： 每周回顾是由todoist-gtd技能编排的三阶段工作流：
  1. 归档（本技能）——清理杂乱区域
  2. 成果回顾（todoist-gtd）——检查成果健康状况
  3. 模式反思（todoist-gtd）——自由度评分、模式中断
每周回顾期间，检查所有9个清理区域：
  1. ~/Downloads - 归档或删除
  2. iCloud Downloads - 归档或删除
  3. iA Writer零散文件 - 归档或删除
  4. ~/Desktop - 归档或删除（注意iCloud占位符）
  5. Work/根目录 - 仅保留CLAUDE.md
  6. My Drive根目录 - 分类归档到Work/或删除
  7. My Drive Temp - 删除所有内容（Claude暂存文件夹）
  8. Work Inbox - 分类子文件夹（Voice Transcripts、Meeting Notes、Quick Notes）
  9. JPR Voice - 转录新录音，回顾转录内容

Anti-Patterns

反模式

PatternProblemFix
File without readingActions lostMandatory processing first
Bulk move meeting notesWaiting-fors vanishUse Sublime Loop, extract first
Skip running docsMiss recurring meeting actionsCheck standing docs + calendar prompt
Skip zones during weekly reviewClutter accumulatesCheck ALL 9 zones explicitly
Keep "just in case"Folders bloatDelete liberally, most things don't need keeping
File without renamingUntitled docs pile upRename to content-descriptive name first
Skip Todoist search before addingDuplicate tasksAlways search for existing task first
模式问题修复
不阅读就归档行动项丢失强制先处理
批量移动会议记录待跟进事项丢失使用Sublime循环，先提取
跳过持续更新文档错过 recurring 会议行动项检查固定文档 + 日历提示
每周回顾时跳过区域杂乱堆积明确检查所有9个区域
保留“以防万一”的文件文件夹臃肿大胆删除，大多数文件不需要保留
不重命名就归档无标题文档堆积先重命名为描述性名称
添加前跳过Todoist搜索重复任务始终先搜索现有任务

Remember

记住

File promptly, delete liberally. Most downloads don't need keeping. Screenshots are usually transient. When in doubt, delete.
Projects complete, Areas don't. If you're wondering "is this done?", it's probably a Project. If you're wondering "is this still my responsibility?", it's an Area.
及时归档，大胆删除。 大多数下载文件不需要保留。截图通常是临时的。如有疑问，删除。
Projects会完成，Areas不会。 如果你在想“这个完成了吗？”，它可能是Project。如果你在想“这还是我的职责吗？”，它可能是Area。

~/Repos Naming Convention

~/Repos 命名约定

Development tools live in 
~/Repos/
with prefix conventions:
PrefixContainsExample
claude-suite
Core session skillsopen, close, beads, filing
skill-*
Specialized skills
skill-itv-styling
mcp-*
MCP servers
mcp-workspace
infra-*
Infrastructure
infra-openwrt
claude-*
Claude experiments
claude-memory
Skills: Symlinked to 
~/.claude/skills/
. Core skills in 
claude-suite/skills/
, specialized skills in individual repos, skills with tooling co-located with their infrastructure.
开发工具存放在
~/Repos/
，使用前缀约定：
前缀包含内容示例
claude-suite
核心会话技能open, close, beads, filing
skill-*
专业技能
skill-itv-styling
mcp-*
MCP服务器
mcp-workspace
infra-*
基础设施
infra-openwrt
claude-*
Claude实验
claude-memory
技能： 符号链接到
~/.claude/skills/
。核心技能在
claude-suite/skills/
，专业技能在单独的仓库中，带有工具的技能与基础设施共存。