Create your first assistant
Pick the right first use case, define the assistant clearly, and avoid the most common setup mistakes.
Start with one job
Your first project should solve one clear problem for one clear audience.
Write the project brief first
Before adding any files, answer these questions:
- What should the assistant help people do?
- Who will use it?
- What good answer should it be able to give on day one?
- Which sources do you already trust enough to teach from?
What belongs in a first project
Start with a narrow, high-signal set of material:
- current help docs
- trusted internal policies
- a small set of good examples
- links that people already rely on
- real prompts that users actually ask
Common first-project mistakes
- uploading everything before validating one use case
- mixing unrelated teams or audiences into the same project
- using demo prompts instead of real questions
- assuming better prompting can fix weak source material