# Blog Brand

Establish durable brand and voice context for cross-skill consumption.

- Repository: https://github.com/AgriciDaniel/claude-blog (2608 stars)
- Category: Marketing
- License: MIT
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add AgriciDaniel/claude-blog --skill blog-brand -g -a claude-code -y`
Codex: `npx skills add AgriciDaniel/claude-blog --skill blog-brand -g -a codex -y`
Cursor: `npx skills add AgriciDaniel/claude-blog --skill blog-brand -g -a cursor -y`
Gemini CLI: `npx skills add AgriciDaniel/claude-blog --skill blog-brand -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add AgriciDaniel/claude-blog`

## Description

Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, the blog orchestrator auto-loads these files for write, rewrite, brief, outline, calendar, and strategy workflows. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Blog Brand: Durable Editorial Context

Generates two project-root files that the blog orchestrator auto-loads for supported writing and planning commands when present:

- `BRAND.md`: who the audience is, what the brand stands for, what to never say
- `VOICE.md`: how the brand sounds, structurally and lexically

These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command.

## Why this exists

Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context it has.

`BRAND.md` and `VOICE.md` fix this: one canonical source, loaded by the `blog` orchestrator at the start of every command.

When neither file exists, behavior is unchanged from v1.7.1. Backward compatible.

## Commands

| Command | Purpose |
|---|---|
| `/blog brand init` | Interactive interview, writes BRAND.md and VOICE.md to project root |
| `/blog brand show` | Display current contents (or report missing) |
| `/blog brand update` | Re-run the interview with current values as defaults |

## Init Workflow

Run the 5-step interactive interview. Ask each step, wait for response, then proceed. If `blog-persona` JSON already exists, pre-fill voice answers from it.

### Step 1: Audience

Ask:
- **Primary audience role** (e.g. "head of marketing at a 50-500 person B2B SaaS")
- **Secondary audience** (optional)
- **Reader expertise level**: beginner / intermediate / advanced / mixed
- **Problems the reader is actively trying to solve** (3 to 5 bullets)
- **Common misconceptions the audience holds** (used to anchor information gain)

### Step 2: Positioning and Canonical Entity

The rest: https://github.com/AgriciDaniel/claude-blog/blob/HEAD/brain/.raw/sources/claude-blog-skill/skills/blog-brand/SKILL.md