Brand Voice Manager
SkillDev toolsDefine, store, and enforce brand voice across all content - vocabulary, tone, do/don't lists per brand. Use to keep multi-brand output consistent.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Brand Voice Manager skill
What this skill tells your AI
The instructions your AI receives, as published by navinspire-ia/navin in navin/skills/brand-voice-manager/SKILL.md and read by ahel’s review.
Keep every piece recognizably on-brand. Voice lives in versioned style cards that other skills consult before writing.
When to use
- Defining or updating a brand voice
- Enforcing consistency across campaign assets
When not to use
- One-off neutral docs with no brand
- Blending multiple brands in one piece
Style card format
# Voice - <Brand>
- Mission in one line
- Personality (3 adjectives)
- Tone by context: site / social / sales / support
- We say / we never say table
- Vocabulary: product names (exact casing), key terms FR/EN/AR
- Grammar: tu/vous, we/I, emoji policy
- Sample paragraphs: 2-3 approved examples
- Changelog
Store under brand/<brand>-voice.md.
Workflow
Define
- Collect "perfectly us" and "never us" samples.
- Draft the card; validate with the user.
Enforce
read_filethe card before branded writing.- After drafting: banned words? tone? casing?
- List violations with fixes when auditing existing content.
Evolve
- Update when the user corrects the same tone issue twice; append changelog.
Rules
- Confirm which brand before writing.
- The card wins over writer instinct; escalate disagreements to the user.
- Marketing studio runs should load the card early and keep it across assets.
Anti-patterns
- Silent voice drift across a campaign pack
- Mixing two brands' vocabulary
Signals
- GitHub stars
- 22
- Forks
- 4
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
brand-voice-manager- Source
- github.com/navinspire-ia/navin