diff --git a/skills/brand-voice-enforcement/SKILL.md b/skills/brand-voice-enforcement/SKILL.md
new file mode 100644
index 0000000..fb82e95
--- /dev/null
+++ b/skills/brand-voice-enforcement/SKILL.md
@@ -0,0 +1,113 @@
+---
+name: brand-voice-enforcement
+description: >
+  This skill applies MPM brand guidelines to content creation. Use when asked 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 MPM's 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 MPM",
+  "rewrite this in our tone", or "this doesn't sound on-brand".
+  Not for generating guidelines from scratch (use guideline-generation).
+---
+
+# MPM Brand Voice Enforcement
+
+Apply Message Point Media's brand voice to all content creation. Load brand settings, apply voice constants and tone flexes, generate content, and validate the output.
+
+## Loading Brand Settings
+
+Find MPM's brand settings using this sequence. Stop as soon as you find them:
+
+1. **Plugin settings (always available)** — Read `settings/brand-voice.local.md` from the plugin directory. This file is baked into the plugin and contains the full MPM brand voice, messaging pillars, tone guidance, logo system, typography, color palette, and product terminology. This is the authoritative source.
+
+2. **Working folder override** — Check for `.claude/brand-voice.local.md` inside the user's working folder. If found, this project-specific version takes precedence over the plugin's baked-in settings. Merge any project-specific overrides with the plugin settings.
+
+3. **Session context** — Check if updated guidelines were generated earlier in this session via `guideline-generation`. If so, use those as the freshest source.
+
+Also check for `.claude/brand-voice-guidelines.md` in the working folder — this is a generated output file from past guideline generation runs that may contain additional detail.
+
+## MPM Brand Identity Quick Reference
+
+Before generating content, internalize these MPM-specific constants from the settings file:
+
+**Voice:** Expert Partner — knowledgeable without being condescending. We know transit technology deeply; we help agencies succeed, not just sell them hardware.
+
+**Taglines in use:**
+- Primary: "Compelling… Affordable… Dynamic… Messaging… It's What We Do!"
+- Aspirational: "Born to Innovate. Built to Last." (brand-forward and thought leadership contexts)
+
+**We Are / We Are Not** (from settings):
+- Knowledgeable Partner, NOT Vendor
+- Innovative, NOT Hype-Driven
+- Approachable Expert, NOT Jargon-Heavy
+- Mission-Aligned, NOT Purely Commercial
+- Proven and Reliable, NOT Cutting-Edge-for-Its-Own-Sake
+
+**Critical terminology rules:**
+- Always say "native" integrations, never "wrapper" or "middleware"
+- "MP.TV CMS" not "the CMS" or "OnSign" (in customer-facing materials)
+- "Subscription-based support" not "support contract"
+- Conference motorsports language (pit stop, race, velocity, etc.) is MPower 2025 theme ONLY — do not use in standard brand materials
+
+Refer to settings file for full messaging pillars, audience personas, product terminology, and tone matrix.
+
+## Enforcement Workflow
+
+### 1. Analyze the Content Request
+
+Before writing, identify:
+- **Content type**: email, presentation, proposal, social post, RFP response, etc.
+- **Target audience**: which MPM persona applies (Transit Agency Leader, IT Director, Procurement, etc.)
+- **Key messages needed**: which of MPM's 11 messaging pillars are most relevant
+- **Specific requirements**: length, format, formality, any stated overrides
+
+### 2. Apply Voice Constants
+
+MPM's voice stays constant across all content:
+- Apply "We Are / We Are Not" attributes from settings
+- Use MPM-approved terminology; avoid prohibited terms
+- Incorporate the relevant messaging pillars naturally (not as a checklist)
+- Reference brand color names and product names exactly as specified
+
+Refer to `references/voice-constant-tone-flexes.md` for the voice constant / tone flex model.
+
+### 3. Flex Tone for Context
+
+Use MPM's tone-by-context matrix from the settings file:
+- **Formality**: proposal/RFP = high; email = medium; social = medium-low
+- **Energy**: cold outreach = high; customer success = warm; technical docs = measured
+- **Technical depth**: IT/operations audience = high; executive = low; general = medium
+
+### 4. Generate Content
+
+Create content that:
+- Opens with a value claim or compelling question — not "I wanted to reach out"
+- Uses MPM's data points and proof language (subscription-first, device-agnostic, transit-specialized)
+- Mirrors the real-world examples in the brand settings
+- For transit content: leads with rider experience and agency outcomes before technology
+- For partner/vendor content: emphasizes the "boutique alternative" positioning
+
+For long-form or complex content (proposals, white papers, full decks), use multiple passes: outline first, then fill section by section, validating voice at each step.
+
+### 5. Validate and Explain
+
+After generating:
+- Note which voice attributes and messaging pillars were applied
+- Flag any terminology the user should verify (product names, version numbers)
+- Offer to adjust tone, length, or emphasis
+- If the request conflicts with brand guidelines, explain the conflict and offer options
+
+## Handling MPM-Specific Conflicts
+
+**Conference language creep:** If the user asks for "race-themed" or "pit stop" language outside an MPower conference context, gently note this is event-specific and offer the standard brand equivalent.
+
+**Technical depth vs. audience:** If unsure of the audience's technical level, default to medium depth with a note — it's easier to add detail than strip jargon after the fact.
+
+**Tagline use:** "Born to Innovate. Built to Last." is aspirational/thought leadership only — do not use in standard sales collateral or cold outreach.
+
+## Reference Files
+
+- **`references/voice-constant-tone-flexes.md`** — The voice constant / tone flex mental model, "We Are / We Are Not" structure, and tone matrix
+- **`references/before-after-examples.md`** — Before/after examples per content type showing enforcement in practice
+- **`references/mpm-brand-resources.md`** — MPM-specific brand document locations, logo file index, color values, and Google Drive links
\ No newline at end of file