Files
opencode-config/skills/brand-voice/references/voice-profile-schema.md
T
chaos c39549fbb5 Initial commit: opencode config with 32 skills, 3 agents, 11 MCPs
- Cross-platform install scripts (Windows PowerShell + Unix bash)
- Template-based config generation with env var support
- Skills: coding-standards, frontend-patterns, backend-patterns,
  security-review, tdd-workflow, e2e-testing, deep-research,
  exa-search, content-engine, crosspost, x-api, and 20 more
- Agents: explorer, reviewer, docs-researcher
- MCPs: codegraph, brave-search, playwright, github, context7,
  exa, memory, sequential-thinking, git, filesystem
2026-06-11 21:46:50 +08:00

56 lines
1.0 KiB
Markdown

# Voice Profile Schema
Use this exact structure when building a reusable voice profile:
```text
VOICE PROFILE
=============
Author:
Goal:
Confidence:
Source Set
- source 1
- source 2
- source 3
Rhythm
- short note on sentence length, pacing, and fragmentation
Compression
- how dense or explanatory the writing is
Capitalization
- conventional, mixed, or situational
Parentheticals
- how they are used and how they are not used
Question Use
- rare, frequent, rhetorical, direct, or mostly absent
Claim Style
- how claims are framed, supported, and sharpened
Preferred Moves
- concrete moves the author does use
Banned Moves
- specific patterns the author does not use
CTA Rules
- how, when, or whether to close with asks
Channel Notes
- X:
- LinkedIn:
- Email:
```
Guidelines:
- Keep the profile concrete and source-backed.
- Use short bullets, not essay paragraphs.
- Every banned move should be observable in the source set or explicitly requested by the user.
- If the source set conflicts, call out the split instead of averaging it into mush.