Skill Introduction

Overview

Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

Core value

Turns reusable Testing know-how into an installable skill, helping users complete github, community work faster.

Target users

Developers, testers, and maintainers who handle Testing tasks in Focus Code.
Teams that already trust workflows or content from affaan-m.
Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

Read the skill content first to confirm required inputs, expected outputs, and dependencies.
Try it on a small task before relying on it for critical work.
Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

Tasks related to github, community that need a reusable execution flow.
Converting a community repo, team convention, or personal workflow into day-to-day assistance.
Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

Results depend on the quality of the original skill content and may need human correction.
It does not replace code review, tests, security review, or professional judgment.
External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

Structured around Testing, making it easier to discover and reuse than loose prompt snippets.
Marked as GitHub, which helps users judge trust and maintenance expectations.
Keeps the original source link available for repository, documentation, or discussion follow-up.
Tagged with github, community, so it can be filtered by concrete task intent.

Install and use

Install

Copy Install Command

focus install brand-voice-471b6b

View source

Detail Preview

SKILL.md

Primary filemarkdown4 KB

name: brand-voice description: Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.

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.

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

Source Priority

Use the strongest real source set available, in this order:

recent original X posts and threads
articles, essays, memos, launch notes, or newsletters
real outbound emails or DMs that worked
product docs, changelogs, README framing, and site copy

Do not use generic platform exemplars as source material.

Collection Workflow

Gather 5 to 20 representative samples when available.
Prefer recent material over old material unless the user says the older writing is more canonical.
Separate "public launch voice" from "private working voice" if the source set clearly splits.
If live X access is available, use x-api to pull recent original posts before drafting.
If site copy matters, include the current ECC landing page and repo/plugin framing.

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.

Affaan / ECC Defaults

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

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

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.

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.

brand voice