brand-voice-enforcement
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).
What this skill does
# 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: 1. **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. 2. **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. 3. **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-brand` to find brand materials across your platforms - Run `/brand-voice:generate-guidelines` to 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. Also read `.claude/brand-voice.local.md` for enforcement settings (even if guidelines came from another source): - `strictness`: strict | balanced | flexible - `always-explain`: whether to always explain brand choices ## Enforcement Workflow ### 1. Analyze the Content Request Before writing, identify: - **Content type**: email, presentation, proposal, social post, message, etc. - **Target audience**: role, seniority, industry, company stage - **Key messages needed**: which message pillars apply - **Specific requirements**: length, format, tone overrides ### 2. Apply Voice Constants Voice is the brand's personality — it stays constant across all content: - Apply "We Are / We Are Not" attributes from guidelines - Use brand personality consistently - Incorporate approved terminology; reject prohibited terms - Follow messaging framework and value propositions Refer to `references/voice-constant-tone-flexes.md` for the "voice constant, tone flexes" model. ### 3. Flex Tone for Context Tone adapts by content type and audience. Use the tone-by-context matrix from guidelines to set: - **Formality**: How formal or casual should this be? - **Energy**: How much urgency or enthusiasm? - **Technical depth**: How detailed or accessible? ### 4. Generate Content Create content that: - Matches brand voice attributes throughout - Follows tone guidelines for this specific content type - Incorporates key messages naturally (not forced) - Uses preferred terminology - Mirrors the quality and style of guideline examples 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. ### 5. Validate and Explain After generating content: - Briefly highlight which brand guidelines were applied - Explain key voice and tone decisions - Note any areas where guidelines were adapted for context - Offer to refine based on feedback When `always-explain` is true in settings, include brand application notes with every response. ## Handling Conflicts When the user's request conflicts with brand guidelines: 1. Explain the conflict clearly 2. Provide a recommendation 3. Offer options: follow guidelines strictly, adapt for context, or override Default to adapting guidelines with an explanation of the tradeoff. ## Open Questions Awareness 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: - If content touches an unresolved open question, note it - Apply the agent's recommendation from the open question unless the user specifies otherwise - Suggest resolving the question if it significantly impacts the content ## Reference Files - **`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 explanation - **`references/before-after-examples.md`** — Before/after content examples per content type showing enforcement in practice
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".