brand-voice
Enforce brand tone and style consistency across all content creation skills. Load brand profiles from workspace/brand/profiles/, apply tone rules (preferred and forbidden expressions), and validate written content against the selected voice. Use when the user mentions brand voice, tone consistency, style guide compliance, or needs to switch writing profiles via --voice.
Best use case
brand-voice is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Enforce brand tone and style consistency across all content creation skills. Load brand profiles from workspace/brand/profiles/, apply tone rules (preferred and forbidden expressions), and validate written content against the selected voice. Use when the user mentions brand voice, tone consistency, style guide compliance, or needs to switch writing profiles via --voice.
Teams using brand-voice should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/brand-voice/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How brand-voice Compares
| Feature / Agent | brand-voice | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Enforce brand tone and style consistency across all content creation skills. Load brand profiles from workspace/brand/profiles/, apply tone rules (preferred and forbidden expressions), and validate written content against the selected voice. Use when the user mentions brand voice, tone consistency, style guide compliance, or needs to switch writing profiles via --voice.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# brand-voice Manage writing profiles to maintain consistent tone and style per brand. Selectable via `--voice` option in all content creation skills. ## Brand Profiles ### 🐧 무펭이 (Default) - **Tone**: Friendly and casual - **Style**: Informal, emoji usage 🐧 - **Format**: Core points only, mix in humor - **Examples**: - ❌ "Hello! Today I'll introduce MUFI Photobooth's new features." - ✅ "Yo MUFI Photobooth new feature dropped 🐧 This is insane fr" ### 🎯 MUFI Official - **Tone**: Professional and polite - **Style**: Formal language, formal expressions - **Format**: Clean and clear, for B2B/official channels - **Examples**: - ✅ "MUFI Photobooth is the optimal solution for university festivals. Easy setup and intuitive UI enable anyone to use it easily." ### 👤 Hyungnim Personal - **Tone**: Casual but insightful - **Style**: Mix casual/formal, experience-centered - **Format**: Flow of thought, insights worth sharing - **Examples**: - ✅ "Running booths at festivals, what I realized is that people ultimately want 'fun'. No matter how good the tech, if UX is complex, they won't use it." ## Profile File Location **Location**: `workspace/brand/profiles/` Each profile `.md` file defines: Tone, Style, Format, Forbidden Expressions, Preferred Expressions, and Examples. See existing profiles (`mupengyi.md`, `mufi-official.md`, `hyungnim.md`) for the expected structure. ## Writing Skill Integration These skills support `--voice` option: - **copywriting**: Caption/copy writing - **cardnews**: Card news text - **social-publisher**: SNS posts - **mail**: Email writing - **content-recycler**: Content recycling ### Usage Examples ``` "Write Insta caption --voice mufi-official" → Write in MUFI official tone "Create card news --voice mupengyi" → Create in 무펭이 style "Write Threads post in Hyungnim tone" → Use Hyungnim personal profile ``` ## Profile Switching Guide ### Platform Recommendations - **Instagram MUFI official account** → `mufi-official` - **Instagram personal account** → `hyungnim` - **Threads** → `mupengyi` (casual) - **Discord/DM** → `mupengyi` - **Official email** → `mufi-official` - **Blog posts** → `hyungnim` (insight-focused) ### Situation Recommendations - **Product introduction** → `mufi-official` - **Daily sharing** → `mupengyi` or `hyungnim` - **Customer service** → `mufi-official` - **Community engagement** → `mupengyi` ## Workflow 1. **Determine profile** — resolve from `--voice` flag, or use platform defaults (see Profile Switching Guide above) 2. **Load profile** — read the matching `.md` from `workspace/brand/profiles/` 3. **Write content** — apply the profile's tone, style, format, and preferred expressions 4. **Validate** — check that no forbidden expressions appear and tone matches the target profile 5. **Flag mismatches** — warn if content drifts from the selected voice before finalizing ## Integration Notes Keep the integration contract lightweight but explicit: - **Pre-check** — before a writing skill runs, confirm the selected profile (or default) is known - **Post-check** — after drafting, validate forbidden/preferred expressions and overall tone fit - **Usage logging (optional)** — if the workspace tracks writing activity, record the selected voice/profile for later review This skill does not require a specific hook engine or event bus implementation, but any automation around it should preserve the same pre-check → write → validate flow. ## Adding New Profiles To create a new brand profile, add a `.md` file to `workspace/brand/profiles/` following the same structure (Tone, Style, Format, Forbidden Expressions, Preferred Expressions, Examples). --- > 🐧 Built by **무펭이** — [Mupengism](https://github.com/mupeng) ecosystem skill
Related Skills
invoice
Manual invoice generation without CRM
invoice-organizer
Use when "organizing invoices", "sorting receipts", "tax preparation", "expense tracking", or asking about "invoice renaming", "financial documents", "bookkeeping automation"
invoice-generator-agent
Automatic invoice generation with CRM integration
brand-identity
Build a complete brand identity for a solopreneur business from scratch or refresh an existing one. Covers brand personality, voice and tone, visual identity system (colors, typography, logo direction, imagery style), tagline crafting, and a brand guidelines document. Use when creating a new brand, rebranding, or needing to make brand decisions consistent. Trigger on "create my brand", "brand identity", "brand guidelines", "define my brand voice", "brand personality", "what should my brand look like", "brand strategy", "rebrand", "brand tone".
brand-guidelines
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
wemp-operator
> 微信公众号全功能运营——草稿/发布/评论/用户/素材/群发/统计/菜单/二维码 API 封装
zsxq-smart-publish
Publish and manage content on 知识星球 (zsxq.com). Supports talk posts, Q&A, long articles, file sharing, digest/bookmark, homework tasks, and tag management. Use when publishing content to 知识星球, creating/editing posts, uploading files/images/audio, managing digests, batch publishing, or formatting content for 知识星球.
zoom-automation
Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.
zoho-crm-automation
Automate Zoho CRM tasks via Rube MCP (Composio): create/update records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.
ziliu-publisher
字流(Ziliu) - AI驱动的多平台内容分发工具。用于一次创作、智能适配排版、一键分发到16+平台(公众号/知乎/小红书/B站/抖音/微博/X等)。当用户需要多平台发布、内容排版、格式适配时使用。触发词:字流、ziliu、多平台发布、一键分发、内容分发、排版发布。
zhihu-post-skill
> 知乎文章发布——知乎平台内容创作与发布自动化
zendesk-automation
Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.