This skill generates, creates, or builds brand voice guidelines from source materials. It should be used when the user asks to "generate brand guidelines", "create a style guide", "extract brand voice", "create guidelines from calls", "consolidate brand materials", "analyze my sales calls for brand voice", "build a brand playbook from documents", "synthesize a voice and tone guide", or uploads brand documents, transcripts, or meeting recordings for brand analysis. Also triggers when the user has a discovery report and wants to convert it into actionable guidelines.
Generates structured brand voice guidelines from documents, transcripts, and reports with confidence scoring and open questions.
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install brand-voice@knowledge-work-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/confidence-scoring.mdreferences/guideline-template.mdGenerate comprehensive, LLM-ready brand voice guidelines from any combination of sources — brand documents, sales call transcripts, discovery reports, or direct user input. Transform raw materials into structured, enforceable guidelines with confidence scoring and open questions.
Accept any combination of:
When a discovery report is provided, use it as the primary input — sources are already triaged and ranked. Supplement with additional analysis as needed.
Determine what the user has provided. If no sources are available:
/brand-voice:discover-brand run.claude/brand-voice.local.md for known brand material locations/brand-voice:discover-brandFor documents: Delegate to the document-analysis agent for heavy parsing. Extract voice attributes, messaging themes, terminology, tone guidance, and examples.
For transcripts: Delegate to the conversation-analysis agent for pattern recognition. Extract implicit voice attributes, successful language patterns, tone by context, and anti-patterns.
For discovery reports: Extract pre-triaged sources, conflicts, and gaps. Use the ranked sources directly.
Merge all findings into a unified guideline document following the template in references/guideline-template.md. Key sections:
"We Are / We Are Not" Table — The core brand identity anchor:
| We Are | We Are Not |
|---|---|
| [Attribute — e.g., "Confident"] | [Counter — e.g., "Arrogant"] |
| [Attribute — e.g., "Approachable"] | [Counter — e.g., "Casual or sloppy"] |
Derive attributes from the most consistent patterns across sources. Each row should have supporting evidence.
Voice Constants vs. Tone Flexes — Clarify what stays fixed and what adapts:
Tone-by-Context Matrix:
| Context | Formality | Energy | Technical Depth | Example |
|---|---|---|---|---|
| Cold outreach | Medium | High | Low | "[example phrase]" |
| Enterprise proposal | High | Medium | High | "[example phrase]" |
| Social media | Low | High | Low | "[example phrase]" |
Score each section using the methodology in references/confidence-scoring.md:
Generate open questions for any ambiguity that cannot be resolved:
## Open Questions for Team Discussion
### High Priority (blocks guideline completion)
1. **[Question Title]**
- What was found: [conflicting or incomplete info]
- Agent recommendation: [suggested resolution with reasoning]
- Need from you: [specific decision or confirmation needed]
Every open question MUST include an agent recommendation. Turn ambiguity into "confirm or override" — never a dead end.
Before presenting, verify via the quality-assurance agent (defined in agents/quality-assurance.md):
Summarize key findings:
The default save location is .claude/brand-voice-guidelines.md inside the user's working folder.
Important: The agent's working directory may not be the user's project root (especially in Cowork, where plugins run from a plugin cache directory). Always resolve the path relative to the user's working folder, not the current working directory. If no working folder is set, skip the file save and tell the user guidelines will only be available in this conversation.
.claude/brand-voice-guidelines.md inside the user's working folder. Confirm the working folder path before writing.brand-voice-guidelines-YYYY-MM-DD.md in the same directory (using today's date).claude/brand-voice-guidelines.md inside the working folder<full-path>. /brand-voice:enforce-voice will find them automatically in future sessions."The guidelines are also present in this conversation, so /brand-voice:enforce-voice can use them immediately without loading from file.
After saving, offer:
/brand-voice:enforce-voiceEnforce these privacy constraints throughout the entire generation workflow, not only at output time:
references/guideline-template.md — Complete output template with all sections, field definitions, and formatting guidancereferences/confidence-scoring.md — Confidence scoring methodology, thresholds, and examplesExpert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.