Shared Context Setup
Create a centralized context folder that all skills and agents reference for consistent output.
Modes
brand — Voice profile, tone, banned words, audience personas, content pillars
domain — Project conventions, terminology glossary, domain knowledge
full (default) — Both brand and domain
Process
Step 1: Assess What Exists
- Check for
.claude/shared-context/, .claude/brand-context/, or existing voice/persona files
- Read CLAUDE.md, README, any marketing or docs directories
- Report what's found and what's missing
Step 2: Interview
Brand questions (skip in domain mode):
- Brand personality in 3 adjectives?
- Primary audience: job title, pain points, language they use?
- Words/phrases to NEVER use? (AI artifacts, competitor names, off-brand jargon)
- Platform differences? (LinkedIn vs docs vs email vs social)
- Share 1-2 examples of content you're proud of
Domain questions (skip in brand mode):
- Project domain? (fintech, healthcare, e-commerce, etc.)
- Project-specific terminology that's often misused?
- Non-obvious conventions from reading the code?
- Who consumes this project's output? (engineers, end users, both)
Step 3: Create Structure
.claude/shared-context/
├── README.md # What this folder is, how to use it
├── brand/
│ ├── voice-profile.md # Tone, banned words, platform rules, examples
│ ├── audience-personas.md # ICP with pain points and values
│ └── content-pillars.md # Core topics (content projects only)
└── domain/
├── conventions.md # Project-specific rules and gotchas
└── glossary.md # Domain terminology
CHECKPOINT: Show each document before writing. User confirms or edits.
Step 4: Wire Into Skills
- Scan
.claude/skills/ for writing/content skills
- Offer to add
Read .claude/shared-context/brand/voice-profile.md before generating content to relevant skills
Step 5: Register in CLAUDE.md
Add:
## Shared Context
Brand voice, audience personas, and domain conventions: `.claude/shared-context/`
Content-generating skills should read relevant files before producing output.
1---2name: shared-context3description: Set up a centralized shared context folder for your project with brand voice, audience personas, and domain knowledge. Use when the user says "set up brand context", "create voice profile", "define our audience", "shared context", "ICP setup", or wants consistent non-generic output across skills.4---56# Shared Context Setup78Create a centralized context folder that all skills and agents reference for consistent output.910## Modes11- **`brand`** — Voice profile, tone, banned words, audience personas, content pillars12- **`domain`** — Project conventions, terminology glossary, domain knowledge13- **`full`** (default) — Both brand and domain1415## Process1617### Step 1: Assess What Exists18- Check for `.claude/shared-context/`, `.claude/brand-context/`, or existing voice/persona files19- Read CLAUDE.md, README, any marketing or docs directories20- Report what's found and what's missing2122### Step 2: Interview2324**Brand questions** (skip in domain mode):251. Brand personality in 3 adjectives?262. Primary audience: job title, pain points, language they use?273. Words/phrases to NEVER use? (AI artifacts, competitor names, off-brand jargon)284. Platform differences? (LinkedIn vs docs vs email vs social)295. Share 1-2 examples of content you're proud of3031**Domain questions** (skip in brand mode):321. Project domain? (fintech, healthcare, e-commerce, etc.)332. Project-specific terminology that's often misused?343. Non-obvious conventions from reading the code?354. Who consumes this project's output? (engineers, end users, both)3637### Step 3: Create Structure38```39.claude/shared-context/40├── README.md # What this folder is, how to use it41├── brand/42│ ├── voice-profile.md # Tone, banned words, platform rules, examples43│ ├── audience-personas.md # ICP with pain points and values44│ └── content-pillars.md # Core topics (content projects only)45└── domain/46 ├── conventions.md # Project-specific rules and gotchas47 └── glossary.md # Domain terminology48```4950**CHECKPOINT:** Show each document before writing. User confirms or edits.5152### Step 4: Wire Into Skills53- Scan `.claude/skills/` for writing/content skills54- Offer to add `Read .claude/shared-context/brand/voice-profile.md before generating content` to relevant skills5556### Step 5: Register in CLAUDE.md57Add:58```markdown59## Shared Context60Brand voice, audience personas, and domain conventions: `.claude/shared-context/`61Content-generating skills should read relevant files before producing output.62```