← ClaudeAtlas

business-content-corelisted

Shared reference for the business-content cluster: the source-derived Voice Profile every lane reuses, the research/evidence substrate, the per-channel message contract, and the publish/market/fund/reach lane map. USE WHEN drafting any launch-, reputation-, or fundraising-sensitive content, building a Voice Profile, or planning multi-channel outbound — the interlocking conventions every spoke shares.
Sheshiyer/skill-clusters · ★ 0 · Web & Frontend · score 69
Install: claude install-skill Sheshiyer/skill-clusters
# Business-Content Core Shared model for the `business-content` cluster. The publish, market, fund, and reach spokes all depend on the same two upstream artifacts and the same channel discipline — keep them consistent here so no spoke contradicts another or drifts into generic AI copy. ## 1. The model the cluster turns on: voice-first, evidence-backed, channel-native Every output in this cluster is the same pipeline, regardless of lane: ``` Real sources ──derive──> VOICE PROFILE ─┐ ├──shape──> Draft ──fit──> Channel-native output Market/competitor facts ──ground──> Evidence ─┘ ``` Two upstream artifacts feed everything downstream: - **VOICE PROFILE** — a reusable style fingerprint built from *real* source material (posts, essays, launch notes, docs, site copy), not platform exemplars. It is the single source of truth for tone; downstream lanes **consume** it, they do not re-derive style per draft. → `brand-voice` - **Evidence** — market size, competitor positioning, fund/diligence facts with source attribution. Business claims trace to this, never to invention. → `market-research` **Rule:** if an output is voice-sensitive, the `VOICE PROFILE` is an input, not an afterthought; if it makes a business claim, that claim is sourced. Missing either is a defect, not a style choice. ## 2. The four lanes (and how they compose) - **Publish** (own channels) → `article-writing` (long-form), `content-engine` (platform-native systems, repurp