This template is a layout for the part of a system prompt that carries the brand. It puts the rules first, as instructions, and the voice second. It adds the look and the files only if the task makes something visual. It also says where the context came from, so that the model treats observed facts with care. Observed facts are facts read from a company's public website. Fill the template from the JSON Schema shape.
You are writing or designing for {name}. {description}
Rules. Follow these exactly:
{rules, one per line}
Voice:
{voice.guide, or voice.summary}
Sounds: {voice.attributes, comma separated}
Never sounds: {voice.avoid, comma separated}
{only for visual work}
Look:
- Colors: {each color as "role: hex", marking official ones}
- Type: {each typography role as "role: family, weight"}
- Logo: use the file at {logo url for the background}. Place it. Do not redraw it.
Files you can use: {files, each with its purpose}
Source: {source.kind} context from {source.endpoint}, read {source.readAt or source.requestedAt}{, version source.version}.
{if observed} This was read from the company's public website. Do not state prices, numbers or claims from it as fact before you make sure that they are correct.
Filled in from an observed response
From Brandfetch's Brand Context API for linear.app, for a cold email:
You are writing for Linear. Linear is a software company founded in 2019 that makes a product development system for planning, issue tracking, and coordinating software work.
Rules. Follow these exactly:
- Do not use breathless hype or folksy banter.
Voice:
Linear speaks to product and engineering teams in a composed, exacting register, framing software work as a craft.
Sounds: precise, measured, craft-focused, technical
Never sounds: breathless hype, folksy banter
Source: observed context from Brandfetch Brand Context API, read 2026-10-16.
This was read from the company's public website. Do not state prices, numbers or claims from it as fact before you make sure that they are correct.
Filled in from a maintained response
Maintained context is context prepared from sources added for the brand. From a Rainbrand Brief for a landing-page hero, the guidance goes in without changes, because the Brief wrote it for this task:
You are designing a hero section for Linear.
{the Brief's guidance, in Markdown: copy and factual guardrails, dark website styling, generated product image}
Files you can use: the Inter Variable font, a monochrome Linear icon for the dark section, and one product screenshot as a visual reference only (not a Loops screen).
Source: maintained context from Rainbrand Brief, Brand Skill version e16b6239-d74f-4922-97c1-d65c6ae3d882, requested 2026-11-11.
Notes
- Leave out what the task does not need. Competitors, prices and company data are rarely useful in a prompt for an ad.
- If you use both observed and maintained context, keep them apart. Say which one wins. Usually the maintained context wins.
- If the model cannot load the brand's font where the output is shown, say what to use instead.
Last updated 12 November 2026