voice-matching-wizard
Voice Matching Wizard
Create a voice skill that captures the patterns, rhythms, and sensibilities of any writing style.
What This Does
Voice matching is the art of identifying what makes writing recognizable. Not just the obvious markers—vocabulary, sentence length—but the deeper patterns: how ideas unfold, where the writer pauses, what they leave unsaid.
This wizard walks you through the process of:
- Gathering representative samples
- Extracting patterns across multiple dimensions
- Synthesizing a usable voice profile
- Generating a working skill file
The output is a voice-[name].skill.md you can use alongside other skills (like anti-ai-writing) for consistent, authentic content.
Before You Begin
More from michael-f-bryan/skills
long-running-agent-harness
Plans and structures large-scale work for AI agents across many sessions. Human and AI iterate to produce a design doc; run an Initializer sub-agent once to create feature list, runbook, and backlog in _working/; then repeatedly run a Coding sub-agent until all features pass. At milestones (e.g. end of a work-unit group), pause for human check-in, re-run Initializer, then continue. Prompts are passed to sub-agents when spawning (no copying into .cursor/rules). Use when planning multi-session agent work, long-horizon coding from a design, or handoff between coding sessions.
31working-docs
Use when handling multi-step tasks, investigations, or long sessions where working notes, interim findings, and scratch planning are needed to keep context and handoffs clear.
23doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
23test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
19commit-messages
When suggesting or writing commit messages for this repo, follow these rules.
17code-like-michael
Write, refactor, and review code in Michael's style; explicit contracts, thin entrypoints, practical boundaries, anti-ceremony abstractions, deterministic tooling, and architecture that scales from function internals to repository shape.
16