brand-voice-enforcement
Brand Voice Enforcement
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.
Loading Brand Guidelines
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.mdinside 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:
- Run
/brand-voice:discover-brandto find brand materials across your platforms - Run
/brand-voice:generate-guidelinesto create guidelines from documents or transcripts - Paste guidelines directly into this chat or point me to a file"
Wait for the user to provide guidelines before proceeding.
- Run
More from anthropics/knowledge-work-plugins
data-visualization
Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.
6.5Kcode-review
Review code changes for security, performance, and correctness. Trigger with a PR URL or diff, "review this before I merge", "is this code safe?", or when checking a change for N+1 queries, injection risks, missing edge cases, or error handling gaps.
4.2Ktask-management
Simple task management using a shared TASKS.md file. Reference this when the user asks about their tasks, wants to add/complete tasks, or needs help tracking commitments.
3.5Ksystem-design
Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.
3.4Kdocumentation
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
3.3Kmemory-management
Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acronyms, nicknames, and internal language so Claude understands requests like a colleague would. CLAUDE.md for working memory, memory/ directory for the full knowledge base.
3.3K