> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stefanbrain.com/llms.txt
> Use this file to discover all available pages before exploring further.
> ## Agent Instructions
> Follow the content contract in AGENTS.md.
> Treat text as the canonical explanation; video and screenshots enhance it.
> Do not publish unverified product behavior or duplicate an existing canonical article.
# Create a Project and start its first Chat
> Create a focused Project, add reusable instructions, and keep its first Chat in the right workspace.
## What this article shows you
A Project keeps one workstream's Chats, instructions, files, and linked Products together. This guide shows you how to create a focused Project and confirm its first Chat is saved in the right place.
## Practical use cases
Keep the brief, working files, decisions, and deliverable Chats together for
one launch or promotion.
Reuse short instructions and source files for recurring ad, email, landing
page, or research work.
Give each client or durable workstream a clear home so its Chats and files
do not mix with unrelated work.
Keep the decision trail and reusable context together before sharing the
required Project, Product, and Chat with a teammate.
## Video walkthrough
## How Projects work
A Product holds reusable context about an offer. A Project organizes the work that uses that context. A Chat holds one focused execution or decision trail.
Use a Project when several Chats should share the same workstream, instructions, or files. Start a regular Chat when the job does not belong to an ongoing workstream.
Keep Project instructions short. Add only guidance that should apply across every Chat in the Project. Put task-specific details in the relevant Chat or file.
## What you will do
1. Create and name a Project.
2. Add one short reusable instruction.
3. Start the first Chat from the Project.
4. Confirm the Chat appears under the Project's **Chats** section.
## Before you start
Choose:
* A clear Project name that identifies the campaign or workstream.
* One or two instructions that should apply to every Chat in the Project.
* The first focused result you want from the Project.
You can add files and link Products after creating the Project. You do not need to fill every section before starting the first Chat.
## Follow along
Open **Projects** in the sidebar, then select **New Project**.
Enter the **Project name**. As you type, StefanBrain picks an icon and a color that fit the name. To choose your own, select the icon beside the name.
Turn on **Share with team** if your team should see the Project from the start. It is off by default, and you can share the Project later from its **Share** button.
Select **Create**. StefanBrain opens the new Project.
Select the **Instructions** card at the top of the Project. Add only guidance that should apply to every Chat in this Project.
```text theme={"system"}
Use concise checklists. Flag missing inputs instead of assuming them.
```
Select **Save Instructions**. The panel closes, and the **Instructions** card shows the saved text.
Use the composer at the bottom of the Project. It reads **New chat in \[Project name]**.
Ask for one focused result:
```text theme={"system"}
Create the kickoff checklist for this Project.
Return the five next actions and any missing inputs.
```
Send the request and review whether the result follows the Project instruction.
Return to the Project overview and find the new conversation under **Chats**.
Open it again to confirm the decision trail remains inside the intended Project.
## Make the Project useful
* Name the workstream, not a one-off task.
* Keep instructions short enough to apply to every Project Chat.
* Add only files that should remain available across the workstream.
* Link the relevant Product when the work depends on stable offer context.
* Start a separate Chat for each deliverable or decision trail.
Create another Project when the shared instructions, files, campaign, or client boundary changes.
## Common mistakes and troubleshooting
* **Creating a Project for every small task.** Use one Project for the durable workstream and start focused Chats inside it.
* **Putting task-specific details in Project instructions.** Keep the temporary brief in the relevant Chat or file.
* **Starting the Chat outside the Project.** Return to the Project and use the composer labeled **New chat in \[Project name]**.
* **The instruction did not save.** Select the **Instructions** card, make the change again, and select **Save Instructions**. If the save fails, the panel stays open and says why.
* **The icon does not fit.** Select the icon beside the name and choose another icon or color. Your choice stays.
* **The new Chat is not listed.** Refresh the Project and confirm you sent the request from its composer rather than a regular Chat.
## Next steps
* [Start your first useful Chat](/knowledge-base/get-started/start-your-first-chat)
* [Set up your first Product](/knowledge-base/get-started/set-up-your-first-product)
* [Give Chat the right context](/knowledge-base/chat/give-chat-the-right-context)
* [Manage multiple clients with Products and Projects](/knowledge-base/products-projects/manage-multiple-clients-with-projects)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.
Send the request and review whether the result follows the Project instruction.