同样用Claude,为什么有人每月多出52小时可支配时间
Source: http://x.com/i/article/2037124412349054977
有人连续两周记录了自己每一次使用 Claude 的时间戳、任务类型和手动完成同样任务需要的时间。最终数据:每周省出13小时,每月52小时,相当于每个月多出整整两个工作日
关键发现不是 Claude 有多强,而是大部分人所谓的"工作"其实是在反复切换上下文:开标签页、重读资料、走神后重新定位、做一些看起来有产出但实际没推进任何事情的动作
这10个工作流覆盖了研究、写作、代码审查到数据分析的完整场景。每一个都附带可以直接复制的 prompt
研究类:3个工作流省掉6小时我们可以用于做什么任务和场景 工作流一:结构化研究 以前做一个话题调研要开15个标签页,在 Google Doc 里复制粘贴,两小时后得到一份还需要整理的乱稿。现在一个 prompt 搞定
Research [TOPIC]. Structure: 1. Executive summary (3 sentences max) 2. Key findings (top 5, ranked by impact) 3. What's missing: gaps in available info 4. Sources with URLs If data is insufficient for any claim, say so. Don't speculate. Don't pad.
核心行是 "If data is insufficient for any claim, say so." 没有这句话 Claude 会自信地编造数字。加了这句,输出质量完全不同
每周从2小时压缩到15分钟,省1小时45分钟 工作流二:多源内容提炼
一篇文章通常需要阅读5到10个信源:GitHub README、文档、X 上的 thread、博客、changelog。手动阅读标注交叉引用过去要一个多小时
Here are my sources on [TOPIC]: [PASTE ALL RAW MATERIAL] Extract: 1. The 5 facts that matter most for my audience (builders, not consumers) 2. Anything that contradicts the common narrative 3. Specific numbers: stars, users, funding, benchmarks 4. One angle nobody else is covering If two sources disagree, show me both sides. Don't summarize fluff. Only signal.
每周从4小时压缩到1.5小时,省2小时30分钟 工作流三:GitHub 仓库批量筛选
写第一篇文章的时候需要从1000多个仓库里筛选出40个值得推荐的。每个仓库手动看3到5分钟就是50多个小时
Here's a list of GitHub repos with descriptions: [PASTE BATCH] For each repo, evaluate: 1. What it actually does (1 sentence, no marketing speak) 2. Traction signals: stars, recent commit activity, contributor count 3. Category: agent framework / dev tool / MCP / infrastructure / other 4. Worth featuring? Yes/No with one reason Skip anything that's just a wrapper, a tutorial repo, or has no commits in 30+ days. Sort the "Yes" picks by most interesting first.
关键过滤条件是"跳过30天内没有提交记录的仓库"。一半的热门仓库其实已经被放弃了。最终只需要手动验证80个,而不是审查1000个
工作类:4个工作流省掉5小 工作流四:数据分析不用表格 > Analyze this data. I need: 1. Top 3 trends over time 2. Anything unusual or unexpected 3. Correlations between [COLUMN A] and [COLUMN B] Table first, then a 2-paragraph summary explaining what this means in plain English. If the dataset is too small for a conclusion, say so.
直接上传 CSV,不用打开 Google Sheets 建公式。每周从2小时压缩到20分钟 工作流五:竞品分析 > I'm analyzing [COMPETITOR/ACCOUNT]. Based on what you know + the data I'm providing: 1. Top 3 things they're doing well (be specific) 2. Gaps or weaknesses in their approach 3. What I can learn from them 4. How my positioning is different About me: I write about AI tools, vibe coding, and crypto for builders. TG + X. Don't say "they have a strong brand." Tell me WHY and what specifically makes it work.
关键是给 Claude 你自己的上下文,不只是竞品的。不然你得到一份对谁都适用的通用 SWOT 分析。每周从1小时压缩到15分钟 工作流六:代码审查 > Review this code for: - Security issues (exposed keys, injection, XSS) - Logic errors and edge cases I might have missed - Performance problems - Anything that would make a senior dev uncomfortable For each issue: severity (Critical/High/Medium/Low), exact location, why it matters, and the corrected code. Be harsh. "Looks good overall" is not helpful. [PASTE CODE]
"Be harsh" 这句指令比你想象的重要。没有它 Claude 默认给礼貌反馈:"代码结构良好,也许可以考虑..." 加了之后你得到的是真正严厉的 code review 能量
每周从2小时压缩到15分钟 工作流七:长内容转短内容 > Here's my article: [PASTE OR UPLOAD] Create: 1. A 2-sentence hook for X (include a specific number or claim from the article) 2. A 4-paragraph TG post with the key insight 3. A provocative quote-tweet caption (1 sentence) 4. 3 standalone insights that work as separate tweets throughout the week Each piece must work independently. Someone who never read the article should still get value.
一篇长文变成:1条 TG 公告、3条分散在一周内的推文、2条引用推文标题、1个 thread 开头。一个 prompt 加10分钟编辑,以前要2小时
反过来也好用。把一周的5到6条短 TG 帖子全部粘贴进去,让 Claude 找到连接线索,生成长文大纲
效率类:3个工作流省掉1.5小时 工作流八:邮件 > Draft an email. To: [NAME + how I know them] Goal: [WHAT I WANT THEM TO DO] Tone: professional but sounds like a real person Max: 5 sentences Context: [THE SITUATION] Does not sound like: a cold pitch template, corporate speak, or something ChatGPT would write. No "I hope this email finds you well."
"Does not sound like ChatGPT" 这句是关键。没有它你每次都得到经典 AI 开头。加了之后 Claude 写出来的东西读起来像一个尊重对方时间的忙人
每周从30分钟压缩到5分钟 工作流九:每日早报 > 3-minute briefing: 1. Top 3 AI news from last 24 hours (one sentence each) 2. Crypto: major moves, liquidations, new narratives 3. Anything I should know before posting content today Be specific: names, numbers, links. Skip anything that isn't genuinely important. 3 real updates > 10 filler items.
替代了每天早上45分钟刷 X "保持更新"的习惯。刷 X 的问题是新闻混着drama、meme、钓鱼内容和20分钟的兔子洞。Claude 给你信号,不给噪音
不完美,有时候会漏掉最近一小时的突发新闻。但能覆盖80%重要信息,剩下20%群聊和通知里自然会刷到 工作流十:周度复盘(ROI 最高的一个) > Here are my notes and ideas from this week: [PASTE EVERYTHING] Help me: 1. Find patterns: what topics am I gravitating toward? 2. Which 3 ideas have the most content potential? 3. What am I ignoring that I shouldn't be? 4. Content plan for next week: 3 TG posts + 1 article topic Be honest. If an idea is weak, say so. Don't tell me everything is great.
周日晚上把一周所有的笔记、书签、半成品想法、截图全部扔进 Claude。它能看到你自己因为离得太近而看不见的跨主题关联
周日30分钟。省掉一周里"该写什么"的纠结时间。这是所有工作流里 ROI 最高的一个
完整时间统计
工作流之前之后每周节省结构化研究2h15min1h 45min多源内容提炼4h1.5h2h 30minGitHub 仓库筛选1.5h20min1h 10min数据分析2h20min1h 40min竞品分析1h15min45min代码审查2h15min1h 45min内容多平台分发2h20min1h 40min邮件30min5min25min每日早报45min5min40min周度复盘1h30min30min合计约13h/周这些数字因人而异。但即使只用其中3到4个,每周也能省出5小时以上
真正改变的是什么
最大的发现不是关于 Claude 或者 prompt 技巧,而是时间到底花在了哪里
大部分所谓的"工作"其实是上下文切换。开标签页、重读东西、走神后重新定位、做那些感觉有产出但没推进任何事的动作
思考和编辑仍然是你自己做。写什么、做什么决策、上线什么,这些判断 Claude 做不了
但初稿、研究、格式化、初步分析这些事现在用分钟计而不是用小时计。腾出来的时间留给了真正需要人脑的部分
说"AI 做不了我的工作"的人通常是对的。但 AI 大概率能做掉你工作周围60%的事务性劳动。而那60%正是所有浪费时间的藏身之处
via