blog-brand
让写作子技能共享统一品牌与语音规范，便于一致输出。
生成项目级 BRAND.md 和 VOICE.md 建立持久品牌与写作语音。
把品牌和写作语音写成两个项目级文件（BRAND.md、VOICE.md），把受众定位、编辑禁忌、差异化要点和可读的人设说明都固化下来并写到项目根目录。用在需要跨多人、多文章保持一致品牌口径时，所有写作子工具会自动加载这些文件。特别之处是把抽象的品牌规则变成团队可持续引用的“源文件”。
▸ 展开 SKILL.md 英文原文
Establish durable brand and voice context for cross-skill consumption. Generates BRAND.md (audience, positioning, do/don't editorial rules, taboo phrases, competitor differentiation) and VOICE.md (existing persona JSON re-expressed as readable prose), both written to the project root. When present, all blog sub-skills auto-load these files before writing or reviewing. Pairs with blog-persona, which manages the structured persona JSON. Use when user says "blog brand", "create brand context", "brand voice doc", "BRAND.md", "VOICE.md", "establish editorial brand", "brand guidelines for blog".
帮我安装这个 skill：https://raw.githubusercontent.com/dxxx/Bot-OS/main/skills/claude-blog/skills/blog-brand/SKILL.mdcurl -fsSL "https://raw.githubusercontent.com/dxxx/Bot-OS/main/skills/claude-blog/skills/blog-brand/SKILL.md"# Blog Brand: Durable Editorial Context Generates two project-root files that every blog sub-skill auto-loads when present: - `BRAND.md`: who the audience is, what the brand stands for, what to never say - `VOICE.md`: how the brand sounds, structurally and lexically These are the editorial equivalent of impeccable's PRODUCT.md / DESIGN.md pattern: persistent context that survives across sessions and propagates to every command. ## Why this exists Today, persona JSON (from `blog-persona`) is loaded by some skills and not others. Topic-cluster context lives inside cluster vaults. Competitor positioning lives nowhere. Each blog command re-derives "what is the brand" from whatever context i