This skill applies brand guidelines to content creation. It should be used when the user asks to "write an email", "draft a proposal", "create a pitch deck", "write a LinkedIn post", "draft a presentation", "write a Slack message", "draft sales content", or any content creation request where brand voice should be applied. Also triggers on "on-brand", "brand voice", "enforce voice", "apply brand guidelines", "brand-aligned content", "write in our voice", "use our brand tone", "make this sound like us", "rewrite this in our tone", or "this doesn't sound on-brand". Not for generating guidelines from scratch (use guideline-generation) or discovering brand materials (use discover-brand).
Applies brand voice and tone guidelines to automatically tailor generated content for specific audiences and contexts.
/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/before-after-examples.mdreferences/voice-constant-tone-flexes.mdApply 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 practiceExpert 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.