Claude Projects: What Are You Trying to Achieve?
The project goal in Claude Projects says what you are trying to produce. Here is how to write one clearly, with examples, and how to keep it separate from standing instructions.
Updated 5 min read
When you create a Claude Project, Claude asks what you are trying to achieve. That question is asking for the project goal: a short statement of the outcome you want. It is not asking for style rules, constraints, or a list of tasks. Getting this right shapes every conversation in the project. A tool like fenbs keeps project goals, decisions, and reusable instructions in one place so any connected assistant starts with the same clear picture.
Many people write standing instructions in the goal field instead of a goal. The result is a project that tells Claude how to behave but not what it is actually working toward.
What the goal field is for
The goal is an outcome statement. It describes what the project is trying to produce or accomplish. A good goal answers the question: "At the end of this project, what will exist or be true that does not exist or is not true right now?"
Say you are using a Claude Project to write a book chapter. The goal might be: "A complete first draft of Chapter 3, covering the migration from paper records to digital systems, written for a general business audience." That tells Claude what it is helping to produce and who the audience is.
Compare that to: "Always use plain language. Do not use jargon. Keep paragraphs short." Those are useful instructions, but they describe how Claude should write, not what it is writing toward. They belong in the instructions field, not the goal.
Good and poor project goals: examples
A good project goal is specific enough to shape what Claude does and short enough to stay clear. It names the deliverable, the context, and usually the intended audience or use.
| Goal | What makes it work or not |
|---|---|
| A set of onboarding documents for new hires in a small software team, covering tools, processes, and first-week expectations. | Specific deliverable, clear audience, practical scope. |
| A financial model for a retail business tracking monthly revenue, costs, and cash flow over 12 months. | Clear output, defined time horizon, and scope. |
| Help me with work. | No deliverable, no audience, no scope. Claude cannot use this to make useful decisions. |
| Be helpful, concise, and professional. | This is a style instruction, not a goal. It belongs in the instructions field. |
| Research and summarize the competitive landscape for a fintech startup entering the US small business lending market. | Specific task, clear audience context, defined market. |
How to separate the goal from standing instructions
Claude Projects has separate fields for a reason. The goal shapes what the project is for. The instructions field (sometimes called custom instructions or the system prompt) shapes how Claude behaves across every conversation.
Put in the goal: what you want to produce, who it is for, and the scope. Put in the instructions: tone, format preferences, things to always or never do, constraints on sources or language. If you find yourself writing "always" or "never" in the goal field, that line probably belongs in instructions.
- Goal: the outcome, the deliverable, the audience, the scope.
- Instructions: tone, style, format preferences, things to always or never do.
- Project files: reference documents, source material, context Claude should read.
Keep project goals and reusable instructions in one place
fenbs project descriptions serve the same purpose as the Claude Projects goal field, but for any connected AI app. Add a clear goal to each project and save your standing instructions as skills. Claude, ChatGPT, Cursor and other connected apps read the same project context and the same instruction library at the start of each session.
Create a free accountFree for one person · No credit card · Works with Claude, ChatGPT, Cursor and more
When the goal is shared across a team
If multiple people are working in the same Claude Project, a clear goal matters more. Each teammate's conversations start from the same project context. A vague goal means each person's AI may interpret the project differently.
Write the goal together and agree on it as a team. "A client-facing proposal for expanding the company's warehouse operations, targeting a 40% capacity increase in the Southeast region" is a goal a team can align on. Each conversation then works toward the same output.
For guidance on sharing a project and setting up team access, the article on whether Claude Projects can be shared covers the current options. For keeping project instructions consistent over time, see how to organize Claude Projects.
How to write a goal when you are not sure what you want yet
Sometimes you start a project before you know exactly what the output will be. That is fine. A useful starting goal names the general area and the question you are trying to answer: "Research and initial recommendations on whether to expand the product into the Canadian market."
As the project progresses, you can update the goal to reflect what you have learned. "A go/no-go recommendation with supporting evidence" is more specific than the starting goal and gives Claude a clearer target. Update it when the target changes rather than letting it drift.
The goal is also useful for review. If a Claude response does not seem to be moving the project forward, check whether the goal is still accurate. A mismatch between the goal and the current stage of the work often explains why.
How to do this with fenbs
- Create a free account and add a project. The project description is your goal: one or two sentences on what you are trying to produce, who it is for, and the scope.
- Add standing instructions to Skills and prompts: tone preferences, format rules, things to always or never do.
- Connect your AI apps from Integrations. Each connected app reads the project description and your saved skills at the start of a session.
- As the project progresses, update the description to reflect the current goal. Add context notes for the current phase and any decisions made.
- When a goal or approach is agreed by the whole team, record it in Decisions and rules. Connected assistants see it at the top of their context.