Skip to content

Playbooks becomes more useful when it understands how you work. You can give it standing direction, a visual language, methods worth repeating, and reference material it can consult. Each serves a different purpose, so you can change one without rewriting everything else.

Guidance

External access

Configure the capabilities that connect work to other systems. Account authorization, resource assignment, and provider selection remain separate decisions.

Guidance can describe how to work with a system; it cannot grant access to it. Use /connector or /mcp in the Composer to enter the available setup workflow.

Choose the right resource

Start with the part of the work you want to improve. Keep each resource responsible for one kind of guidance so future changes have a clear home.

GoalConfiguration
How a recurring kind of task should be performedSkills
How the operator plans or requests approvalPreferences
How the result should lookDesigns
What background information it should consultFiles
What external actions it can performConnections
What it should consistently keep in mindInstructions

Example: a weekly customer update

Start with a recurring result you can evaluate. For a weekly customer update, configure each resource around one responsibility:

ResourceExampleReview
DesignUse the team's typography, colors, and document hierarchyA consistent visual presentation
FilesProduct glossary and audience backgroundCorrect terminology and relevant explanations
InstructionsWrite for customers; distinguish released features from planned workClear, accurate claims
PreferencesPlan first while you establish the processAn approach you can review before drafting
SkillGather changes, group them by customer benefit, then check source linksA repeatable editorial process

Supply this week's notes as a conversation attachment. They are task input, while the glossary remains useful across weeks. Once the process works, refine the standing guidance only when a lesson should apply to future updates.

Configure from the Composer

The Composer command menu gives you access to configuration without abandoning your draft. Type / and choose an available action.

ActionCommand
Add a repeatable method/skill
Add managed background material/file
Add visual guidance/design
Choose a model/model
Review approval choices/permission
Review planning choices/plan
Review standing direction/instruction
Supply input for one request/attach

Check the destination shown before saving. Creating a resource, selecting a Design, and inserting a mention are separate decisions. A mention makes a request specific; it does not silently change lasting configuration.

Choose the right scope

Chats use eligible Workspace configuration. Agents have their own configuration; Projects configure development work. A resource available in one scope is not automatically available everywhere. Edit shared material at its owner, and check which resource you are configuring before saving.

Start with the smallest amount of guidance that improves a real task. Review the result, identify what was missing, and refine that resource. Instructions and reference content do not grant tool permissions.