Before you start
- An agreed audience and purpose for the project.
- A small set of references you can share, with notes explaining why they matter.
Connect your AI to the work
Open Stash and choose Connect your AI tools. Authorize your client, then check that it can read the intended work before asking it to edit. The connection uses MCP, a way for AI tools to read and update work in another service.
For a new publication, explicitly ask for private access. New MCP artifacts otherwise allow public editing. Your selected space is the default publishing destination, not a limit on everything the connection can access.
See the connection and handoff workflow. Client availability and workspace permissions can vary.
The workflow
- 01
Define the task and audience
Start with the audience’s situation and the result the design should support. “Busy adults looking for a low-pressure creative workshop” is more useful than “everyone interested in creativity”. Add the one action you want people to take and the information that must remain accurate.
- 02
Translate references into decisions
For each reference, describe the quality you want: generous spacing, documentary photography, clear dates or warm colour. Identify what you do not want to copy. Add source links and usage restrictions where relevant. A folder of attractive images gives an AI less direction than a few references tied to an explicit rationale.
- 03
Separate fixed rules from experiments
Use headings for approved, open and rejected. Approved might include the name, logo and audience. Open might include two palette directions. Rejected might include stock images of paint splashes. Explain the reason for each meaningful rejection so another model does not reintroduce it.
- 04
Keep the brief beside the work
Save the brief as a supported document, such as a Markdown artifact, in the same project context. When using a connected AI to publish a new brief, explicitly choose private access. Include links to the current design version. External assets still need their own permissions; putting their URLs in a brief does not make them accessible.
- 05
Update the brief after a decision
Create a new version when the direction changes. Add the decision, rationale and date, then update the link used for the next task. Ask the next AI to summarize the fixed constraints before creating anything. If it cannot access a reference, supply an appropriate export rather than letting it invent what the reference shows.
WORKED EXAMPLE
The Field Notes brand brief
Audience: adults who want a low-pressure creative habit. Promise: make something small in a friendly workshop. Tone: calm, practical and welcoming.
Starting point
“Make it modern, premium and creative” leaves nearly every design choice open.
A clearer result
“Use generous spacing and one warm accent. Make the workshop date easy to find. Avoid luxury language, stock paint splashes and invented testimonials. Keep the booking action explicit.”
Check the result
- Each reference has a stated purpose.
- Approved facts are separate from proposed ideas.
- The next task points to the current brief and design versions.
A prompt you can use
Replace the bracketed fields with your project details. Check what the AI can access before requesting changes.
Read this brand brief and [work/version link]. Summarize the audience, promise, approved facts, visual rules, open choices and rejected directions. Identify inaccessible references or contradictions. Propose [deliverable] only after making those gaps explicit. Preserve the approved facts and do not invent testimonials, metrics or brand assets.Download the brief, prompt and checklist ↓
Questions & answers
How do I hand a brand brief and references to another AI?
Share a brief with the current work link, approved decisions, references and next task. Ask the receiving AI to confirm what it can read. This transfers recorded project context, not hidden memory or the entire prior conversation.
How do I keep a shared brief current as decisions change?
Version the brief when a decision changes and record the rationale. Point new tasks to the current version. Treat one reviewed brief as authoritative instead of maintaining conflicting summaries in several chats.
How do I turn references into an actionable design brief?
For each reference, state the design quality it demonstrates and how that quality serves your audience. Translate those observations into a small set of concrete constraints and open questions.
How do I create a reusable brand brief for ChatGPT or Claude?
Use a repeatable structure: audience, goal, message, approved facts, visual rules, references, rejected directions and next task. Keep it concise enough to review and specific enough to constrain a design.
Keep in mind
- The brief does not grant access to linked external files or enforce brand consistency automatically.
Put it into practice.
Start with the example or bring a small project of your own.
Keep your brief in Stash ↗