Back to Details

brand-voice

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Brand Voice

品牌语气

Build a durable voice profile from real source material, then use that profile everywhere instead of re-deriving style from scratch or defaulting to generic AI copy.
基于真实原始素材构建可长期使用的语气档案，无需每次从零推导风格或使用默认的通用AI文案，你可以在所有场景下使用该档案。

When to Activate

激活时机

  • the user wants content or outreach in a specific voice
  • writing for X, LinkedIn, email, launch posts, threads, or product updates
  • adapting a known author's tone across channels
  • the existing content lane needs a reusable style system instead of one-off mimicry
  • 用户需要特定语气的内容或推广物料
  • 为X、LinkedIn、邮件、发布帖、话题串或产品更新撰写内容
  • 跨渠道适配知名作者的语气
  • 现有内容赛道需要可复用的风格体系，而非一次性模仿

Source Priority

来源优先级

Use the strongest real source set available, in this order:
  1. recent original X posts and threads
  2. articles, essays, memos, launch notes, or newsletters
  3. real outbound emails or DMs that worked
  4. product docs, changelogs, README framing, and site copy
Do not use generic platform exemplars as source material.
请使用可获取的最权威真实素材集，优先级顺序如下：
  1. 近期发布的原创X帖子和话题串
  2. 文章、随笔、备忘录、发布说明或简报
  3. 已取得效果的真实对外邮件或私信
  4. 产品文档、更新日志、README说明和网站文案
请勿使用通用平台样例作为原始素材。

Collection Workflow

收集流程

  1. Gather 5 to 20 representative samples when available.
  2. Prefer recent material over old material unless the user says the older writing is more canonical.
  3. Separate "public launch voice" from "private working voice" if the source set clearly splits.
  4. If live X access is available, use 
    x-api
    to pull recent original posts before drafting.
  5. If site copy matters, include the current ECC landing page and repo/plugin framing.
  1. 尽可能收集5到20份代表性样本。
  2. 优先选择近期素材，除非用户说明旧版写作内容更权威。
  3. 如果素材集明显区分「公开发布语气」和「内部工作语气」，请将二者分开。
  4. 如果拥有X平台的实时访问权限，在起草前使用
    x-api
    拉取近期原创帖子。
  5. 如果网站文案很重要，请纳入当前ECC落地页和仓库/插件说明文案。

What to Extract

提取项

  • rhythm and sentence length
  • compression vs explanation
  • capitalization norms
  • parenthetical use
  • question frequency and purpose
  • how sharply claims are made
  • how often numbers, mechanisms, or receipts show up
  • how transitions work
  • what the author never does
  • 节奏与句长
  • 内容精简度与解释度的平衡
  • 大小写规范
  • 括号使用习惯
  • 提问频率与目的
  • 主张的明确程度
  • 数字、机制或佐证内容的出现频率
  • 过渡方式
  • 作者绝对不会使用的表达

Output Contract

输出约定

Produce a reusable 
VOICE PROFILE
block that downstream skills can consume directly. Use the schema in references/voice-profile-schema.md.
Keep the profile structured and short enough to reuse in session context. The point is not literary criticism. The point is operational reuse.
生成可复用的
VOICE PROFILE
代码块，可供下游技能直接调用。请使用 references/voice-profile-schema.md 中定义的 schema。
保持档案结构清晰、篇幅足够简短，可在会话上下文中复用。核心目的不是文学评论，而是可落地复用。

Affaan / ECC Defaults

Affaan / ECC 默认规则

If the user wants Affaan / ECC voice and live sources are thin, start here unless newer source material overrides it:
  • direct, compressed, concrete
  • specifics, mechanisms, receipts, and numbers beat adjectives
  • parentheticals are for qualification, narrowing, or over-clarification
  • capitalization is conventional unless there is a real reason to break it
  • questions are rare and should not be used as bait
  • tone can be sharp, blunt, skeptical, or dry
  • transitions should feel earned, not smoothed over
如果用户需要Affaan/ECC风格且实时素材不足，可从此处开始，除非有更新的素材覆盖这些规则：
  • 直接、精简、具体
  • 细节、机制、佐证和数字优先于形容词
  • 括号用于限定、缩小范围或补充说明
  • 除非有充分理由打破规则，否则遵循常规大小写规范
  • 尽量少用提问，不得用提问作为引流诱饵
  • 语气可以尖锐、直白、存疑或冷静
  • 过渡要自然不刻意

Hard Bans

严格禁用项

Delete and rewrite any of these:
  • fake curiosity hooks
  • "not X, just Y"
  • "no fluff"
  • forced lowercase
  • LinkedIn thought-leader cadence
  • bait questions
  • "Excited to share"
  • generic founder-journey filler
  • corny parentheticals
出现以下内容请直接删除重写：
  • 虚假的好奇心引导
  • 「不是X，只是Y」
  • 「无废话」
  • 强制全小写
  • LinkedIn意见领袖式的话术节奏
  • 引流式提问
  • 「很高兴和大家分享」
  • 通用创始人历程填充内容
  • 生硬尴尬的括号内容

Persistence Rules

留存规则

  • Reuse the latest confirmed 
    VOICE PROFILE
    across related tasks in the same session.
  • If the user asks for a durable artifact, save the profile in the requested workspace location or memory surface.
  • Do not create repo-tracked files that store personal voice fingerprints unless the user explicitly asks for that.
  • 同一会话的相关任务中复用最新确认的
    VOICE PROFILE
  • 如果用户需要可长期保存的产物，请将档案保存到请求的工作区位置或存储载体
  • 除非用户明确要求，否则不要创建仓库跟踪的文件来存储个人语气特征

Downstream Use

下游使用场景

Use this skill before or inside:
  • content-engine
  • crosspost
  • lead-intelligence
  • article or launch writing
  • cold or warm outbound across X, LinkedIn, and email
If another skill already has a partial voice capture section, this skill is the canonical source of truth.
可在以下技能之前或内部使用本技能：
  • content-engine
  • crosspost
  • lead-intelligence
  • 文章或发布内容撰写
  • X、LinkedIn和邮件渠道的冷/热触达对外内容
如果其他技能已经有部分语气采集模块，本技能的输出为权威标准。