How Creative Directors Share Visual Direction With Claude or ChatGPT (2026): One Board the Whole Team Reads

Key Takeaways

• Storyflow is the best place to share a campaign's visual direction with the team in 2026: one board holds the territory, do and don't pairs, palette, type, tiered references and rationale, and every teammate's Claude or ChatGPT reads that board through the Storyflow connector instead of a forwarded summary.
• Direction now has two readers. The team looks at the pictures; their assistants read the words. A reference with no caption is invisible to the second reader, so every image needs one written line.
• Sort references into three tiers (make this, borrow one thing, not this). Tiers answer the question a team asks most: how literally should we take this picture?
• Write the rationale as a short document on the board, not as speaker notes in a deck. It is the part an assistant uses to answer a question you did not anticipate.
• Each discipline asks its own assistant for its own brief from the same board: layout rules for the designer, light and lens for the photographer, grade and pacing for the editor. One source, three translations.
• Figma, Miro and Frontify each have their own MCP server and each beats Storyflow at one thing: components, workshops and governed brand assets. We found no connector for Milanote.
• Storyflow is paid-only during early access, from $7.99 a month billed annually. Its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now.

Why Visual Direction Now Has Two Readers

For years the handoff looked the same. You built a deck, presented it at the kickoff, exported a PDF and trusted the team to remember what you said over slide 14. The deck held the pictures. Your voice held the reasons. The two separated the moment the meeting ended.

Something changed in how teams work, and it changes how direction should be written. The designer drafts a layout brief in Claude before opening a file. The photographer asks ChatGPT to turn a moodboard into a lighting plan. The editor asks an assistant for a grade description to send the colourist. Each of them now gives your direction to a second reader before making anything, and that reader only knows what it was given.

The team paraphrases you to their assistant

If the direction lives in a PDF on a drive, each person describes it to their assistant from memory: "the look is warm, kind of cinematic, blue and amber." Three people give three paraphrases, and three assistants write three confident briefs that disagree. Nobody did anything wrong. The direction was simply copied by hand, once per person, with losses each time.

The assistant reads words, not taste

A photographer looks at a reference and knows you mean the window light, not the wardrobe. An assistant reading a board through a connector works from what is written on it: the notes, the headings, the tables, the documents and the names on the swatches. Treat an uncaptioned picture as something the assistant cannot use. The caption is the direction; the picture is the proof.

Written direction is what survives week three

The same rule held before assistants existed. A producer cutting a shot for budget, or a freelancer who joined after the kickoff, needs the reason behind a rule to decide well without you. Writing for the assistant forces you to write what the humans needed all along. That is why this post treats the connector as a discipline, not a gadget: it punishes vague direction immediately, in the first brief it writes.

For the full kickoff process (agenda, checkpoints, handling drift), read how a creative director shares campaign visual direction with the team. This post covers the part that is new: building a direction board that people and assistants both read correctly.

What Goes on a Direction Board That an Assistant Can Read

A direction board has six parts. Each one is listed below with what it is for, how much of it you need, and what has to be written down so that a second reader gets it right.

The territory: one line and three sentences

The territory is the name of the visual world and the idea behind it. Write it as one line (five to nine words) and three sentences: what the audience should feel, what the pictures always contain, and what they never contain. Put it in a heading and a note at the top left of the board, because both people and assistants read from the top.

A weak territory is a list of adjectives: warm, premium, authentic. A usable one makes a choice: "Blue hour outside, warm windows inside." You can check a frame against the second. You cannot check anything against the first.

Do and don't pairs

A pair is two pictures of the same subject, one right and one wrong, with a sentence under each. Six to eight pairs cover most campaigns: light, crop, casting, styling, colour, type treatment, product scale and retouching.

The sentence matters more than the picture. "Do: one practical light source in frame, faces lit from the side" gives a photographer a setup. "Don't: flat overhead light, every face evenly exposed" tells an editor which takes to drop. Written as a two-column table beside the pictures, the pairs become the part of the board an assistant can quote directly, because a table states a rule as text.

The palette, with values and jobs

A palette is four to six colours, each with a name, a hex value and a job. The job is what stops a palette from being decoration: which colour is the field, which is the accent, which is reserved for the product, and how much of the frame each may take.

Storyflow's connector has a tool for this. Ask the assistant for a colour palette and it places a grid of swatches on the board, each showing its colour, the name you gave it and its hex and RGB values. Add a small table next to it with the jobs and the proportions, so the rule exists as text as well as colour.

Type rules

Type direction for a campaign is rarely a full system. It is usually four decisions: the headline face and weight, the supporting face, the case and tracking, and where type may sit on a picture. Put a specimen image on the board (a real headline set in the real face) and write the four decisions in a note beside it.

Be plain about what the board is for here. It carries the rules and the specimen. The font files, the styles and the templates belong in the design tool, which is why Figma sits in this post's comparison.

Reference tiers

Most moodboards fail on one question: how literally should the team take each picture? Tiers answer it before anyone asks.

Build each tier as its own section on the board with the tier name as its title. A reader, human or assistant, then knows the weight of a picture from where it sits. Fifteen to twenty references in total is enough. A board of sixty pictures has no direction in it, only research.

The written rationale

The rationale is a document of 250 to 400 words that sits on the board. It answers five questions: what the brief asked for, what the audience already believes, why this territory answers that, what was considered and rejected, and what is fixed versus open.

That last question earns its place every week of production. "Fixed: single warm light source, blue ambient, no faces to camera. Open: locations, wardrobe colour within the palette, aspect ratios" lets a photographer improvise inside the direction instead of around it. It is also the paragraph an assistant leans on when a teammate asks something the board does not literally answer.

Notes by discipline

Finish with a short table: one row per discipline, with the three things that person must get right. Three is the limit. It forces you to rank, and it gives every assistant a clear place to start when a teammate asks "what matters most for me?"

How We Compared the Places to Hold the Direction

We scored five tools on one job: holding a campaign's visual direction so that a mixed team (in-house and freelance, each using their own assistant) works from the same source. Features and prices come from each vendor's own pages, checked on 10 October 2026 and linked in the reviews. The scores are our judgement against the weighting below, not a lab test.

Two notes on the weighting. First, it favours tools with a connector, because the target of this post is a team that already works with assistants. If yours does not, read the best tools for creative directors to share visual direction, which weights the kickoff and the handoff instead. Second, governance carries only 10% because a campaign lasts weeks. For a brand system that lasts years, governance should weigh far more, and Frontify would rank higher.

Comparison Table: Where to Hold Campaign Visual Direction When the Team Uses Claude or ChatGPT

How the scores add up

Each criterion is marked out of 10, multiplied by its weight and summed. The marks are our reading of the vendor pages linked in the reviews.

Storyflow loses marks where you would expect: it is paid-only today (access), it has no components or variables (into the making) and no governed approvals (governance). Milanote scores well on the two criteria that do not involve an assistant and zero on the two that do, which is the whole reason it sits last on this list and near the top of lists that ignore connectors.

How to Share Visual Direction With Claude or ChatGPT, Step by Step

The nine steps below take a locked brief to a direction board the team's assistants read. Plan on a working day spread across two or three sittings; the time goes into choosing and captioning references, which no assistant can do for you.

Step 1: Connect Storyflow to your own assistant first

Connect the tool before you build, so the assistant does the layout work.

In Claude: open Customize, then Connectors, then Add, then Add custom connector. Name it Storyflow, paste the address https://mcp.storyflow.so/mcp, choose Continue, then Sign in now, then Add, and sign in to Storyflow. Claude Free allows one custom connector.

In ChatGPT (web): you need ChatGPT Plus or above with Developer mode. Open Settings, then Security and login, and turn Developer mode on (on Business and Enterprise an admin does this). Go to chatgpt.com/plugins, press the plus button, name it Storyflow, choose Public endpoint, paste the same address, create it and sign in.

At sign-in you choose which projects the connection may use and whether it may make changes. For your own build, pick the campaign project and allow changes. The full walkthrough is in the help article on connecting AI assistants, with separate guides for Claude and ChatGPT.

Step 2: Write the territory before you collect anything

Paste the client's brief into the chat (the real document, not your summary) and work on the territory there. Ask for ten candidate lines, reject nine, rewrite the tenth yourself. Then write the three sentences: the feeling, what is always in frame, what is never in frame.

Do this before you open a single reference site. A territory written after the references is a description of what you happened to find.

Step 3: Have the assistant lay out the empty board

Ask the assistant to build the structure with nothing in it yet: a heading and note for the territory, three sections named Tier 1: Make this, Tier 2: Borrow one thing and Tier 3: Not this, a do and don't table with two columns, a palette area, a type area, a rationale document and a table of notes by discipline.

The connector builds a section in one call (a titled wall with its cards in order), so the skeleton appears live if you have the board open. Starting from an empty structure matters. It shows you the gaps: an empty Tier 3 is a direction with no edges.

Step 4: Put the references on the board, sorted by tier

Now collect. Pull wide (forty to sixty pictures), cut to fifteen or twenty, and place each one in its tier.

Three routes get pictures onto the board. Drag them in yourself in the browser, which is the fastest route for a folder of saved references. Give the assistant image addresses and it places copies on the board. Or ask the assistant for an upload link: a picture you attach in the chat does not reach Storyflow, so the connector hands you a link to upload it to the board instead.

Two honest limits. The connector does not generate images; image generation is the built-in Storyflow agent, on the Pro and Max plans. And check the usage rights on every reference before the board goes to a client; this guide to commercial use of moodboard images covers what a reference board may and may not contain.

Step 5: Caption every reference in one line

This is the step that makes the board work for both readers. Under each picture, write one line in a fixed pattern.

• Tier 1: "Make this: the single warm source at the window, blue everywhere else."
• Tier 2: "Borrow: the crop (subject in the lower third). Ignore: the colour."
• Tier 3: "Not this: flat daylight, everyone smiling at camera. Tempting because it reads as friendly."

You write these, not the assistant. It can tidy your wording, but only you know what you saw in the frame. Allow two minutes a picture, so about forty minutes for twenty references. Nothing else in the build pays back as much.

Step 6: Turn the look into rules

With the references captioned, write the rules they imply. Ask the assistant to place the palette as swatches with the names and hex values you give it, then to add a table with each colour's job and its share of the frame. Fill in the do and don't table, one row per subject. Write the four type decisions beside the specimen.

Ask the assistant to draft the rules from your captions, then correct them. It is quick at turning "single warm source at the window" across five captions into "Light: one practical source in frame, key from the side, no fill above half a stop". You decide whether half a stop is right.

Step 7: Write the rationale as a document on the board

Have the assistant draft the rationale document from the brief and the board: what was asked, what the audience believes, why this territory, what was rejected, what is fixed and what is open. Then rewrite the rejected routes and the fixed and open lists by hand. Those two parts carry your judgement, and they are what the team will ask about.

Keep it under 400 words. A rationale nobody finishes is a rationale nobody uses.

Step 8: Share the board and have each person connect their own assistant

Invite the team to the board. Anyone a paid member invites joins free. Each person then connects their own Claude or ChatGPT to their own Storyflow account, and chooses at sign-in which projects the assistant may reach and whether it may make changes.

Recommend read-only to the team. The direction is yours; they need to read it, not edit it through a chat. Two things to tell them up front: a free account gets 25 connector actions a week (each read or change counts as one, and the count resets on Monday UTC), and a connection expires after 30 days and needs a fresh sign-in. Paid plans have no connector limit.

For the client and anyone who only needs to look, send the view-only link. It opens with no account; they sign in to comment. For the kickoff itself, present the board fullscreen in presentation mode.

Step 9: Each discipline asks for its own brief from the same board

Now the new part pays off. The designer opens Claude and asks for a layout brief from the direction board. The photographer asks ChatGPT for a lighting and lens plan. The editor asks for grade and pacing notes. Each assistant reads the same territory, the same tiers, the same rules and the same rationale, and translates them for one craft.

The briefs should differ in vocabulary and agree in substance. When two of them disagree, do not read it as a fault in an assistant. The board is unclear at that point, and you fix the board.

When you change the direction, change it on the board, then tell the team. Anyone can ask their assistant what changed on the board in the last day, the last week or the last month, and who changed it.

The Five Tools, Reviewed for This Job

1. Storyflow

Storyflow is a visual project planning workspace for creative work: an infinite canvas board that holds notes, tables, documents, images, moodboards, storyboards, mind maps, kanban, charts and slide decks, with an AI agent that reads the board and builds on it. For this job the relevant part is its MCP server, launched in October 2026. It works with any assistant that can add a remote MCP server, including Claude, ChatGPT, Gemini and Grok.

Through the connector an assistant reads boards, notes, documents and files, and what changed on a board and who changed it. It builds notes, sections, tables, documents, colour palettes, diagrams and slide decks, placed on the board and appearing live while you watch. That combination is why it ranks first here: the direction and its rationale are one object, the assistant can lay it out and keep it current, and every teammate's assistant reads the same object under that teammate's own permissions.

It also carries the direction forward. The same project can hold the brief, the shot list and the deck, so the direction board does not get left behind when production starts. Inside the app, the built-in agent has moodboard and brand moodboard workflows and reads the current board plus up to five attached documents and up to three other boards.

Where it is strongest: pictures, rules and written rationale on one board; a connector that reads and builds; view-only links that open with no account; invited collaborators join free.

Where it is weaker: the connector does not read comment threads and does not generate images; it adds and edits, while removing elements from a board is done by you. There are no component libraries or design styles, no approve button or versioned approvals, and no desktop or mobile app or offline mode. It is browser only.

Price: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly) with AI image generation, Max $39 ($49 monthly) with a team workspace, roles and permissions. Paid-only during early access; a Free plan launches before the end of 2026. The connector runs on your assistant's own model, so it does not spend Storyflow AI credits. See pricing.

2. Figma

Figma is where direction becomes the thing designers build from: variables, components, key visual layouts and templates. If your campaign's hardest problem is forty layouts staying consistent across formats, the direction should end up here whatever tool it started in.

Figma has its own MCP server. Per Figma's guide, the remote server is available on all seats and plans, pulls design context (including variables, components and layout data) into the assistant, reads FigJam content, and lets an assistant write to the canvas in Figma Design and FigJam. The guide also lists Figma Slides as a supported file type, but its write-to-canvas section names only Design and FigJam, so confirm Slides for yourself. Figma's MCP catalog lists both Claude and ChatGPT as supported clients with read and write access.

Where it beats Storyflow: design variables and components are real, enforceable objects; a designer's assistant reads the actual tokens instead of a description of them.

Where it is weaker for this job: the server is designed around design files and code generation, so a photographer or editor gets less from it. A written rationale and a tiered reference wall can live in FigJam, but they sit apart from the design file, and non-designers on the team tend not to open either.

Price: per Figma's pricing page, Starter is free, and Professional lists a Full seat at $16 a month, a Dev seat at $12 and a Collab seat at $3. Organization lists a Full seat at $55 a month billed annually. On paid plans others can view and comment on your files without an extra seat. The page also notes that MCP rate limits vary by seat and plan (it lists 200 tool calls a day on Professional), so check yours before a busy week.

3. Miro

Miro is the strongest pick when the team already lives there. If the strategy workshop, the customer research and the campaign plan are Miro boards, the direction is better off beside them than in a tool nobody opens.

Miro's MCP server works on all Miro plans, including free teams, and lists Claude, ChatGPT, Claude Code, Cursor, Gemini CLI and VS Code as clients. Its tool list covers searching and reading board content, reading image data, creating items, and reading, replying to and resolving comments.

Where it beats Storyflow: comments. Miro's connector reads comment threads, and Storyflow's does not. If your review culture runs on comments pinned to frames, an assistant can summarise them in Miro. Miro is also stronger at facilitation for a large group.

Where it is weaker for this job: every member is a paid seat on the paid plans, and the connector has daily tool-call limits by plan: 100 on Free, 500 on Starter, 2,000 on Business and 10,000 on Enterprise, reset at 00:00 UTC.

Price: per Miro's pricing page, Free includes 3 editable boards, Starter is $8 a member a month billed yearly and Business is $20 a member a month billed yearly.

4. Frontify

Frontify is a brand portal: the governed home for guidelines, logos, approved assets and templates. It answers a different question from the other four. A direction board says "this is the look for this campaign." Frontify says "this is the brand, for everyone, for years."

Frontify has an MCP server too. Its help article describes 52 tools grouped into packs, a default discovery pack of 25 read-only tools, and an official Claude connector; account admins can enable the server at no additional cost. The article warns that write-capable packs can change assets and metadata, and advises starting with the read-only pack.

Where it beats Storyflow: authority. When an assistant pulls the logo or the tone of voice rules from Frontify, it gets the approved version, with the permissions and history a brand team needs.

Where it is weaker for this job: a portal is where a direction lands once it is approved, not where you explore it. Tier 3 references and rejected routes have no natural home there.

Price: quote-based. Frontify's pricing page says it does not show fixed prices and bases packages on monthly active users.

The practical pattern for a brand that has Frontify: build and argue the campaign direction on a board, then publish the approved rules to the portal.

5. Milanote

Milanote is a well-loved moodboard tool, and for a director who builds direction alone and presents it in person it remains a pleasure to use. Boards look good with little effort, and a read-only link opens with no account. Per Milanote's sharing guide, commenters need a free account, which is the same rule as Storyflow.

For this job it ranks fifth for one reason: we found no connector. Milanote's plans page lists no AI features and no MCP server, so an assistant cannot read a Milanote board. The team is back to paraphrasing.

Where it beats Storyflow: a real free tier today (100 notes, images or links and 10 file uploads) and a board-building feel many art directors prefer.

Price: free tier as above; $9.99 a person a month billed annually ($12.50 monthly); flat team pricing from $49 a month billed annually.

A Worked Example: The Direction for a Night-Train Campaign

This is an illustrative example. The brand, the team and the figures are invented to show the method; none of the counts or timings below were measured.

The brief and the territory

Nordvale Sleeper is a fictional overnight rail operator launching a winter campaign for its northern route. The brief asks for bookings from people who currently fly: the business problem is that the train is seen as slow. The creative director's territory line: "Blue hour outside, warm windows inside."

The three sentences beneath it read as follows. The audience should feel that the journey is the first night of the trip, not the cost of it. Every frame contains one warm interior light and a cold blue exterior. No frame contains a station clock, a departure board or a face looking at the camera.

What went on the board

In this example the director asks Claude to lay out the skeleton, then fills it by hand.

The palette and its jobs

The assistant placed the swatches with one request. The jobs and shares went into the table by hand, because they are decisions.

Three assistants, three briefs

Each teammate connected their own assistant read-only and asked for a brief from the board.

The designer asked Claude for layout rules. The reply led with type placement (headline in Wool Cream on the darkest third of the frame, never over the warm source), the 60, 15, 15, 10 colour split, and a warning from Tier 3 against daylight imagery in any format.

The photographer asked ChatGPT for a lighting and lens plan for a two-day shoot in a real cabin. The reply led with one practical lamp as key, blue ambient from the window, side light on faces, and a list of what the fixed and open paragraph allowed: any wardrobe inside the palette, any cabin, no faces to camera.

The editor asked Claude for grade and pacing notes. The reply described a cool base with a protected amber range, long takes, and no cuts faster than the Tier 2 title card reference implied.

In this example the three briefs use different words and reach the same picture, with one disagreement, about faces: the photographer's brief said "no faces to camera" and the designer's said "no faces". The board's do and don't row read "Casting: no eye contact", which is ambiguous. The fix is to the board, not the briefs: the director rewrites the row as "Faces may appear in profile or from behind, never looking at the lens", and the next brief either assistant writes has one rule to quote.

The change in week two

The client asked for one daytime frame for a partner placement. The director added a Tier 2 reference captioned "Borrow: overcast noon, lamp still on. Ignore: the open landscape", added a line to the fixed and open paragraph, and told the team to ask their assistants what changed on the board in the last week. Nobody needed a second kickoff.

Prompts You Can Copy

Replace the bracketed parts. These work in Claude and ChatGPT once Storyflow is connected. The first five are for the creative director; the rest are for the team.

A note on the "check a draft" prompt: describe the draft in words, or put the draft on the board first. A picture you attach in the chat does not reach Storyflow.

One Board, Four Briefs: What Each Discipline Should Ask For

The value of a shared source shows in how differently each craft reads it. Use this table at the kickoff so each person knows what to ask their assistant for, and what to check by eye.

The last column matters. An assistant working from the board's text can tell a photographer what you wrote about the light. It should not be asked whether a contact sheet matches the references. That stays a job for trained eyes, and for you.

What It Costs to Share Direction This Way

The table prices an illustrative team of five: a creative director, an in-house designer, a freelance photographer, a freelance editor and a producer. Assistant subscriptions are separate and not included; each person uses their own Claude or ChatGPT plan.

Is 25 actions a week enough for a freelancer? Every read counts as one action. If a photographer's brief takes about four reads (a board summary, the board's elements, the rationale document and a check on changes), a free collaborator can ask about six times in a week before the count resets on Monday UTC. That covers a check before each shoot day, not a running conversation with the board. That four is our estimate, not a measured figure; a large board or a long session will use more. If one freelancer hits the limit, a Plus plan removes it for that person.

Storyflow has no per-seat pricing, which is why the first row is small. Do not read it as the lowest possible cost: Milanote and Miro both have free tiers today, and Storyflow does not.

Decision Rules: Which Tool Holds the Direction

• If the team uses Claude or ChatGPT and includes freelancers across photo, video and design, hold the direction on a Storyflow board and have each person connect read-only.
• If the campaign is mostly layouts (out-of-home, display, social templates) and the team is designers, put the approved rules into Figma as variables and components, and keep the references and rationale on a board that links to the file.
• If the brand already has Frontify, build and argue the direction on a board, then publish the approved rules to the portal. Do not explore inside the portal.
• If the whole company runs on Miro and reviews by comment, hold the direction in Miro and accept per-member pricing.
• If you work alone, present in person and nobody on the team uses an assistant, Milanote's free tier is a reasonable place to start.
• If the client's security team will not approve a connector, skip the assistants entirely: share the view-only link and present the board. The six parts work without AI.

Common Mistakes When Assistants Read Your Direction

Leaving references uncaptioned

The most common failure and the easiest to fix. Twenty pictures with no words give an assistant nothing to quote and give a freelancer twenty guesses. One line per picture, in the fixed pattern for its tier.

Putting the rationale in the meeting instead of on the board

If the reasons live only in what you said at the kickoff, they are gone for anyone who joined later and for every assistant. Write the document. If you prefer to talk it through first, talk to your assistant, then cut the draft to 400 words.

Letting the assistant choose the references

An assistant can find pictures and place them. It cannot have your taste. A board whose references were chosen by a model reads as average because it is: the mean of what the web associates with your adjectives. Use the assistant for layout, rules and drafts, and choose the pictures yourself.

Giving the team edit access through their assistants

When five assistants can write to the direction board, it stops being a direction. Recommend read-only at sign-in. Changes go through you, on the board, with a note to the team.

Treating the assistant's brief as the direction

A teammate's brief is a translation. When it conflicts with the board, the board wins; when the board is ambiguous, you fix the board. Ask each person to keep the prompt "quote the board for each rule" so you can see what the brief was built from.

Skipping Tier 3

Directors leave out the "not this" tier because collecting bad work feels unkind or unnecessary. It is the tier that prevents the most rework. Three or four frames with a reason each are enough.

Forgetting that connections expire

A Storyflow connection lasts 30 days. On a ten-week campaign, each person will need to sign in again at least twice. Mention it at the kickoff so nobody concludes in week five that the board has vanished.

Sharing sensitive work without checking the client's AI policy

Reading a board through a connector sends its text to the assistant's vendor. Some client contracts restrict that. Check before you connect a project that holds unreleased product shots or embargoed dates; this guide to connector permissions covers what each permission allows and how to disconnect.

When Storyflow Is Not the Right Choice

Storyflow ranks first on this post's weighting, and there are clear cases where another tool is the better answer.

• You need a free tool today. Storyflow is paid-only during early access. Its Free plan launches before the end of 2026. Until then, Miro's free plan or Milanote's free tier costs nothing, and an invited collaborator on someone else's Storyflow board joins free.
• The direction must be enforced in design files. Storyflow has no variables, styles or components. For a campaign of forty layouts, the rules belong in Figma.
• You need a governed brand system. Storyflow has no asset approvals, no versioned guidelines and no approve button. That is Frontify's job.
• Your review runs on comment threads an assistant should read. Storyflow's connector does not read comments. Miro's does.
• The team works offline or on location without a connection. Storyflow is browser only, with no desktop or mobile app and no offline mode. Build a deck of the essentials and export it as a PDF before a remote shoot.
• You want the assistant to generate the references. The connector does not generate images. The built-in agent does on Pro and Max, and generated frames should be labelled as comps, not presented as references.
• Nobody on the team uses an assistant. The connector criterion carries 25% of this ranking. Without it the gap to Figma and Miro narrows, and the tool your team already opens every day is usually the right one.

A Direction Board Template You Can Copy

Build the board in this order, top left to bottom right. Each row is one part; the last column is the test to run before you share it.

Then run the test prompt from the table above: ask your own assistant to read the board as a freelancer who missed the kickoff and list the questions it still has. Fix the board until the list is short. Storyflow also has pages on building an art direction board, a brand moodboard and a creative direction deck.

The Bottom Line

Sharing visual direction has always meant getting your reasons to travel with your pictures. What changed in 2026 is that the team now hands your direction to an assistant before making anything, so the reasons have to be written where that assistant can read them.

Build one direction board: a territory you can reject frames with, three tiers of captioned references, do and don't pairs, a palette with jobs, four type decisions and a rationale under 400 words. Hold it on Storyflow, where each teammate's Claude or ChatGPT reads that same board through the connector, and send the approved rules onward to Figma or Frontify when the campaign needs components or governance. Then fix the board, not the briefs, every time two people disagree.