Skip to content

Skill · Blog Writing & SEO Team

Brand & Voice Context

Build durable BRAND.md and VOICE.md context that every writing and planning playbook can draw on.

What it is

Build durable BRAND.md and VOICE.md context that every writing and planning playbook can draw on.

A skill is a written procedure an agent loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.

File
SKILL.md
Length
28 lines · 1 min read
Category
Marketing
License
MIT
Author
Brainwrite
Words
294

Paste it into any agent’s instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add the team to Brainwrite and it arrives switched on.

Use it

Use this skill in Brainwrite.

  1. 1

    Add the Blog Writing & SEO Team

    Its agents carry this skill. You preview every agent and skill first; skills arrive switched on and routines paused.

    Install in Brainwrite →
  2. 2

    Brief your Chief of Staff

    “Use the Brand & Voice Context skill for this: [describe the job]. Show me the plan first, and send, post or change nothing.”

  3. 3

    Approve what matters

    The agent follows the skill and brings the result back. Anything that sends, posts or changes data waits for your approval in Ask mode.

    How approvals work →

Use this when

blog brand, create brand context, brand voice doc, establish editorial brand, brand guidelines for blog.

Process

Interview the user once, and store the result so every future strategy, brief, calendar, write, and rewrite job can start from the same context instead of re-deriving it.

Audience: primary and (optional) secondary audience role, reader expertise level, 3-5 active problems the reader is trying to solve, and common misconceptions worth correcting.

Positioning: official entity name, homepage URL, logo, official social/profile links, one-sentence mission, the brand's distinctive (even contrarian) point of view, explicit anti-positioning ("what we are NOT"), and the top 3 competitors each with a one-line differentiator.

Editorial rules: 3-7 always-do rules (e.g. "cite primary sources only"), 3-7 never-do rules (e.g. "no clickbait titles"), taboo phrases specific to this brand, and any required disclosures (affiliate, AI-content, conflict-of-interest).

Topic boundaries: what's fully in scope (core pillars), partially in scope (adjacent, only with an original angle), and explicitly out of scope.

Voice: pronoun stance (first/second/third-person or mixed), contraction policy, a hard sentence-length ceiling, a paragraph-length ceiling (default 150 words), headline patterns to favor and to avoid, and the summary-box label. Pre-fill these from an existing writing-persona profile when one exists; this file mirrors the persona's tone fingerprint in prose rather than duplicating it as the source of truth.

Write two files at the project root: BRAND.md (audience, positioning, editorial rules, topic scope) and VOICE.md (pronoun stance, lexical rules, headline patterns, voice fingerprint, readability target). When present, every writing and planning playbook should treat them as auto-loaded context. When absent, behavior is unchanged; these are opt-in, never something to demand before writing.

To update, re-run the interview with current values as defaults and let the user accept or change each one, then overwrite both files.

Put this skill to work.

Download Brainwrite, add the team that carries it, and tell your Chief of Staff what needs doing.

macOS today. Windows and Linux are coming soon.