# How to Actually Use Claude. 18 steps that unlock 100% of its potential
**作者**: Anatoli Kopadze
**日期**: 2026-05-13T14:26:20.000Z
**来源**: [https://x.com/AnatoliKopadze/status/2054568935274549597](https://x.com/AnatoliKopadze/status/2054568935274549597)
---
Claude has been out for two years. Most people who use it every day are still using 10% of what it can do.
Not because it's complicated. Because nobody showed them what the other 90% looks like.
This guide fixes that. By the end you will have Claude set up in a way that remembers you, understands you, and works the way you actually think. And you will know how to use it for things most people have never tried.
## Start Here
1 - Create a Project, not a chat
Every time you open a new Claude chat, it starts with zero memory. It doesn't know your name, your work, your goals, or how you like to communicate. You spend the first few messages re-explaining yourself, or you don't, and Claude gives you something generic that doesn't fit how you actually work.
Projects fix this. A Project is a persistent workspace where Claude keeps context across every conversation inside it. You set it up once and every session that follows starts with Claude already knowing who you are.
Go to Claude, click Projects in the sidebar, and create a new one. Name it something like "Work" or "Personal" depending on how you plan to use it. Everything that follows goes inside this Project.
2 - Tell Claude who you are
Before Claude can help you well, it needs to understand you. Most people skip this step entirely and wonder why Claude gives them answers that feel slightly off.
Paste this into your Project and fill in every field honestly. The more specific you are, the better every single response becomes.
```
My name is [your name].
I work as [your role or profession]. My main responsibilities are [2-3 things you actually do day to day].
Right now my biggest goals are [1-3 specific goals you're working toward].
I use Claude mostly for [list your main use cases — writing, research, analysis, learning, coding, etc].
My background and knowledge level: [what you know well, what you're learning, what you're new to].
How I like to receive information: [e.g. direct and concise / detailed with examples / step by step / no bullet points / short paragraphs].
Things I don't want: [e.g. don't add disclaimers, don't use corporate language, don't repeat what I just said back to me, don't start with "Great question"].
Topics and areas I care about: [your interests, industry, niche].
```
Save this inside your Project's knowledge base. Claude will read it at the start of every conversation in this Project.
3 - Turn that into Custom Instructions
Pasting your background is a good start. But Custom Instructions go further. They tell Claude not just who you are, but exactly how to behave with you by default.
Paste this prompt into Claude after you've filled in the template above:
```
Based on everything I've told you about myself, write me a set of custom instructions for this Claude Project.
The instructions should:
- Describe who I am and what I do
- Set my default communication style and format
- Tell Claude what to never do when working with me
- Define the tone I want in every response
- Include any default behaviors I would want in every session
Write them in second person, as if Claude is reading rules about how to help me. Be specific. No generic advice. Under 400 words.
```
Take the output and paste it into your Project Instructions. This becomes Claude's permanent operating mode for every conversation in this Project.
## Claude Is Not What You Think
4 - Claude is not a search engine
Most people use Claude the way they use Google. They type a question and wait for an answer. That is the lowest-value way to use it.
Claude is not a retrieval tool. It is a thinking partner. It doesn't just pull information, it reasons, synthesizes, argues, and builds on context. The moment you treat it like a search engine, you cut its usefulness by 80 percent.
Stop asking Claude what something is. Start asking Claude to help you think through something.
Instead of: "What is prompt caching?"
Try: "I'm building a workflow that calls Claude 20 times per session. Walk me through how prompt caching works and whether it would actually reduce my costs given that context."
The second prompt gives Claude a problem to solve with you. The first gives it a definition to recite.
5 - Ask Claude to ask you questions first
This is one of the most powerful techniques almost nobody uses. Before Claude starts any complex task, tell it to gather information from you first.
When Claude asks you questions before starting, the output is dramatically better because it's built on the right foundation. Without this, Claude makes assumptions and you spend time correcting things that could have been right the first time.
Use this before any important task:
```
Before you start, ask me the 5 most important questions that would help you do this well.
After I answer, then begin.
```
Or for a specific task:
```
I need you to help me write a cold email to a potential client.
Before you write anything, ask me what you need to know to make this genuinely good, not generic.
```
## What Even Regular Users Don't Know
6 - Style cloning
When Claude writes in your voice without examples, it writes in its own voice. The output is grammatically correct and completely wrong in tone. It sounds like AI because it is.
Give Claude three to five samples of your own writing. Ask it to analyze your patterns, not just describe your style. After that analysis, it writes like you, not like a polished corporate assistant.
```
Here are 3 examples of my writing:
[paste sample 1]
[paste sample 2]
[paste sample 3]
Analyze my writing style in detail. Look at: sentence length, rhythm, vocabulary choices, how I open and close paragraphs, what I avoid, how formal or informal I am, and any patterns that make my writing distinct.
After this, when I ask you to write anything for me, match this style exactly. Do not default to your own patterns.
```
7 - Claude as your sparring partner
Most people ask Claude to help them with ideas. That means Claude builds on what you say, adds to it, expands it. You get agreement and elaboration.
That is useful sometimes. But it is not how you stress-test an idea.
Before committing to any plan, decision, or piece of writing, ask Claude to attack it. Not critique it. Attack it. The distinction matters.
```
Here is my plan: [describe your plan]
Your job is to destroy it. Find every assumption I'm making that could be wrong. Find every way this could fail. Argue the opposite position as hard as you can. Do not be polite. Do not add qualifications. Just attack.
After that, steelman my position. Build the strongest possible case for why I'm right.
Then tell me what you actually think.
```
8 - Extended Thinking
Most Claude users have never turned this on. Extended Thinking is a mode where Claude reasons through a problem step by step before giving you an answer, instead of going straight to the output.
For simple tasks, you don't need it. For complex decisions, analysis, or any question where you want Claude to actually think rather than pattern-match, turn it on.
In Claude, click the brain icon before sending your message. Or add this to your prompt:
```
Think through this carefully before responding.
Work through the problem step by step, show your reasoning, identify where you're uncertain, then give me your conclusion.
```
The difference in output quality on hard questions is significant.
9 - Claude writes prompts for Claude
This is the most underused thing you can do. If you're not sure how to prompt Claude for a specific task, ask Claude to write the prompt for you.
Claude knows what kinds of instructions produce better results. Let it use that knowledge on your behalf.
```
I need Claude to help me [describe your actual task].
Write me the best possible prompt for this task.
Include role, context, format instructions, and any constraints that would improve the output.
Then use that prompt immediately.
```
## How to Spend Fewer Tokens and Get More
10 - Specify the output length
Claude's default is to write as much as it thinks is appropriate. That is usually more than you need, which means more tokens used, more time spent reading, and more noise in the output.
Tell Claude exactly how long you want the answer before it starts.
```
Answer in 3 sentences maximum.
```
```
Give me 5 bullet points. No explanations. Just the points.
```
```
Write this in under 150 words.
```
This one instruction cuts token usage on most tasks by 40 to 60 percent without losing any of the value you actually need.
11 - Remove the preamble
Every Claude response defaults to starting with something you didn't ask for. "Great question. Let me break this down for you." Or a full restatement of what you just said. Or a disclaimer. Or a closing summary that repeats everything it just told you.
You didn't ask for any of that. It costs tokens and it wastes your time.
Add this to your Custom Instructions:
```
Never start responses with preamble, affirmations, or restatements of my question.
Go directly to the answer.
Do not add a summary at the end unless I specifically ask for one.
No disclaimers unless the topic genuinely requires one.
```
12 - Don't re-explain yourself every conversation
If you're pasting the same background information into every new chat, you are wasting tokens every single time and training yourself into a habit that costs you more as Claude usage scales.
This is exactly what Projects and Custom Instructions are for. Put your context in once. Let Claude read it automatically at the start of every session. Never paste your background again.
If you are not using Projects yet, start there before anything else in this article.
13 - Start a new chat for a new topic
Claude carries the context of everything said earlier in a conversation. When you switch topics inside a long chat, Claude still has all the previous context loaded. That means more tokens used on every response, slower processing, and context bleed from earlier in the conversation affecting your new topic.
When you switch to something unrelated, start a fresh chat inside your Project. You keep the Project memory. You lose the irrelevant baggage.
## Ready to Use Right Now
These are complete prompts you can copy and use immediately.
14 - Understand anything through analogies (Feynman method)
Most explanations Claude gives by default are technically correct and practically useless. They use the same vocabulary as the thing you're trying to understand, which means you walk away with a definition but not actual comprehension.
The Feynman method forces understanding through simplicity. If Claude can't explain it in plain terms using analogies, it means the explanation isn't clear enough yet. This prompt works for anything from investing to quantum physics to how a specific API works.
```
Explain [topic] to me using only analogies and everyday examples. No jargon. Assume I have no background in this field.
After each analogy, check whether I've actually understood it by asking me one question. Based on my answer, go deeper or adjust the explanation.
Keep going until I can explain it back to you in my own words without using any technical terms.
```
15 - Travel plan built around how you actually travel
Most travel planning starts with destinations and ends with a generic itinerary you could find on any travel blog. Claude can do something different: build a plan around your specific travel style, pace, budget, and what actually matters to you, not what's on every must-see list.
The key is giving it real information about you, not just dates and locations.
```
I'm planning a trip to [destination]. I'll be there for [number of days]. My budget is approximately [amount] per day including accommodation.
Here's how I actually travel: [describe your style — do you like slow mornings or packed days, touristy places or local spots, museums or food, active or relaxed, solo or with someone, etc].
Things I want to avoid: [crowds, tourist traps, expensive restaurants, long transport times, etc].
Build me a day-by-day itinerary that fits this. For each day, include where to stay, what to do, where to eat, and any logistics I need to know. Flag anything that requires booking in advance.
```
16 - Monthly expense analysis with real conclusions
Most people look at their bank statement and feel vaguely bad about their spending without understanding what's actually happening. Claude can turn raw numbers into a clear picture of where your money is going and what you should actually do about it.
This works best when you paste real data, not estimates.
```
I'm going to paste my expenses from the last month. Analyze them and tell me:
1. What categories am I spending the most on
2. Where my spending looks unusual compared to what I described as my goals
3. What I could cut without meaningfully affecting my life
4. What I'm probably underspending on that matters
5. One specific change that would have the biggest financial impact
Here are my expenses: [paste your bank statement or expense list]
My financial goals right now: [describe what you're trying to do — save more, pay off debt, invest, etc]
```
17 - Claude as your personal thinking partner
Most people don't have someone in their life who will listen without judgment, ask the right questions, and help them work through something they're stuck on without pushing their own agenda. Claude can fill that role, but only if you give it the right instructions.
This isn't therapy. It's structured self-reflection with an outside perspective that helps you think more clearly.
```
I want to talk through something I'm dealing with. Your job is not to give me advice right away.
First, ask me questions to understand the situation fully. What's actually happening, how I feel about it, what I've already tried, and what outcome I'm hoping for.
After you understand the full picture, reflect back what you're hearing — not just the facts but what seems to be underneath them.
Then, and only then, offer your perspective. Be honest, not reassuring. Tell me what you actually think, including anything I might not want to hear.
Here's what's on my mind: [describe what you want to think through]
```
18 - Stress-test any business idea before you commit
Most business ideas die because people fall in love with them before testing them. They spend months building something nobody wants because they never honestly asked whether the idea was actually good.
Claude can act as a ruthless first filter. Not to kill ideas, but to find the real problems before they cost you time and money.
```
I have a business idea I want to stress-test before I invest serious time in it.
Here's the idea: [describe it in detail — what it is, who it's for, how it makes money, why you think it works]
Your job is to find everything wrong with it. Specifically:
1. What assumptions am I making that could be wrong
2. Who already does this and why I might lose to them
3. Why the target customer might not actually pay for this
4. What would have to be true for this to work, and how likely is that
5. The single biggest problem with this idea
Be specific. Generic risks like "the market might not be ready" are not useful. Give me the real version of each problem.
After that, tell me what the idea would need to look like to actually work.
```
## The Actual Point
Claude is not smarter than you. It does not have better ideas than you. What it has is infinite patience, broad knowledge, and the ability to think through problems from angles you haven't considered.
The people who get the most from Claude are not the ones with the best questions. They are the ones who have set it up to understand them, who give it real context, and who know how to use it as a partner rather than a dispenser.
Most people will read this and keep opening Claude the same way they always have.
Set it up once. Change how you work permanently.
## 相关链接
- [Anatoli Kopadze](https://x.com/AnatoliKopadze)
- [@AnatoliKopadze](https://x.com/AnatoliKopadze)
- [940K](https://x.com/AnatoliKopadze/status/2054568935274549597/analytics)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [10:26 PM · May 13, 2026](https://x.com/AnatoliKopadze/status/2054568935274549597)
- [940.1K Views](https://x.com/AnatoliKopadze/status/2054568935274549597/analytics)
- [View quotes](https://x.com/AnatoliKopadze/status/2054568935274549597/quotes)
---
*导出时间: 2026/5/14 16:34:34*
---
## 中文翻译
# 如何真正用好 Claude。18 个步骤解锁其 100% 的潜力
**作者**： Anatoli Kopadze
**日期**： 2026-05-13T14:26:20.000Z
**来源**： [https://x.com/AnatoliKopadze/status/2054568935274549597](https://x.com/AnatoliKopadze/status/2054568935274549597)
---
Claude 已经发布两年了。大多数每天都在使用它的人，仍然只用了它 10% 的能力。
这不是因为它复杂。而是因为没有人向他们展示剩下的 90% 是什么样子。
本指南就是为了解决这个问题。读完之后，你将把 Claude 设置成一个能记住你、理解你、并按照你实际的思维方式工作的助手。而且你还会知道如何用它来做大多数人从未尝试过的事情。
## 从这里开始
1 - 创建一个 Project（项目），而不是一个聊天
每次你打开一个新的 Claude 聊天，它都是从零记忆开始的。它不知道你的名字、你的工作、你的目标，也不知道你喜欢怎样的沟通方式。你在前几条消息里得重新介绍自己，或者你不介绍，然后 Claude 给你一些不符合你实际工作方式的泛泛之谈。
Projects 解决了这个问题。Project 是一个持久的工作区，Claude 会在其中的每次对话中保留上下文。你只需设置一次，之后的每个会话开始时，Claude 就已经知道你是谁了。
进入 Claude，点击侧边栏中的 Projects，创建一个新项目。根据你的使用计划，将它命名为"工作"或"个人"之类的名称。接下来的所有内容都放在这个 Project 里。
2 - 告诉 Claude 你是谁
在 Claude 能好好帮助你之前，它需要先了解你。大多数人完全跳过了这一步，然后纳闷为什么 Claude 给出的答案总感觉差了点意思。
把下面的内容粘贴到你的 Project 中，并诚实地填写每一项。你越具体，每一次回复的质量就越高。
```
我的名字是 [你的名字]。
我的职业是 [你的角色或专业]。我的主要职责是 [2-3 件你日常实际做的事情]。
现在我最大的目标是 [1-3 个你正在努力实现的具体目标]。
我主要用 Claude 来 [列出你的主要使用场景——写作、研究、分析、学习、编程等]。
我的背景和知识水平： [你熟悉什么，你在学什么，你是新手]。
我喜欢接收信息的方式： [例如：直接简洁 / 详细并附有例子 / 分步骤 / 不要用列表 / 短段落]。
我不想要的东西： [例如：不要加免责声明，不要用官方腔调，不要复述我刚才说的话，不要以"好问题"开头]。
我关心的话题和领域： [你的兴趣、行业、细分领域]。
```
把这份内容保存到你的 Project 知识库中。Claude 会在该 Project 中的每次对话开始时阅读它。
3 - 把它转化为自定义指令
粘贴你的背景信息是一个好的开始。但自定义指令能更进一步。它们不仅告诉 Claude 你是谁，还告诉它默认情况下应该如何与你相处。
在你填好上面的模板后，把这段提示词粘贴给 Claude：
```
根据我告诉你的关于我自己的所有信息，为这个 Claude Project 写一套自定义指令。
这些指令应该：
- 描述我是谁以及我做什么
- 设定我默认的沟通风格和格式
- 告诉 Claude 在与我合作时绝不能做什么
- 定义我在每次回复中想要的语气
- 包含我希望每次会话中默认执行的任何行为
以第二人称撰写，就像 Claude 在阅读关于如何帮助我的规则。要具体。不要泛泛而谈。400 字以内。
```
把生成的结果粘贴到你的 Project Instructions（项目指令）中。这将成为 Claude 在该 Project 中每次对话的永久操作模式。
## Claude 不是你想的那样
4 - Claude 不是搜索引擎
大多数人使用 Claude 的方式就像使用谷歌一样。他们输入一个问题，然后等待答案。这是使用它价值最低的方式。
Claude 不是检索工具。它是一个思考伙伴。它不仅仅是提取信息，它还会推理、综合、辩论并基于上下文进行构建。一旦你把它当作搜索引擎，就削减了它 80% 的用处。
不要再问 Claude 某个东西是什么。开始让 Claude 帮你思考某个问题。
不要问："什么是提示词缓存？"
试试这样问："我正在构建一个工作流，每个会话要调用 Claude 20 次。请为我讲解提示词缓存是如何工作的，以及在这个上下文下它是否真的能降低我的成本。"
第二个提示给 Claude 提供了一个需要和你一起解决的问题。第一个只是给它一个需要背诵的定义。
5 - 先让 Claude 向你提问
这是几乎没人使用的最强大的技巧之一。在 Claude 开始任何复杂任务之前，告诉它先从你这里收集信息。
当 Claude 在开始之前向你提问时，输出质量会显著提高，因为它建立在正确的基础之上。没有这一步，Claude 会自行假设，而你就得花时间纠正那些本来一开始就能做对的事情。
在任何重要任务之前使用这个：
```
在你开始之前，先问我 5 个最重要的问题，它们能帮助你把这件事做好。
在我回答之后，再开始。
```
或者针对特定任务：
```
我需要你帮我给一位潜在客户写一封开发信。
在你写任何东西之前，先问问我，你需要知道什么才能让这封信真正出色，而不是泛泛而谈。
```
## 即使是普通用户也不知道的事
6 - 风格克隆
当 Claude 在没有示例的情况下用你的口吻写作时，它用的是自己的口吻。输出在语法上正确，但在语气上完全错误。它听起来像 AI，因为它就是 AI。
给 Claude 三到五个你自己的写作样本。让它分析你的模式，而不仅仅是描述你的风格。经过那次分析之后，它写出来的东西就像你，而不像一个经过打磨的企业助理。
```
以下是我的 3 个写作示例：
[粘贴示例 1]
[粘贴示例 2]
[粘贴示例 3]
请详细分析我的写作风格。考察以下方面：句子长度、节奏、用词选择、我如何开头和结尾段落、我避免什么、我的正式或非正式程度，以及任何使我的写作独具特色的特点。
在此之后，当我让你为我写作任何内容时，都要精确匹配这种风格。不要退回到你自己的模式。
```
7 - 让Claude做你的陪练对手
大多数人让Claude帮他们出主意。这意味着Claude会在你说的基础上构建、添加、扩展。你得到的是认同和 elaboration。
这有时是有用的。但这不是压力测试一个想法的方法。
在确定任何计划、决策或写作之前，让Claude攻击它。不是批评它。是攻击它。这个区别很重要。
```
这是我的计划：[描述你的计划]
你的任务是摧毁它。找出我每一个可能出错的假设。找出这可能会失败的每一种方式。尽你所能为相反的立场辩护。不要客气。不要加上限定条件。只管攻击。
然后，对我的立场进行最强论证。为我为什么是对的构建最有力的理由。
然后告诉我你的真实想法。
```
8 - 扩展思考
大多数Claude用户从未开启过这个功能。扩展思考是一种模式，Claude会在给你答案之前逐步推理一个问题，而不是直接输出结果。
对于简单任务，你不需要它。对于复杂决策、分析，或任何你希望Claude真正思考而非模式匹配的问题，请开启它。
在Claude中，发送消息前点击大脑图标。或者在提示词中加入：
```
在回答之前仔细思考这个问题。
逐步解决问题，展示你的推理过程，指出你不确定的地方，然后给我你的结论。
```
在难题上输出质量的差异是显著的。
9 - Claude为Claude写提示词
这是最被低估的做法。如果你不确定如何为特定任务编写Claude提示词，让Claude为你写提示词。
Claude知道什么样的指令能产生更好的结果。让它代表你运用这些知识。
```
我需要Claude帮我[描述你的实际任务]。
为这个任务写出尽可能好的提示词。
包括角色设定、上下文、格式说明，以及任何能提升输出质量的约束条件。
然后立即使用这个提示词。
```
## 如何花更少的Token获得更多
10 - 指定输出长度
Claude的默认做法是写多少它认为合适的字数。这通常超过你的需要，意味着更多Token消耗、更多阅读时间，以及输出中更多的噪音。
在Claude开始之前，明确告诉它你想要多长的答案。
```
最多用3句话回答。
```
```
给我5个要点。不要解释。只要要点。
```
```
在150字以内写完。
```
这一条指令能将大多数任务的Token消耗减少40%到60%，而不损失任何你真正需要的内容。
11 - 去掉开场白
Claude的每次回复默认都以你没要求的内容开头。"好问题。让我为你拆解一下。"或者完整复述你刚才说的话。或者免责声明。或者一个重复它刚告诉你的一切的结尾总结。
你没有要求任何这些内容。它消耗Token并浪费你的时间。
在你的自定义指令中加入：
```
回复永远不要以开场白、肯定语或复述我的问题开始。
直接给出答案。
除非我特别要求，否则不要在结尾加总结。
除非话题确实需要，否则不加免责声明。
```
12 - 不要每次对话都重新解释自己
如果你每次新对话都在粘贴同样的背景信息，你每次都在浪费Token，并让自己养成一个随着Claude使用量增加而成本越来越高的习惯。
这正是Projects（项目）和自定义指令的用途所在。把你的上下文设置一次。让Claude在每次会话开始时自动读取。再也不用粘贴你的背景信息。
如果你还没有使用Projects，请先从这里开始，再看本文的其他内容。
13 - 新话题开新对话
Claude会保留对话中之前所说的一切的上下文。当你在长对话中切换话题时，Claude仍然加载着所有先前的上下文。这意味着每次回复消耗更多Token、处理更慢，以及对话早期上下文对你的新话题产生干扰。
当你切换到不相关的内容时，在Project中开启新对话。你保留了Project的记忆，甩掉了不相关的包袱。
## 立即可用
这些是完整的提示词，可以直接复制使用。
14 - 通过类比理解任何事物（费曼方法）
Claude默认给出的解释在技术上正确但实际上无用。它们使用与你要理解的对象相同的词汇，这意味着你获得了一个定义，却没有真正的理解。
费曼方法通过简化来强制理解。如果Claude不能用类比和通俗的语言解释清楚，说明解释还不够清晰。这个提示词适用于任何主题，从投资到量子物理到某个具体API的工作原理。
```
只用类比和日常例子向我解释[主题]。不要用行话。假设我在这个领域没有任何背景。
每个类比之后，问我一个问题来检验我是否真正理解了。根据我的回答，深入讲解或调整解释方式。
一直继续，直到我能用自己的话向你解释清楚，且不使用任何技术术语。
```
15 - 围绕你实际的旅行方式定制的旅行计划
大多数旅行规划从目的地开始，最后给你一份在任何旅行博客上都能找到的通用行程单。Claude可以做得不同：围绕你特定的旅行风格、节奏、预算以及对你真正重要的东西来制定计划，而不是那些人人必看的清单上的内容。
关键是向它提供关于你的真实信息，而不只是日期和地点。
```
我计划去[目的地]旅行，会待[天数]。我的预算大约是每天[金额]，包含住宿。
以下是我的实际旅行风格：[描述你的风格——你喜欢慢节奏的早晨还是满满的行程，喜欢热门景点还是本地小众去处，喜欢博物馆还是美食，偏活跃还是放松，独自出行还是结伴，等等]。
我想避开的东西：[拥挤人群、旅游陷阱、昂贵餐厅、漫长的交通时间，等等]。
据此为我制定一份逐日行程。每一天都要包括住哪里、做什么、去哪里吃饭，以及我需要知道的任何后勤事项。标出需要提前预订的内容。
```
16 - 带有真实结论的月度支出分析
大多数人看着银行账单，对自己的开销有一种模糊的愧疚感，却不明白实际发生了什么。Claude 可以把原始数字转化为一幅清晰的图景：你的钱花到哪里去了，以及你真正应该怎么办。
当你粘贴真实数据而非估算时，效果最佳。
```
我准备粘贴过去一个月的支出记录。请分析并告诉我：
1. 我在哪些类别上花得最多
2. 与我描述的目标相比，哪些支出显得不寻常
3. 我可以削减哪些支出而不明显影响生活
4. 我可能在哪些重要方面花钱不足
5. 一项能带来最大财务影响的具体改变
以下是我的支出：[粘贴你的银行账单或支出清单]
我目前的财务目标：[描述你想要实现的事情——多存钱、还债、投资，等等]
```
17 - 让 Claude 成为你的个人思考伙伴
大多数人的生活中没有这样一个人：不带评判地倾听、问出正确的问题、帮助你理清卡住的事情，而不夹杂自己的意图。Claude 可以扮演这个角色，但前提是你要给它正确的指示。
这不是心理治疗。这是一种结构化的自我反思，借助外部视角帮助你更清晰地思考。
```
我想谈谈我正在面对的一件事。你的任务不是立刻给我建议。
首先，向我提问以充分了解情况。实际发生了什么，我的感受如何，我已经尝试过什么，我期望的结果是什么。
在你了解全貌之后，把你听到的内容复述给我——不仅是事实，还有事实之下似乎隐藏的东西。
然后，也只有在那时，再给出你的观点。要诚实，而不是安慰。告诉我你的真实想法，包括我可能不想听到的内容。
以下是我心里想的事：[描述你想要梳理清楚的问题]
```
18 - 在投入之前对任何商业想法进行压力测试
大多数商业点子之所以夭折，是因为人们在验证之前就爱上了它。他们花几个月构建没人想要的东西，因为他们从未诚实地问过这个点子是否真的好。
Claude 可以充当一个毫不留情的第一道过滤器。不是为了扼杀想法，而是为了让真正的问题在你付出时间和金钱之前浮出水面。
```
我有一个商业想法，想在投入大量时间之前先做压力测试。
以下是这个想法：[详细描述——它是什么，面向谁，如何赚钱，你为什么认为它可行]
你的任务是找出它所有的问题。具体来说：
1. 我做了哪些可能错误的假设
2. 谁已经在做这件事，而我为什么可能会输给他们
3. 目标客户为什么不一定会为此付费
4. 要让这个想法成立，哪些条件必须为真，其可能性有多大
5. 这个想法最大的单一问题
要具体。“市场可能尚未成熟”这类泛泛的风险没有用处。给我每个问题的真实版本。
之后，告诉我这个想法需要是什么样子才能真正行得通。
```
## 真正的重点
Claude 并不比你聪明。它的想法也不比你的更好。它拥有的是无限的耐心、广博的知识，以及从你没有考虑过的角度思考问题的能力。
从 Claude 获益最多的人，并不是那些提问最好的人。而是那些设置好它来理解自己的人，那些给它真实背景的人，以及那些知道如何把它当作伙伴而非自动售货机来使用的人。
大多数人读完这篇文章后，仍会以一贯的方式打开 Claude。
花一次时间设置好它，永久地改变你的工作方式。
## 相关链接
- [Anatoli Kopadze](https://x.com/AnatoliKopadze)
- [@AnatoliKopadze](https://x.com/AnatoliKopadze)
- [94万](https://x.com/AnatoliKopadze/status/2054568935274549597/analytics)
- [升级到 Premium](https://x.com/i/premium_sign_up)
- [2026年5月13日 22:26](https://x.com/AnatoliKopadze/status/2054568935274549597)
- [94.01万次浏览](https://x.com/AnatoliKopadze/status/2054568935274549597/analytics)
- [查看引用](https://x.com/AnatoliKopadze/status/2054568935274549597/quotes)
---
*导出时间: 2026/5/14 16:34:34*
