Enforces brand guidelines on sales/marketing content like emails, proposals, pitch decks, and posts by loading from session, files, or user, applying voice/tone, and validating.
From brand-voicenpx claudepluginhub 8gg-git/knowledge-work-plugins --plugin brand-voiceThis skill uses the workspace's default tool permissions.
references/before-after-examples.mdreferences/voice-constant-tone-flexes.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Configures VPN and dedicated connections like Direct Connect, ExpressRoute, Interconnect for secure on-premises to AWS, Azure, GCP, OCI hybrid networking.
Apply existing brand guidelines to all sales and marketing content generation. Load the user's brand guidelines, apply voice constants and tone flexes to the content request, validate output, and explain brand choices.
Find the user's brand guidelines using this sequence. Stop as soon as you find them:
Session context — Check if brand guidelines were generated earlier in this session (via /brand-voice:generate-guidelines). If so, they are already in the conversation. Use them directly. Session-generated guidelines are the freshest and reflect the user's most recent intent.
Local guidelines file — Check for .claude/brand-voice-guidelines.md inside the user's working folder. Do NOT use a relative path from the agent's current working directory — in Cowork, the agent runs from a plugin cache directory, not the user's project. Resolve the path relative to the user's working folder. If no working folder is set, skip this step.
Ask the user — If none of the above found guidelines, tell the user: "I couldn't find your brand guidelines. You can:
/brand-voice:discover-brand to find brand materials across your platforms/brand-voice:generate-guidelines to create guidelines from documents or transcriptsWait for the user to provide guidelines before proceeding.
Also read .claude/brand-voice.local.md for enforcement settings (even if guidelines came from another source):
strictness: strict | balanced | flexiblealways-explain: whether to always explain brand choicesBefore writing, identify:
Voice is the brand's personality — it stays constant across all content:
Refer to references/voice-constant-tone-flexes.md for the "voice constant, tone flexes" model.
Tone adapts by content type and audience. Use the tone-by-context matrix from guidelines to set:
Create content that:
For complex or long-form content, delegate to the content-generation agent (defined in agents/content-generation.md).
For high-stakes content, delegate to the quality-assurance agent (defined in agents/quality-assurance.md) for validation.
After generating content:
When always-explain is true in settings, include brand application notes with every response.
When the user's request conflicts with brand guidelines:
Default to adapting guidelines with an explanation of the tradeoff.
Open questions are unresolved brand positioning decisions flagged during guideline generation, stored in the guidelines under an "Open Questions" section. When generating content, check if the brand guidelines contain open questions:
references/voice-constant-tone-flexes.md — The "voice constant, tone flexes" mental model, "We Are / We Are Not" table structure, and tone-by-context matrix explanationreferences/before-after-examples.md — Before/after content examples per content type showing enforcement in practice