• Describe the purpose, task types, audience, and shared constraints.
• Add only stable instructions; put temporary details in the relevant request.
• Confirm whether workspace history or organization knowledge is offered as context.
• Verify the displayed memory mode and limits imposed by a shared project.
• Do not assume personal memories, other projects, or all organization data are included.

Practical guidance

Instructions have a dedicated editable field and saving can be restricted independently of member management. Keep them concise enough to remain actionable. The context-policy summary explains the resource’s library and memory boundaries; it is not an invitation to add unrestricted organization data.

Advanced tips

Organize instructions around purpose, vocabulary, required sources and review criteria. When an exception applies to one task, state it in that conversation rather than silently rewriting the shared instructions for everyone.