Collections

A collection is a brief in the making

You might have hundreds of references because you like many kinds of design. A Taste Docs collection answers a narrower question: how should this documentation experience feel and work? Onboarding, Settings, and New Homepage collections each hold a different intention.

Keep the references that help make a decision. Five examples with clear reasons can give an agent more direction than fifty unexplained screenshots.

Build a focused collection

1. Open Saves and create a collection. Give it a specific name and describe the intended project or surface.
2. Save designs into that collection from the save flow. Choose examples that contribute different ideas.
3. Use Upload from the collection to add relevant screenshots as inspiration. Review their visibility.
4. Open the references and add notes: what works, what to borrow, and what to avoid.
5. Revisit the set as the work changes. Remove references that no longer support the direction; removing an item from the collection is different from deleting the original design.

Use the collection with an agent

Ask the agent to find the collection by name and confirm the matching collection before using it. If names are ambiguous, provide its link or ask it to show the available matches. Ask for images and annotations, not only a summary.

When a design brief helps

The collection’s AI brief brings observations and design direction together. A fresh generation can use an AI generation credit; an unchanged cached brief can be reused. If you only need to inspect references, ask for the collection itself when your connection exposes that capability.

Keep it useful as the project changes

Add a reference when a new problem appears, and update notes when a decision changes. Tell the agent to read the collection again; context already loaded into a conversation does not refresh itself.

• Add useful annotations
• Understand sharing and access