# Designs

A Design gives Playbooks a visual direction to use when creating an interface, document, or other visual result. It helps successive pieces of work feel related without requiring you to restate your palette, typography, and presentation choices each time.

## Describe a visual language

Useful guidance connects visual choices to the purpose of the work. For example, a customer portal might need clear hierarchy, quiet supporting text, readable data tables, and a restrained accent color for primary actions.

Include guidance such as:

- Colors and their intended roles.
- Examples of treatments that fit the brand.
- Imagery, iconography, and representative references.
- Layout, spacing, and density.
- Typography and hierarchy.

A reference should explain the quality to preserve. “Use this layout's readable hierarchy” is more actionable than “make it look like this.”

## Create and select

1. Open Designs in the appropriate Workspace or resource configuration.
2. Create or import the guidance you have permission to use.
3. Select the Design for the supported scope where you want it applied.
4. Create a small representative result and review it against the guidance.

Adding a Design to a library does not select it. Selection identifies one authorized Design, including the choice to use none. Check the actual selection when a result appears to follow different guidance.

## Work with Designs in the Composer

Use `/design` in the [slash command menu](/docs/composer/slash-commands) to create or add a Design through the available workflow. Afterward, check the selected Design in the relevant configuration. A newly added library entry is not automatically the selected visual direction.

To refer to a particular Design in one request, type `@` and choose it from the [mention picker](/docs/composer/mentions). Explain what you want to take from it. Referencing the Design does not change the persistent selection.

## Example: a customer portal

A useful Design brief could describe the following choices:

| Element | Guidance | Purpose |
| --- | --- | --- |
| Color | Reserve the accent color for the primary action and selected state | Make the next action easy to identify |
| Data | Use clear column labels and align comparable values | Make records easy to scan |
| Hierarchy | Give each page one clear title and use short section headings | Help customers orient themselves |
| Layout | Keep navigation and content alignment consistent across pages | Make movement through the portal predictable |
| Typography | Keep supporting copy readable and use stronger weight sparingly | Separate importance without visual noise |

Then ask for a representative result:

> Create an account overview using the selected Design. Include a summary, a recent-activity table, and one primary action. Keep supporting text visually quieter than the headings.

Review both a simple page and a denser example before broadening the work. A Design that works for a welcome screen may need clearer table or form guidance for operational pages.

## Bring useful references

Use [attachments](/docs/composer/controls#attachments) for a screenshot relevant to the current task, or managed Files for background that should remain available. State what the reference demonstrates: spacing, information hierarchy, color use, or another specific quality.

For example: “Use this screenshot as a reference for the spacing between sections. Keep our selected Design's typography and colors.” This gives the Operator a concrete relationship between the reference and the standing visual guidance.

## Refine the result

Describe concrete changes: increase separation between sections, reduce visual weight, or make the primary action clearer. When the change should apply to future work, update the Design at its owner. When it belongs only to one result, keep the direction in that conversation.

A Design supplies guidance; it is not a live stylesheet that automatically rewrites existing outputs. It also does not enable tools or grant access to private brand assets. Store supporting reference documents in [Files](/docs/configuration/files), and use a [Skill](/docs/configuration/skills) when a visual task needs a repeatable production method.