Agent skill · Content & Marketing

brand-language-codifier

Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand''s own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel''s voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry''s voice-dossier; not for finished copy

aaron-he-zhugithub.com/aaron-he-zhuGitHub ↗
claude-codeApache-2.0
Install
npx skills add aaron-he-zhu/aaron-marketing-skills --skill brand-language-codifier --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 13 KB
Bundled scripts: none
Version: 19.1.0
Requires: Claude Code and compatible agent-skill hosts
Path: narrative/architect/brand-language-codifier/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,508
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Brand Language Codifier Codifies the brand-level language canon — voice (register, tone spectrum, banned phrases, few-shot examples drawn only from the brand's own published material) and the naming tax (product / feature / tier naming rules, approved and banned terms) — as a dual-mode voice+naming step in the TALE **Architect** phase. It feeds two [TALE](../../../references/tale-benchmark.md)-`A` sub-items directly: *brand voice codified (register, tone, banned phrases, few-shots from own material only)* and *naming/lexicon tax defined (product/feature/tier naming rules, approved and banned terms)*. The voice rules it writes are the **brand-level source** the channel-registry `voice-dossier.md` adapts downward — channel voice points **up** to this canon, never redefines it — and its output seeds `memory/events/narrative.ndjson` via an authorized `operation: propose` request to `registry-events.py` for [narrative-registry](../../../protocol/narrative-registry/SKILL.md) to promote into the canon. It works one lever — brand language — and hands off. **Scope guard**: this skill produces voice and naming rules only. It does not author per-platform adaptations, finished copy, the upst

What's inside
Steps it walks through
  1. Quick Start
  2. Skill Contract
  3. Handoff Summary
  4. Data Sources
  5. Instructions
  6. Save Results
  7. Reference Materials
  8. Next Best Skill
More from aaron-marketing-skills
All skills →
About this skill
What does the brand-language-codifier skill do?

Use when the user asks to "codify our brand voice", "define naming rules for our products and tiers", or "write the tone-of-voice guide with banned phrases"; produces the brand-level voice canon (register, tone spectrum, banned-phrase list, few-shot examples drawn only from the brand''s own published material) and the naming tax (product / feature / tier naming rules plus approved and banned terms) that seeds the narrative-registry canon and that every channel''s voice adaptation points up to. Not for per-platform voice adaptation — use channel-registry''s voice-dossier; not for finished copy

How do I install it?

Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill brand-language-codifier --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going