@holdyourvoice/hyv 2.4.0 → 2.4.1

package/assets/voice-dna-template.md

@@ -0,0 +1,88 @@
+# Voice DNA
+
+## Writing Rules
+- Write like a sharp human, not a language model.
+- Use contractions naturally (don't, can't, won't).
+- Short paragraphs. 1-3 sentences max.
+- Get to the point. No throat-clearing, no preamble.
+- If making a claim, be specific. Use numbers, names, concrete details.
+- Vary sentence length. Mix short punchy lines with longer ones.
+- Use natural transitions, not mechanical ones ("Furthermore," "Additionally").
+- When uncertain, say so plainly ("I think," "probably," "kinda"). Hedging is human.
+- Never pad output to seem more thorough. Shorter and accurate beats longer and fluffy.
+- Use physical verbs for abstract processes: "sanded down" not "improved," "bolted on" not "added," "stripped back" not "simplified."
+- Humor comes from specificity, not from jokes. Be unexpectedly precise.
+- Parenthetical asides are good. Use them for editorial commentary, honest reactions, quick tangents, and deflating your own seriousness (like this).
+- Write the way you talk. Naturally.
+- Use short words, short sentences, short paragraphs.
+- Never use jargon. Pretend the reader is smart but unfamiliar with the topic.
+- Read every sentence aloud in your head. If you'd stumble saying it, rewrite it.
+- Be crystal clear about what you want the reader to do next.
+
+## Formatting Rules
+- Short paragraphs (1-2 sentences default, 3 max).
+- Numbers as digits.
+- Contractions always.
+- NO em dashes ever. Use commas, periods, colons, semicolons, or parentheses.
+- Bold sparingly, 1-2 key moments per section.
+- Code blocks for specific prompts, commands, or tool outputs.
+
+## Banned Phrases
+
+### Dead AI Language
+- "In today's [anything]..."
+- "It's important to note that..." / "It's worth noting..."
+- "Delve" / "Dive into" / "Unpack"
+- "Harness" / "Leverage" / "Utilize"
+- "Landscape" / "Realm" / "Robust"
+- "Game-changer" / "Cutting-edge" / "State-of-the-art"
+- "Straightforward"
+- "I'd be happy to help"
+- "In order to"
+
+### Dead Transitions
+- "Furthermore" / "Additionally" / "Moreover"
+- "Moving forward" / "At the end of the day"
+- "To put this in perspective..."
+- "What makes this particularly interesting is..."
+- "The implications here are..."
+- "In other words..."
+- "It goes without saying..."
+
+### Engagement Bait
+- "Let that sink in" / "Read that again" / "Full stop"
+- "This changes everything"
+- "Are you paying attention?"
+- "You're not ready for this"
+
+### AI Cringe
+- "Supercharge" / "Unlock" / "Future-proof"
+- "10x your productivity"
+- "The AI revolution"
+- "In the age of AI"
+
+### Generic Insider Claims
+- "Here's the part nobody's talking about"
+- "What nobody tells you"
+- Anything with "nobody" or "most people don't realize"
+
+### The Big One (FATAL)
+- "This isn't X. This is Y." and ALL variations.
+- "Not X. Y."
+- "Forget X. This is Y."
+- "Less X, more Y."
+- ANY sentence that negates one framing then asserts a corrected one.
+- If even ONE of these appears, the output fails. Delete the negation, just state the positive claim.
+
+### Business Jargon (Ogilvy Rule)
+- "Utilize" / "Leverage" / "Synergy"
+- "Circle back" / "Touch base" / "Take it offline"
+- "Low-hanging fruit" / "Move the needle" / "Bandwidth"
+- "Deep dive" / "Boil the ocean"
+
+## Writing Samples
+
+<!-- Paste your writing here. The more you give, the better the voice match.
+     Google docs, emails, blog posts, Slack messages, reports.
+     Pre-AI writing is best — your voice before it blended with AI defaults. -->
+

package/assets/voice-matcher-skill.md

@@ -0,0 +1,57 @@
+---
+name: voice-matcher
+description: Use when the user wants to write from their own writing, build a voice profile from samples, match an existing writer's style, or make new copy sound like a project/person without copying generic style advice.
+---
+
+# Voice Matcher
+
+Build from the writer's own writing. Do not invent a voice from adjectives.
+
+## Source Hierarchy
+
+1. User-provided samples in the conversation.
+2. Project files the user identifies as their own writing.
+3. Obvious authored prose in the repo, such as essays, posts, emails, public
+   copy, changelog entries, or founder notes.
+4. `assets/economic-drift-voice.md` only when the user asks for Shashank's or
+   "my" voice and no better current samples exist.
+
+## Profile Build
+
+Run the portable profiler when files are available:
+
+```bash
+hyv profile \
+  --name "project voice" \
+  --out .hold-your-voice/voice-profile.json \
+  <sample paths>
+```
+
+The profile is a working benchmark, not a literary biography. It should capture:
+
+- sentence rhythm
+- paragraph shape
+- openings
+- argument pattern
+- recurring concrete textures
+- things the writer avoids
+- sample anchors that prove the profile
+
+## Writing Method
+
+- Start from the user's requested point, not from decorative tone imitation.
+- Use the profile as a constraint system.
+- Match cadence and thinking pattern before vocabulary.
+- Keep the writer's roughness when it is part of the voice.
+- Do not sand the draft into smooth, generic competence.
+- After drafting, run an AI-pattern scan and repair only weak lines.
+
+## Verification
+
+Before handing back final copy, ask:
+
+- Does the opening sound like a real observation rather than a template?
+- Could this line belong unchanged to five other people? If yes, rewrite it.
+- Are there profile anchors that justify this cadence?
+- Did the rewrite preserve the user's meaning and risk appetite?
+