Group Related Work Under One Project
What it is
A Project is a container that gives a set of chats shared instructions and shared files, so every conversation inside it starts with the same context.
Why it works
Most people re-explain the same background at the top of every chat. A Project moves that background up one level: set the context once, and each chat inherits it. It also keeps a body of work together instead of scattered across your history.
When to use it
Any multi-session effort with stable context: a client account, a codebase, a book, an ongoing research topic. Anything where you'd otherwise paste the same preamble repeatedly.
When not to use it
One-off questions. Spinning up a Project for a single throwaway task is overhead with no payoff — just use a normal chat.
Prompt
In the Project's instructions field, write the durable context once:
"Context for every chat in this project:
- Product: <what it is>
- Audience: <who>
- Voice: <tone rules>
- Constraints: <what to avoid>
Assume this in every reply; don't ask me to repeat it."Example
A founder running support, marketing, and investor updates for one startup keeps three chats in a single Project. All three already know the product, stage, and tone — so 'draft an update' needs no setup.
Advanced version
Attach reference files (a style guide, an API schema, a brand brief) to the Project so answers are grounded in your source of truth, not the model's assumptions. Update the file, and every future chat uses the new version.
Common mistakes
- Dumping unrelated topics into one Project, so its shared context becomes contradictory noise.
- Duplicating durable context in every chat instead of putting it in the Project instructions.
- Forgetting attached files can go stale — update them when the underlying truth changes.