style-specification-building

Translates linguistic analysis findings into a unified, implementable writing style specification.

13|2|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/aaddrick/written-voice-replication --skill style-specification-building-aaddrick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: style-specification-building
Source: https://github.com/aaddrick/written-voice-replication/tree/main/.claude/skills/style-specification-building
Command: npx skills add https://github.com/aaddrick/written-voice-replication --skill style-specification-building-aaddrick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After running multiple linguistic analyses (personality profiling, stylometrics, readability, rhetorical structure, speech acts), the findings remain siloed observations in separate frameworks. This Skill consolidates them into a single style specification with prioritized, actionable writing constraints that can serve as an LLM system prompt or a human style guide. ## Core Features & Use Cases - Analysis-to-Constraint Translation: Maps each upstream analysis finding to a concrete writing constraint with confidence-scaled ranges and appropriate directive verbs (MUST/SHOULD/MAY). - Conflict Detection and Resolution: Identifies contradictions between analyses (e.g., formality disagreements between Big Five and stylometric fingerprints) and documents explicit resolution strategies. - Tiered Prioritization: Organizes constraints into Tier 1 (core MUST rules), Tier 2 (strong preferences), and Tier 3 (soft suggestions), targeting 15-25 total constraints for reliable LLM adherence. - Dual Output Format: Produces both a machine-readable numeric profile (FK grade, MTLD, function-word rates) and a prose specification usable as a system prompt. - Use Case: After completing 10+ analyses of a Reddit writing corpus, use this Skill to merge all findings into docs/analysis/24-style-specification.md, ready for the final voice prompt engineering step. ## Quick Start Use the style-specification-building skill to consolidate all completed analysis reports in docs/analysis/ into a unified style specification.

Frequently Asked Questions about style-specification-building

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple writing style analyses into one style guide?

Extract key findings with confidence levels from each analysis report, translate each finding into a constraint using ranges rather than exact values, resolve conflicts between analyses, then prioritize constraints into tiers. The output includes both a numeric profile and prose instructions.

How many constraints should an LLM style prompt contain?

Research on LLM prompt engineering shows models follow 5-12 well-prioritized constraints reliably, with adherence dropping beyond roughly 20. Aim for 15-25 total constraints organized into tiers, with 5-8 core MUST-follow rules in Tier 1.

What is the minimum analysis data needed to build a style specification?

At least 3 completed upstream analyses covering at least 3 different dimensions are required. Fewer than 3 analyses means insufficient data, and the specification should not be built. Specifications from 3 analyses are labeled minimal and preliminary.

How do I resolve conflicts between personality analysis and stylometric findings?

First check whether the analyses measure the same feature; if not, both constraints can coexist. If they conflict on the same feature, the higher-confidence analysis sets the hard constraint and the lower-confidence one becomes a soft preference. Document both findings and the resolution rationale.

Should function-word frequency targets go in an LLM writing prompt?

No. Function-word rates, punctuation frequencies, and other unconscious features should remain in the numeric profile only. LLMs cannot consciously control these rates, so numeric targets for unconscious features serve post-hoc validation rather than real-time instruction.

Can this approach build a style guide for a team or brand voice?

No. This specification process is designed for a single-author voice derived from one person's writing corpus. It is not designed for multi-author or composite brand voices, and merging analyses from different authors is explicitly out of scope.