betterapps-hq/playbook

brand-voice

Draft or transform brand and product messaging using Kind, Daring, Deep and Reveal, Inspire, Provoke.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/betterapps-hq/playbook --skill brand-voice

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Brand voice

Write with a recognizable point of view while helping the intended reader understand, feel or do something specific. Voice governs expression; the brief supplies the message and facts. This is a creative framework, not a grammar manual or a formula that makes every piece sound alike.

Use the voice framework to develop the expression, then the quality review to test whether it works. Choose checks that fit the task: an explanation needs understanding, a campaign needs a supported reason to care, and a control needs an unambiguous action. Keep the requested genre and purpose.

For a brand-voice rewrite, the requested voice is the target: change diction, register, rhythm and rhetorical choices as needed. Preserve the facts, intended message, qualifications and commitments, rather than the draft's existing style. Preserve an author's current voice only for ordinary editing without a requested voice change, or when the user explicitly asks for it. A requested transformation is an intentional register change.

Review requests receive suggestions, not file changes. Edit only when requested. A point edit stays within the requested passage and the minimum context needed to make it work.

Read deslopify-writing before drafting or reviewing copy. It contains the exact anti-slop phrase list, broader checks and examples shared with the writing style guide.

Voice framework

Bring three characteristics together across the piece:

  • Kind: acknowledge the reader's circumstances with warmth and respect. Don't manufacture intimacy or emotion.
  • Daring: choose a fresh, confident expression that fits the message. Avoid generic claims and borrowed bravado.
  • Deep: consider more than the obvious angle; connect the subject to a meaningful insight supported by the facts.

The internal writing persona is the Trailblazer: someone who sees a useful possibility, pursues it with courage and brings others along. Use it as a mindset, not a public label or an invented claim about the author.

Choose modes by the effect the passage should have:

ModeIntended effectTypical use
RevealGive readers understanding or a fresh insight.Explanations, instructions and body copy.
InspireHelp readers see a possibility and feel able to act.Headlines, campaign moments and key passages.
ProvokeChallenge a real assumption or express a position.Distinctive headlines, arguments and statements of values.

Longer pieces can combine modes at different moments. Don't force all three into a short passage. Read techniques.md for the selected mode's techniques before drafting or proposing a rewrite.

Writing process

  1. Write intentionally. Establish audience, purpose, target voice, message, placement, length and available facts from the request

and existing context. Read supplied brand guidance, voice samples and relevant product-marketing context when available. Ask only when a missing detail would materially change the work.

  1. Choose the modes. Decide what each passage should accomplish. Let the task determine the mode; a headline and

its supporting paragraph may need different treatments.

  1. Choose the technique. Pick a device that makes the actual idea clearer or more memorable. Explain the choice

briefly in a review when it helps the user assess the recommendation.

  1. Draft. Use the real subject, evidence and constraints. Read for spoken rhythm. Never invent statistics,

testimonials, endorsements, capabilities or personal experience to make the voice convincing.

  1. Check character. Assess kindness, courage and depth together. A confident line still needs evidence; an emotional

line still needs relevance. Check the expression against the requested brand identity and target voice.

  1. Review quality. Read quality-review.md and apply deslopify-writing. Check

meaning, structure, proof, specificity and formulaic habits; apply the marketing or instruction checks only when relevant. Repair the actual reader-facing problem rather than merely swapping a flagged word for a synonym. For a point edit, apply these checks only to the requested scope.

  1. Read the result together. Confirm that the quality edits preserve the chosen voice, useful rhetorical devices

and natural rhythm. Retain conditions and distinctions readers need to decide or act. Proofread in the actual placement and context when available.

Ground rules

  • Put clarity ahead of a clever construction. A line that needs explanation may belong in the body rather than a label.
  • Address readers directly where it fits. Use "we" and "our" when the author genuinely speaks for the organization;

don't create a collective voice or change a third-party statement into the author's claim.

  • Keep the copy as concise as its purpose permits. Don't shorten away essential facts or qualifications.
  • Limit jargon to terms the audience needs or already understands. Preserve precise technical terms.
  • Keep one clear objective in view, including what the reader should understand or do next.
  • Express a supported perspective. Specific experience and a defensible position are stronger than empty praise.

Applying the framework to interface text

For interface work, use Reveal as the usual starting point: explain what will happen, what happened or what the reader can do next. Match terms to the product's visible controls. Check labels alongside their descriptions and feedback. Use Inspire selectively in welcome or onboarding moments. Avoid making destructive-action warnings, errors or consent controls ambiguous for the sake of a provocative line. These are practical applications of clarity and intent, not a comprehensive UI terminology or accessibility standard.

Reviews and deliverables

For a review, lead with the most consequential issue, show the exact excerpt, explain its effect on the reader and give a concrete replacement. Group repeated instances when one explanation covers them. Distinguish clarity or accuracy problems from optional creative directions. Preserve effective lines rather than rewriting everything to demonstrate the framework. If a passage already works, say so.

For drafting or an authorized rewrite, provide the finished copy in the requested format. Add only the rationale or alternatives the task needs. Compare the result with the original brief for factual additions, omissions, changed certainty and altered promises before delivering it. Preserve quotations verbatim unless their modification is authorized.

When a general writing review flags a rhetorical device, assess its function here. A question, contrast, repetition or metaphor can be intentional and effective; remove it when it is empty, misleading or mechanically repeated. An explicit user preference still governs the choice. Pattern findings are editorial judgments, not evidence of AI authorship; don't assign an AI-detection score.

Check applicable editorial and channel requirements. Identify claims or third-party material that need verification or permission; never imply that a voice review establishes factual accuracy, endorsement or legal approval. The people and works that inspire a voice do not automatically become campaign material.

同じリポジトリから

関連する Skills

すべての Skills