# Configuration

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

- [**Designs** Give visual work a consistent identity.](/docs/configuration/designs)
- [**Files** Supply the background material that makes answers relevant.](/docs/configuration/files)
- [**Instructions** Set enduring goals, expectations, and constraints.](/docs/configuration/instructions)
- [**Preferences** Choose how the operator approaches work and when it asks for approval.](/docs/configuration/preferences)
- [**Skills** Turn a useful method into reusable guidance.](/docs/configuration/skills)

## External access

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

- [**Connections** Authorize accounts and make them available to the intended resource.](/docs/configuration/connections)
- [**Connectors** Find supported service operations and providers.](/docs/configuration/connectors)
- [**MCP servers** Configure external tool providers for authorized work.](/docs/configuration/mcps)

Guidance can describe how to work with a system; it cannot grant access to it. Use `/connector` or `/mcp` in the [Composer](/docs/composer/slash-commands) 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.

| Goal | Configuration |
| --- | --- |
| How a recurring kind of task should be performed | Skills |
| How the operator plans or requests approval | Preferences |
| How the result should look | Designs |
| What background information it should consult | Files |
| What external actions it can perform | [Connections](/docs/configuration/connections) |
| What it should consistently keep in mind | Instructions |

## Example: a weekly customer update

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

| Resource | Example | Review |
| --- | --- | --- |
| Design | Use the team's typography, colors, and document hierarchy | A consistent visual presentation |
| Files | Product glossary and audience background | Correct terminology and relevant explanations |
| Instructions | Write for customers; distinguish released features from planned work | Clear, accurate claims |
| Preferences | Plan first while you establish the process | An approach you can review before drafting |
| Skill | Gather changes, group them by customer benefit, then check source links | A 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](/docs/composer/slash-commands) gives you access to configuration without abandoning your draft. Type `/` and choose an available action.

| Action | Command |
| --- | --- |
| 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](/docs/composer/mentions) 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.