Keeps every piece of AI-generated content aligned with Message Point Media's voice, tone, messaging pillars, and visual identity. Brand settings are baked in — works immediately in any working folder with no setup required.
## Skills
### Brand Voice Enforcement
Apply MPM's brand guidelines to any content you're creating.
**Trigger phrases:** "write an email", "draft a proposal", "create a pitch deck", "write a LinkedIn post", "write in our voice", "make this sound like MPM", "this doesn't sound on-brand"
The skill loads the baked-in MPM brand settings via `bash cat` (required — the Read tool cannot access `.remote-plugins` paths) and applies them to your content — voice constants, tone adjustments for your audience, correct product terminology, and messaging pillar alignment. If the settings file is unreachable, the skill stops and surfaces an explicit error rather than falling back silently to generic styling. It explains the brand choices it made and offers to refine.
**v1.1.0 additions:** Logo selection table and placement rules for DOCX/PPTX/PDF/email. Explicit Visual Identity block — Montserrat headings, Open Sans body, exact hex color palette. Warning against generic blue (#1A4F8A) and system fonts (Arial, Calibri).
Update or enrich MPM's brand settings from new source materials.
**Trigger phrases:** "update our brand settings", "analyze these materials for brand voice", "add this content to our guidelines", "generate brand guidelines from these documents"
Use this when you have new conference presentations, sales transcripts, updated messaging, or new product documentation that should be reflected in the brand settings. The skill builds on the existing settings rather than replacing them.
---
## How Brand Settings Work
The plugin ships with `settings/brand-voice.local.md` — the full MPM brand settings file. This is the baked-in default that works in any working folder.
> ⚠️ **Read method matters:** The `Read` tool cannot access `.remote-plugins` paths and fails silently. The brand-voice-enforcement skill uses `bash cat` to read the settings file. If it cannot be read, the skill stops and tells you — it will never silently produce generic output.
For most projects, the baked-in settings are all you need. Use a working folder override only when a specific project requires different positioning (e.g., a co-branded proposal, a specific sub-brand focus).
---
## Keeping Settings Current
The MPM brand evolves. When it does:
1.**Update the master** — Edit `.claude/brand-voice.local.md` in the Claude CoWork working folder on Google Drive. This is always the source of truth.
2.**Repackage the plugin** — Open Cowork, select the Claude CoWork folder, and ask Claude to "repackage the MPM brand voice plugin with the updated settings."
3.**Push to the org library** — Upload the new `.plugin` file to the organization plugin library.
| 1.1.0 | May 2026 | Patched brand-voice-enforcement: bash cat required for settings read (Read tool silently fails on .remote-plugins); hard stop on read failure. New Logo Usage section with selection table, placement rules, and fallback behavior. Visual Identity block with explicit font/hex requirements and warning against generic blues/system fonts. |
