# How to Actually Set Up Claude Projects That Most Users Don't Know
**作者**: Khairallah AL-Awady
**日期**: 2026-06-06T09:08:29.000Z
**来源**: [https://x.com/eng_khairallah1/status/2063186252606865711](https://x.com/eng_khairallah1/status/2063186252606865711)
---
Most people treat Claude Projects like a folder with a label on it.
They create a project. They give it a name. Maybe they write a sentence or two in the system prompt. Maybe they upload a file. Then they start chatting and wonder why the output feels the same as regular Claude.
That is not a project. That is a labeled chatbox.
The people getting insane results from Claude Projects are building something completely different. They are building customized AI employees. Each project is tuned so precisely that Claude knows their voice, their standards, their audience, their workflow, and their exact definition of "good output" before they type a single word.
I spent three weeks testing every possible project configuration. Different system prompts. Different knowledge file combinations. Different organizational structures. I rebuilt the same project twelve times until the output was consistently excellent with minimal prompting.
Here is the exact blueprint that works.
## Why Most Claude Projects Fail
There are three reasons most people's projects produce mediocre output.
Reason 1: The system prompt is too vague.
"You are a helpful writing assistant" is not a system prompt. It is a wasted opportunity. Claude already knows how to be helpful. What it does not know is your specific voice, your audience, your formatting rules, your quality bar, and the fifteen things you hate seeing in an output.
Reason 2: There are no knowledge files uploaded.
A project without knowledge files is just a labeled conversation. The entire point of a project is that Claude has persistent access to reference documents that shape every single response. If you are not uploading files, you are not using the feature.
Reason 3: The project tries to do everything.
One project called "Work Stuff" that handles emails, content, strategy, research, coding, and analysis will produce mediocre results across all of them. Separate your workflows into separate projects. Each one should do one thing extremely well.
# The 6-Part Project Blueprint
Every high-performing project has six components. Skip any of them and the output quality drops noticeably. I tested this by removing each component one at a time and measuring the difference in output quality. The drop was immediate every single time.
## Part 1: The Identity Block
This is the first thing in your system prompt. It tells Claude exactly who it is in this project.
Not "you are a helpful assistant." Something like this:
You are my senior content strategist and writer. You have been working with me for two years. You know my voice, my audience, and my quality standards intimately.
Your job in this project is to research, plan, draft, and edit long-form articles for my audience of 250,000 followers who are learning AI tools for the first time.
You are direct. You are specific. You never use filler. Every sentence earns its place or gets cut.
Why this works: Claude performs dramatically better when it has a clear identity. "You have been working with me for two years" creates a framing where Claude defaults to confident, specific output rather than generic safe output. The specificity of "250,000 followers who are learning AI tools" gives it a concrete audience to write for.
## Part 2: The Rules Block
This is the non-negotiable list of things Claude must always do and must never do in this project. This is the most important part of your system prompt by far.
ALWAYS:
- Use short paragraphs. Maximum 3 sentences per paragraph.
- Include specific numbers rather than vague claims. Never say "many" or "some." Give a number.
- Bold the key insight in every section so a skimmer can read just the bold text and get the core message.
- Open with a hook that creates a gap between what the reader thinks they know and what is actually true.
- End with a CTA that creates urgency without being salesy.
NEVER:
- Use the word "leverage" or "utilize" or "streamline"
- Start any sentence with "In today's" or "It's important to note"
- Use em dashes
- Write generic advice that could apply to anyone. Every point must be specific and actionable.
- Include disclaimers or hedging language like "it depends" without immediately following with the specific thing it depends on
Why this works: Rules are constraints. Constraints force Claude into a specific lane where it cannot default to its generic patterns. Every time you find yourself correcting Claude's output, that correction should become a rule. After a month of this, your rules list is a precision instrument.
## Part 3: The Process Block
This tells Claude exactly how to approach work in this project. Not what to produce but how to think.
PROCESS:
1. Before writing anything, spend your first paragraph thinking about what the reader already believes about this topic. Your opening must challenge that belief.
2. Outline the complete structure before writing any section. Share the outline with me for approval before proceeding.
3. Write the first draft in one pass without self-editing.
4. Review the draft against my Rules. Fix any violations.
5. Check every claim for a specific supporting number or example. Replace anything vague.
6. Read the entire piece as if you are a busy person scrolling on their phone. Cut anything that would make them stop reading.
Why this works: Without a process block, Claude jumps straight to generating output. With one, it follows a structured workflow that produces consistently higher-quality results. The "read as a busy person scrolling on their phone" instruction alone improved my content quality more than any other single line.
## Part 4: The Output Format Block
This defines exactly what the finished product looks like. Eliminate all guessing.
OUTPUT FORMAT:
- Title: [Number] + [Claude-Specific Topic] + [Exclusion Hook]
- Length: 2000-3500 words
- Structure: Bold contrast opener (2 paragraphs) > Context section > Numbered main content > Strong closing CTA
- Subheadings: Bold, written as hooks that make the reader want to read the section
- Closing: Italic line + bold italic line using the "most people will X / the ones who Y" dichotomy
Why this works: When Claude knows the exact format before it starts writing, it distributes its effort correctly. Without this, it front-loads detail in the early sections and rushes the ending. With it, every section gets proportional attention.
## Part 5: The Knowledge Files
This is where your project gets its real intelligence. Upload these files and Claude references them in every single conversation:
File 1: Style guide (REQUIRED)
A document showing your writing style. Include at least three examples of your best work. Claude pattern-matches against these examples to capture your voice. Without this file, Claude writes in its default style. With it, Claude writes in yours.
File 2: Audience profile (REQUIRED)
Who reads your content? What do they already know? What frustrates them? What are they trying to achieve? What level of technical depth do they want? Write this as a one-page persona document. Claude uses it to calibrate every piece of content.
File 3: Competitor analysis (RECOMMENDED)
What does the competition look like in your space? What topics have been covered to death? What angles are overused? Upload examples of content you want to be different from. Claude uses this to avoid generic takes.
File 4: Performance data (RECOMMENDED)
Which of your past pieces performed best? What titles got the most engagement? What topics resonated? Upload your metrics. Claude uses this data to make better strategic decisions about what to write and how to position it.
File 5: Template library (RECOMMENDED)
Your best-performing formats as reusable templates. Article structures. Email frameworks. Report layouts. Claude uses these as starting frameworks instead of inventing structure from scratch every time.
## Part 6: The Onboarding Message
This is the first message you send in a new conversation within the project. Think of it as the daily briefing you would give an employee.
Today we are working on [TASK].
Here is the context: [WHAT I NEED AND WHY]
Reference my style guide for voice. Reference my audience profile for targeting. Reference my performance data for strategic decisions.
Before starting, tell me:
1. What angle would make this stand out from what already exists?
2. What does the reader already believe that we can challenge?
3. What is the one-sentence hook?
Once I approve the angle, proceed with a full outline.
Why this works: This message activates all five knowledge files, sets the task context, and forces Claude to think strategically before writing. Without it, Claude starts generating immediately. With it, Claude plans first and executes better.
## The Complete System Prompt Template (Copy This)
Here is the full system prompt, assembled from all six parts. Copy it. Modify the details for your specific use case. Paste it into your project.
IDENTITY:
You are my [ROLE]. You have worked with me for two years. You know my voice, my audience, and my standards.
Your job in this project is to [PRIMARY FUNCTION] for [AUDIENCE DESCRIPTION].
You are [COMMUNICATION STYLE]. You never [ANTI-PATTERNS].
RULES:
ALWAYS:
- [Rule 1]
- [Rule 2]
- [Rule 3]
- [Rule 4]
- [Rule 5]
NEVER:
- [Anti-rule 1]
- [Anti-rule 2]
- [Anti-rule 3]
- [Anti-rule 4]
PROCESS:
1. [Step 1 - Think/Plan]
2. [Step 2 - Outline/Structure]
3. [Step 3 - Execute]
4. [Step 4 - Review against rules]
5. [Step 5 - Quality check]
OUTPUT FORMAT:
- Format: [EXACT FORMAT SPECIFICATION]
- Length: [WORD COUNT RANGE]
- Structure: [SECTION ORDER]
- Style: [SPECIFIC STYLE MARKERS]
# The 5 Projects Everyone Needs
You do not need twenty projects. You need five. Each one handles one core workflow.
Project 1: Content Production
System prompt defines your writing voice, audience, and content standards. Knowledge files include your style guide, best-performing pieces, audience persona, and content calendar.
Project 2: Research and Analysis
System prompt defines how you want research structured, what sources you trust, and what depth of analysis you expect. Knowledge files include your research methodology, past analyses as examples, and your evaluation criteria.
Project 3: Communication
System prompt defines your email and messaging style, your professional tone, and your relationship with different audiences (clients, team, leadership). Knowledge files include examples of great emails you have written and templates for common message types.
Project 4: Strategy and Planning
System prompt defines your business context, your goals, your constraints, and how you think about decisions. Knowledge files include your business plan, competitor data, market research, and strategic frameworks you use.
Project 5: Code and Technical Work
System prompt defines your tech stack, coding conventions, architecture preferences, and quality standards. Knowledge files include your CLAUDE.md content, architecture decision records, and code examples that show your preferred patterns.
## What Happens After You Set This Up
Here is what changes.
Before this setup: You type a detailed prompt. Claude gives you a decent response. You spend twenty minutes editing it to match your voice and standards. You do this five to ten times a day.
After this setup: You type a two-sentence task description. Claude gives you an output that already matches your voice, follows your rules, targets your audience, and hits your quality bar. You spend two minutes reviewing it. You do this five to ten times a day.
That is a 90% reduction in editing time across every single task you delegate to Claude.
The math is simple. If you use Claude for two hours a day and this saves you 60% of your editing and correction time, that is over an hour saved daily. Five hours per week. Over 250 hours per year.
That is six full work weeks of your life back. From a one-time setup that takes about forty-five minutes.
Most people will keep using Claude Projects as labeled chat windows and wonder why their results are average.
The ones who build their blueprint today will never prompt the old way again. And they will never understand how they worked without it.
Follow me @eng_khairallah1 for more AI courses, tools, and workflows. New content every week.
hope this was useful for you, Khairallah ❤️
## 相关链接
- [Khairallah AL-Awady](https://x.com/eng_khairallah1)
- [@eng_khairallah1](https://x.com/eng_khairallah1)
- [404K](https://x.com/eng_khairallah1/status/2063186252606865711/analytics)
- [CLAUDE.md](http://claude.md/)
- [@eng_khairallah1](https://x.com/@eng_khairallah1)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [5:08 PM · Jun 6, 2026](https://x.com/eng_khairallah1/status/2063186252606865711)
- [404.5K Views](https://x.com/eng_khairallah1/status/2063186252606865711/analytics)
- [View quotes](https://x.com/eng_khairallah1/status/2063186252606865711/quotes)
---
*导出时间: 2026/6/7 15:51:02*
---
## 中文翻译
# 大多数用户不知道的 Claude 项目真正搭建方法
**作者**: Khairallah AL-Awady
**日期**: 2026-06-06T09:08:29.000Z
**来源**: [https://x.com/eng_khairallah1/status/2063186252606865711](https://x.com/eng_khairallah1/status/2063186252606865711)
---
大多数人只是把 Claude 项目当作一个贴了标签的文件夹。
他们创建一个项目。给它起个名字。也许会在系统提示词里写一两句话。也许会上传一个文件。然后他们开始聊天，却奇怪为什么输出的感觉和普通 Claude 没什么两样。
那不是项目。那只是个贴了标签的聊天框。
那些从 Claude 项目中获得惊人效果的人，正在构建完全不同的东西。他们正在构建定制化的 AI 员工。每个项目都经过了精确调优，以至于 Claude 在他们输入一个字之前，就已经了解了他们的语调、标准、受众、工作流程以及他们对“良好输出”的确切定义。
我花了三周时间测试了每一种可能的项目配置。不同的系统提示词。不同的知识文件组合。不同的组织结构。我重建了同一个项目十二次，直到输出在只需极简提示词的情况下始终表现出色。
以下是行之有效的精确蓝图。
## 为什么大多数 Claude 项目会失败
大多数人的项目产生平庸输出有三个原因。
原因 1：系统提示词太模糊。
“你是一个乐于助人的写作助手”不是系统提示词。那是浪费机会。Claude 本来就知道如何提供帮助。它不知道的是你特定的语调、你的受众、你的格式规则、你的质量标准，以及你讨厌在输出中看到的十五样东西。
原因 2：没有上传知识文件。
没有知识文件的项目只是一场贴了标签的对话。项目的全部意义在于 Claude 可以持续获取能塑造每一次响应的参考文档。如果你不上传文件，你就没有在使用这个功能。
原因 3：项目试图包办一切。
一个叫“工作杂项”的项目，同时处理邮件、内容、策略、研究、编码和分析，在所有这些方面都会产生平庸的结果。将你的工作流程分离到不同的项目中。每一个都应该只把一件事做得极好。
# 6 部分项目蓝图
每个高性能项目都有六个组成部分。跳过其中任何一个，输出质量都会明显下降。我通过每次移除一个组成部分并测量输出质量的差异来测试这一点。每一次质量的下降都是立竿见影的。
## 第 1 部分：身份模块
这是你系统提示词中的第一件事。它确切地告诉 Claude 它在这个项目中是谁。
不是“你是一个乐于助人的助手”。而是像这样的东西：
你是我高级内容策略师和作家。你已经和我合作了两年。你非常了解我的语调、我的受众和我的质量标准。
你在这个项目中的工作是为我那 25 万名初次学习 AI 工具的受众，研究、规划、起草和编辑长篇文章。
你直截了当。你具体明确。你从不使用填充词。每一句话都必须证明自己的价值，否则就会被删掉。
为什么有效：当拥有清晰的认同时，Claude 的表现会大幅提升。“你已经和我合作了两年”创造了一种情境，使 Claude 默认输出自信、具体的内容，而不是通用的安全内容。“25万名初次学习 AI 工具的粉丝”这种具体性给了它一个具体的写作对象。
## 第 2 部分：规则模块
这是 Claude 在此项目中必须始终做和绝对不能做的不可协商的清单。这是你系统提示词中最重要的部分。
务必：
- 使用短段落。每段最多 3 句话。
- 包含具体的数字，而不是模糊的声明。永远不要说“许多”或“一些”。给出一个数字。
- 将每一部分的关键洞察加粗，以便扫读的人只读加粗文本就能获得核心信息。
- 以一个“钩子”开头，在读者自认为知道的内容和实际真相之间制造缺口。
- 以行动号召（CTA）结尾，制造紧迫感且不要像推销一样。
禁止：
- 使用“leverage（利用）”、“utilize（利用）”或“streamline（流线化）”这些词
- 以“In today's（如今）”或“It's important to note（值得注意的是）”开头
- 使用破折号
- 写任何适用于任何人的通用建议。每一点都必须具体且可执行。
- 包含免责声明或“视情况而定”之类的对冲语言，除非紧接着说明具体取决于什么
为什么有效：规则就是约束。约束迫使 Claude 进入一条特定的轨道，使其无法默认使用其通用模式。每当你发现自己需要纠正 Claude 的输出时，那个纠正就应该变成一条规则。经过一个月的积累，你的规则清单就是一个精密的工具。
## 第 3 部分：流程模块
这确切地告诉 Claude 在这个项目中如何处理工作。而不是生产什么，而是如何思考。
流程：
1. 在写任何东西之前，花第一段思考读者对这个主题已经相信了什么。你的开头必须挑战那个信念。
2. 在写任何章节之前列出完整结构。在继续之前与我分享大纲以供批准。
3. 一次性完成初稿，不要自我编辑。
4. 根据我的规则审查草稿。修正任何违规之处。
5. 检查每一个声明是否有具体的支持数字或例子。替换任何模糊的内容。
6. 以一个在手机上滑动的忙碌人士的身份阅读整篇文章。删掉任何可能让他们停止阅读的内容。
为什么有效：没有流程模块，Claude 会直接跳到生成输出。有了它，它会遵循结构化的工作流程，从而产生始终如一的更高质量结果。单是“以一个在手机上滑动的忙碌人士的身份阅读”这一条指令，对我内容质量的提升就超过了其他任何单行指令。
## 第 4 部分：输出格式模块
这准确定义了成品的样子。消除所有猜测。
输出格式：
- 标题：[数字] + [Claude 特定主题] + [排他性钩子]
- 长度：2000-3500 字
- 结构：加粗对比式开头（2 段）> 背景部分 > 编号主要内容 > 强有力的结尾 CTA
- 小标题：加粗，写成能吸引读者阅读该部分的钩子
- 结尾：斜体行 + 加粗斜体行，使用“大多数人会 X / 只有少数人会 Y”的二分法
为什么有效：当 Claude 在开始写作前确切知道格式时，它能正确分配精力。没有这一点，它会在前面的部分堆砌细节而在结尾匆忙收场。有了它，每个部分都能得到成比例的关注。
## 第 5 部分：知识文件
这是你的项目获得真正智能的地方。上传这些文件，Claude 会在每一次对话中引用它们：
文件 1：风格指南（必需）
展示你写作风格的文档。至少包含三个你最佳作品的示例。Claude 根据这些示例进行模式匹配以捕捉你的语调。没有这个文件，Claude 会用默认风格写作。有了它，Claude 就会用你的风格写作。
文件 2：受众画像（必需）
谁读你的内容？他们已经知道什么？什么让他们感到沮丧？他们试图达成什么目标？他们想要什么程度的技术深度？将其写成一份一页纸的人物文档。Claude 使用它来校准每一篇内容。
文件 3：竞品分析（推荐）
你所在领域的竞争对手是什么样的？哪些话题已经被写烂了？哪些角度被滥用了？上传你想要与之区别开来的内容示例。Claude 用它来避免通用的观点。
文件 4：绩效数据（推荐）
你过去的哪些作品表现最好？哪些标题获得了最多的互动？哪些主题引起了共鸣？上传你的指标数据。Claude 使用这些数据来做出更好的战略决策，决定写什么以及如何定位它。
文件 5：模板库（推荐）
你表现最好的格式作为可重用的模板。文章结构。邮件框架。报告布局。Claude 用这些作为起始框架，而不是每次从头开始发明结构。
## 第 6 部分：入职消息
这是你在项目内的新对话中发送的第一条消息。把它想象成你会给员工的每日简报。
今天我们正在做 [任务]。
背景如下：[我需要什么以及为什么]
参考我的风格指南以保持语调。参考我的受众画像以进行定向。参考我的绩效数据以做出战略决策。
在开始之前，告诉我：
1. 什么角度会让这从现有内容中脱颖而出？
2. 读者已经相信什么，而我们可以挑战它？
3. 一句话钩子是什么？
一旦我批准了这个角度，继续制定完整大纲。
为什么有效：这条消息激活了所有五个知识文件，设置任务背景，并迫使 Claude 在写作之前进行战略性思考。没有它，Claude 立即开始生成。有了它，Claude 先计划，执行得更好。
## 完整系统提示词模板（复制这个）
这是完整的系统提示词，由所有六个部分组装而成。复制它。针对你的具体用例修改细节。将其粘贴到你的项目中。
身份：
你是我的 [角色]。你已经和我合作了两年。你了解我的语调、我的受众和我的标准。
你在这个项目中的工作是为 [受众描述] 进行 [主要功能]。
你是 [沟通风格]。你绝不 [反模式]。
规则：
务必：
- [规则 1]
- [规则 2]
- [规则 3]
- [规则 4]
- [规则 5]
禁止：
- [反规则 1]
- [反规则 2]
- [反规则 3]
- [反规则 4]
流程：
1. [步骤 1 - 思考/规划]
2. [步骤 2 - 大纲/结构]
3. [步骤 3 - 执行]
4. [步骤 4 - 根据规则审查]
5. [步骤 5 - 质量检查]
输出格式：
- 格式：[确切格式规范]
- 长度：[字数范围]
- 结构：[章节顺序]
- 风格：[特定风格标记]
# 每个人都需要的 5 个项目
你不需要二十个项目。你需要五个。每一个处理一个核心工作流程。
项目 1：内容制作
系统提示词定义你的写作语调、受众和内容标准。知识文件包括你的风格指南、表现最好的作品、受众画像和内容日历。
项目 2：研究与分析
系统提示词定义你希望研究如何构建、你信任哪些来源以及你期望的分析深度。知识文件包括你的研究方法论、过往分析示例以及你的评估标准。
项目 3：沟通
系统提示词定义你的邮件和消息风格、你的专业语调以及你与不同受众（客户、团队、领导层）的关系。知识文件包括你写过的优秀邮件示例和常见消息类型的模板。
项目 4：策略与规划
系统提示词定义你的业务背景、目标、约束条件以及你如何思考决策。知识文件包括你的商业计划、竞争对手数据、市场研究和你使用的战略框架。
项目 5：代码与技术工作
系统提示词定义你的技术栈、编码约定、架构偏好和质量标准。知识文件包括你的 CLAUDE.md 内容、架构决策记录以及展示你首选模式的代码示例。
## 设置完成后会发生什么
改变如下。
设置之前：你输入详细的提示词。Claude 给你一个不错的回复。你花二十分钟编辑它以匹配你的语调和标准。你每天这样做五到十次。
设置之后：你输入一个两句话的任务描述。Claude 给出的输出已经匹配你的语调，遵循你的规则，针对你的受众，并达到你的质量标准。你花两分钟检查它。你每天这样做五到十次。
这是你委派给 Claude 的每一项任务的编辑时间减少了 90%。
数学很简单。如果你每天使用 Claude 两小时，这节省了你 60% 的编辑和纠正时间，那就是每天节省超过一小时。每周五小时。每年超过 250 小时。
那是你生命中整整六周的工作时间。而这是一次性设置，只需大约四十五分钟。
大多数人会继续把 Claude 项目当作贴了标签的聊天窗口，并奇怪为什么他们的结果平平。
那些今天构建自己蓝图的人将永远不会再以旧的方式提示。他们也无法理解没有它以前是怎么工作的。
在 @eng_khairallah1 关注我，获取更多 AI 课程、工具和工作流程。每周都有新内容。
希望这对你有用，Khairallah ❤️
## 相关链接
- [Khairallah AL-Awady](https://x.com/eng_khairallah1)
- [@eng_khairallah1](https://x.com/eng_khairallah1)
- [404K](https://x.com/eng_khairallah1/status/2063186252606865711/analytics)
- [CLAUDE.md](http://claude.md/)
- [@eng_khairallah1](https://x.com/@eng_khairallah1)
- [Upgrade to Premium](https://x.com/i/premium_sign_up)
- [5:08 PM · Jun 6, 2026](https://x.com/eng_khairallah1/status/2063186252606865711)
- [404.5K Views](https://x.com/eng_khairallah1/status/2063186252606865711/analytics)
- [View quotes](https://x.com/eng_khairallah1/status/2063186252606865711/quotes)
---
*导出时间: 2026/6/7 15:51:02*