Instructions describe what the operator should consistently know about its responsibility: who the work serves, what a good result looks like, and which constraints should shape its decisions.
Use them for guidance that stays useful across tasks. Put the immediate request in the conversation and keep lengthy reference material in Files.
Write useful instructions
A short set of concrete expectations is easier to apply than a long list of overlapping rules. Include:
- Audience: who will use the result and what they already understand.
- Boundaries: choices that require discussion or actions outside the task.
- Purpose: the outcome the operator is helping you achieve.
- Standards: the evidence, tone, or quality you expect.
For a customer research specialist, you might write:
Help us understand recurring customer problems. Separate direct customer observations from your interpretation. Cite the source of each important finding. Write for a product team deciding what to investigate next.
Separate direction from methods
| Guidance | Resource |
|---|---|
| Always distinguish evidence from inference | Instructions |
| Interview transcript for a specific task | Sources |
| Permission to read a research system | Connections |
| Product background for ongoing work | Files |
| The steps for conducting a research synthesis | Skills |
Set instructions from the Composer
Use /instruction in the slash command menu to open the available instruction controls. Review the destination before saving: eligible Chat work uses Workspace guidance, while Agents and Projects have their own configuration.
For a one-time request, write the direction in the message instead. “Keep this answer under 200 words” may belong to today's task; “Write for a nontechnical customer audience” may belong in standing instructions.
Example: a customer update assistant
Start with a small set of expectations that you can check against the output:
Help our team write customer updates. Lead with what customers can now do. Use our product terminology and explain unfamiliar terms. Describe released capabilities accurately and label planned work as planned. Link to the supplied evidence for important claims. Flag missing facts instead of filling them in.
Then use the Composer to supply the current task:
Draft this week's update from the attached release notes. Focus on the three changes that matter most to account administrators.
The standing instructions establish the editorial responsibility; the message supplies this week's assignment. Add the release notes using attachments, and keep the stable terminology guide in Files.
Make guidance observable
| Vague direction | More useful direction |
|---|---|
| Be concise | Lead with the recommendation, then include the evidence needed to assess it |
| Be professional | Use direct language and explain technical terms for customers |
| Do thorough research | Link each major finding to evidence and identify unanswered questions |
| Follow our brand | Use the selected Design for visual work and the supplied glossary for terminology |
Avoid repeating the same requirement in several resources. Put the detailed procedure in a Skill and refer to its purpose in your instructions. When two instructions disagree, revise them at their owners instead of adding another rule to explain the conflict.
Refine through real work
Run a representative task, then review where the result departed from your expectations. Revise the instruction responsible for that decision. Avoid adding a permanent rule for an isolated preference that belongs in one request.
Keep passwords, tokens, and account credentials out of instructions. Text can describe a permitted workflow, but actual resource access and execution approvals remain separately enforced. Shared Workspace guidance and independently configured Agent or Project guidance retain their own scope.