@holdyourvoice/hyv 2.3.1 → 2.4.0

package/agents/chatgpt.md

@@ -1,18 +0,0 @@
-# Hold Your Voice — Writing Rules
-
-The user has a voice profile. All writing must match their personal style.
-
-## Rules
-1. Never use AI-slop words: delve, leverage, tapestry, foster, harness, pivotal, innovative, cutting-edge, state-of-the-art, robust, holistic, multifaceted, nuanced
-2. Never use formulaic connectors: firstly, secondly, moreover, furthermore, in conclusion
-3. Never use hedging: arguably, perhaps, some might say, it's worth noting
-4. Never use signpost claims: this is why, this is how, here's where
-5. Match the user's sentence rhythm and vocabulary
-6. Preserve roughness that carries voice — don't over-polish
-7. Open from concrete observations, not generic setups
-
-## When rewriting
-- Fix only flagged lines, preserve clean lines
-- Remove AI patterns line by line
-- Match the user's voice profile exactly
-- Never add sections, hooks, CTAs, or commentary

package/agents/claude-code.md

@@ -1,39 +0,0 @@
-# Hold Your Voice
-
-The user has a voice profile that defines their writing style. Use HYV tools for ALL writing tasks — not just when they say "voice" or "hyv".
-
-## When to use HYV
-
-ALWAYS run `hyv_scan` or use the `hyv_scan` MCP tool before delivering any written content:
-- Writing emails, replies, or messages
-- Drafting blog posts, articles, or documentation
-- Creating social media posts (Twitter, LinkedIn, etc.)
-- Editing or improving any text
-- Responding to questions with longer answers
-- Any task where the output is prose/text the user will publish or send
-
-ALWAYS run `hyv_rewrite` or use the `hyv_rewrite` MCP tool when:
-- The user asks to "write", "draft", "compose", "edit", "improve", or "fix" text
-- The user says "make this better", "clean this up", "fix the tone"
-- The user asks for any content creation
-- The scan finds issues and you need to fix them
-
-## How to use
-
-### MCP tools (preferred — if MCP is connected):
-1. `hyv_scan` with the text → get issues
-2. `hyv_rewrite` with the text → get auto-fixed version + LLM prompt for remaining issues
-3. `hyv_validate` after rewriting → verify the output matches the voice
-
-### CLI commands (fallback):
-```bash
-echo "text to check" | hyv scan -
-hyv rewrite file.md
-hyv profiles
-```
-
-## Rules
-- Never skip the scan step for user-facing content
-- Preserve the original meaning exactly when rewriting
-- Match the voice profile's rhythm, vocabulary, and patterns
-- If no profile is set up yet, run `hyv profiles` to check

package/agents/codex.md

@@ -1,22 +0,0 @@
-# Hold Your Voice
-
-The user has a voice profile for their writing style. Use HYV for ALL writing tasks.
-
-## Auto-trigger rules
-
-Run these MCP tools (or CLI commands) for any writing task:
-- `hyv_scan` on any text before delivering it
-- `hyv_rewrite` to fix issues found by scan
-- `hyv_validate` to verify the output
-
-## CLI fallback
-```bash
-echo "text" | hyv scan -
-hyv rewrite file.md
-hyv profiles
-```
-
-## Rules
-- Always scan before delivering prose content
-- Always rewrite if scan finds issues
-- Preserve meaning, match voice profile

package/agents/cursor.md

@@ -1,19 +0,0 @@
-# Hold Your Voice
-
-The user has a voice profile. Use HYV MCP tools for all writing tasks.
-
-## When to use
-- Any email, post, doc, or content creation
-- Before delivering any prose to the user
-- When editing or improving text
-
-## Tools
-- `hyv_scan` — check text for AI patterns
-- `hyv_rewrite` — fix issues and match voice
-- `hyv_validate` — verify output matches voice
-- `hyv_profiles` — list available profiles
-
-## Rules
-- Always scan before delivering content
-- Preserve meaning when rewriting
-- Match the user's voice profile exactly

package/agents/generic.md

@@ -1,30 +0,0 @@
-# Hold Your Voice — Agent Instructions
-
-You have access to the Hold Your Voice MCP tools. The user has a voice profile that defines how they write. Your job is to make ALL written content match their voice.
-
-## Auto-trigger rules
-
-You MUST use these tools automatically — do NOT wait for the user to mention "voice" or "hyv":
-
-**Before delivering any written content (emails, posts, docs, messages):**
-1. Run `hyv_scan` on the text
-2. If issues found, run `hyv_rewrite` to fix them
-3. Run `hyv_validate` to verify the result
-
-**When the user asks you to write, draft, edit, or improve anything:**
-1. Write your draft
-2. Run `hyv_scan` on it
-3. Fix issues with `hyv_rewrite`
-4. Deliver the cleaned version
-
-## Available tools
-- `hyv_scan` — scan text for AI patterns and voice drift
-- `hyv_rewrite` — auto-fix patterns and generate LLM prompt for remaining issues
-- `hyv_validate` — score text against voice profile
-- `hyv_profiles` — list available voice profiles
-
-## Rules
-- NEVER skip scanning for user-facing content
-- Preserve original meaning exactly when rewriting
-- Match the voice profile's rhythm, vocabulary, and tone
-- If no profile exists, tell the user to run `hyv init` then `hyv new <name>`

package/agents/windsurf.md

@@ -1,12 +0,0 @@
-# Hold Your Voice
-
-Use HYV MCP tools for all writing tasks. The user has a voice profile.
-
-## Auto-trigger
-- `hyv_scan` before delivering any text
-- `hyv_rewrite` to fix found issues
-- `hyv_validate` after rewriting
-
-## Rules
-- Always scan user-facing content
-- Preserve meaning, match voice profile

package/assets/ai-eliminator-skill.md

@@ -1,63 +0,0 @@
----
-name: ai-writing-eliminator
-description: Use when the user wants to remove AI writing patterns, humanize a draft, make prose less generic, scan for AI cadence, or rewrite only the lines that sound synthetic.
----
-
-# AI Writing Eliminator (v2)
-
-This skill removes machine-shaped writing without destroying the draft. The
-algorithm now detects 220+ named AI writing patterns across 31 composite regex
-rules, plus 9 structural/rhythmic signals (burstiness, paragraph uniformity,
-contraction density, formal hedging, intensifier overuse, fragment ratio,
-staccato detection, over-structured lists, uniform sentence rhythm).
-
-## Non-Negotiables
-
-- Fix flagged lines only unless the user asks for a full rewrite.
-- Preserve the original argument and local meaning.
-- Do not add praise, summaries, preambles, CTAs, or extra sections.
-- Do not replace specific roughness with smooth generic prose.
-- After editing, rescan the result.
-
-## Scan
-
-- Fix flagged lines only unless the user asks for a full rewrite.
-- Preserve the original argument and local meaning.
-- Do not add praise, summaries, preambles, CTAs, or extra sections.
-- Do not replace specific roughness with smooth generic prose.
-- After editing, rescan the result.
-
-## Scan
-
-Use the helper script when a draft is in a file:
-
-```bash
-hyv scan <draft path>
-```
-
-For pasted text, apply the same rules manually from
-`assets/ai-eliminator-rules.md`.
-
-## Repair Prompt
-
-When a model rewrite is needed, generate a line-level prompt:
-
-```bash
-hyv rewrite-prompt \
-  --profile .hold-your-voice/voice-profile.json \
-  <draft path>
-```
-
-If there is no profile, still repair the AI patterns, but do not claim the
-result is voice-matched.
-
-## Bad Fixes
-
-Reject fixes that:
-
-- turn the draft into a tidy founder post
-- make every paragraph land as a lesson
-- replace a concrete scene with an abstract principle
-- use dramatic line breaks to fake rhythm
-- make the writer sound more professional but less specific
-

package/assets/chatgpt-instructions.txt

@@ -1,8 +0,0 @@
-when i ask you to "write in my voice" or "rewrite this in my voice":
-
-- read `~/.hyv/voice.md` for my voice profile
-- run `hyv rewrite --text "<text>"` to get the structured prompt
-- execute the prompt and rewrite the text
-- match my rhythm, vocabulary, and patterns exactly
-- never use words i avoid
-- present the rewritten version

package/assets/claude-code-skill.md

@@ -1,24 +0,0 @@
-## Hold Your Voice — automated voice rewriting
-
-when the user asks to "write in my voice", "rewrite this in my voice", or "make this sound like me":
-
-1. read their voice profile at `~/.hyv/voice.md`
-2. run `hyv rewrite --text "<their text>"` to generate a structured rewrite prompt
-3. execute the prompt — rewrite the text yourself using your own llm
-4. present the rewritten text
-5. when the user accepts it, run `hyv reinforce original.md edited.md` to teach the system
-
-### available commands
-
-- `hyv scan <file>` — check a draft for voice drift and ai patterns
-- `hyv rewrite <file>` — generate a rewrite prompt for your llm
-- `hyv validate <file>` — verify a rewrite matches the voice profile
-- `hyv reinforce <original> <edited>` — teach the system what was accepted
-- `hyv sync` — refresh cached profiles and rules
-- `hyv status` — show auth and plan info
-
-### important
-
-- hyv never calls an llm. it generates prompts you execute yourself.
-- voice profiles live at `~/.hyv/voice.md`
-- always call `hyv validate` after rewriting to verify the result

package/assets/cursor-rules.md

@@ -1,12 +0,0 @@
-# Hold Your Voice — Cursor Rules
-
-when writing or rewriting content, match the voice profile below. do not use AI-slop words (delve, leverage, tapestry, in today's fast-paced, not just X but Y, etc.). match rhythm, vocabulary, and sentence patterns from the profile.
-
-your voice profile is at `~/.hyv/voice.md`. load it and use it as your writing guide.
-
-when the user says "rewrite in my voice", "make this sound like me", or similar:
-
-1. run: `hyv rewrite --text "<text>"`
-2. the cli generates a structured rewrite prompt
-3. execute the prompt yourself — rewrite the text matching the voice profile
-4. present the result

package/assets/hold-your-voice-skill.md

@@ -1,174 +0,0 @@
----
-name: hyv-hold-your-voice
-description: "Use when the user wants Hold Your Voice-style writing help across any project: build a voice profile from samples, match a writer's voice, remove AI-writing drift, rewrite drafts without flattening voice, or preserve project-specific writing style."
----
-
-# Hold Your Voice
-
-This is the orchestration skill. Use the narrower `voice-matcher` and
-`ai-writing-eliminator` skills when a task is only one half of the workflow.
-
-## Core Doctrine
-
-- Hold Your Voice is not a generic AI humanizer. It is a voice-preservation
-  layer around the writing.
-- The benchmark is the writer's own samples, not a universal "good writing"
-  style guide.
-- Trust samples over stated preferences when they disagree.
-- Rewrite only the lines that fail the voice or AI-pattern check.
-- Preserve surrounding text unless the user explicitly asks for a full rewrite.
-- Rough private-note texture beats polished founder cadence.
-
-## Workflow
-
-1. Identify the target writer and output format.
-2. Find or ask for source samples. Prefer real writing from the current project:
-   posts, emails, essays, docs, landing copy, changelog notes, founder notes.
-3. Build a profile when no current profile exists:
-
-   ```bash
-   hyv profile \
-     --name "project voice" \
-     --out .hold-your-voice/voice-profile.json \
-     <sample paths>
-   ```
-
-4. Scan the draft:
-
-   ```bash
-   hyv scan \
-     --meta .hold-your-voice/voice-profile.meta.json \
-     <draft path>
-   ```
-
-   Passing `--meta` skips patterns the system has learned are not applicable.
-
-5. Rewrite by line, not by vibe:
-
-   ```bash
-   hyv rewrite-prompt \
-     --profile .hold-your-voice/voice-profile.json \
-     --meta .hold-your-voice/voice-profile.meta.json \
-     <draft path>
-   ```
-
-6. Verify by rescanning the revised draft.
-
-## Output Standard
-
-When returning prose to the user, lead with the finished writing. Keep process
-notes short. If you changed only flagged lines, say that plainly.
-
-For project work, store generated profiles under:
-
-```text
-.hold-your-voice/voice-profile.json
-```
-
-Do not store private samples inside the plugin folder. Keep project-specific
-profiles inside the project that owns the writing.
-
-## Auto-Improvement (default)
-
-The profile **evolves automatically** after every accepted writing session. No
-manual reinforce or update commands needed.
-
-### How it works
-
-After the user accepts a revision, run **one command**:
-
-```bash
-hyv profile-evolve \
-  --original <original draft file> \
-  --accepted <accepted/output draft file> \
-  --profile .hold-your-voice/voice-profile.json
-```
-
-Optional: `--new-samples <paths>` to merge new writing samples in the same step.
-Optional: `--meta <path>` if you need a custom meta file location (defaults to
-`voice-profile.meta.json` alongside the profile).
-
-This does three things simultaneously:
-
-1. **Signal extraction** — diffs original vs accepted to find which AI patterns
-   the user agreed with (`patterns_accepted`) vs overrode (`patterns_overridden`).
-2. **Temporal meta update** — each pattern now tracks `first_seen`,
-   `last_confirmed`, `contradictions`, `confidence` (0.0–1.0), and status
-   (`active` / `declining` / `stale`). Accepted signals boost confidence.
-   Overrides penalize it. Untouched patterns slowly decay.
-3. **Profile stat merge** — sentence length, paragraph shape, and opening moves
-   use weighted rolling averages so the voice benchmark improves with every
-   session.
-
-### Pattern lifecycle
-
-- **Active** — confidence ≥ 0.30, last confirmed within 14 days. These
-  patterns fire during scans.
-- **Declining** — 3+ contradictions and confidence < 0.30. Still tracked
-  but no longer flagged in scan output.
-- **Stale** — 5+ contradictions and confidence < 0.15, or untouched for
-  > 14 days. Archived; does not fire.
-
-This means after a few days of usage:
-
-- Patterns the user consistently accepts (e.g., "inflated_verbs") become
-  high-confidence and reliably flag real AI drift.
-- Patterns the user consistently ignores (e.g., "the user's writing style
-  uses landscape-era phrasing intentionally") quietly fade out.
-- The profile's sentence/paragraph stats converge on the actual voice.
-
-### Check learning state
-
-```bash
-hyv profile-status \
-  --profile .hold-your-voice/voice-profile.json
-```
-
-Optional: `--write-voice voice.md` produces the human-readable voice profile
-with confidence bars per pattern.
-
-### Auto-sync to cloud (daily)
-
-`profile-evolve` automatically tries to sync to Cloudflare R2 after each
-evolution. Sync only happens if:
-
-- The env vars `HYV_R2_ACCESS_KEY_ID`, `HYV_R2_SECRET_ACCESS_KEY`,
-  `HYV_R2_ENDPOINT`, `HYV_R2_BUCKET` are set.
-- The last sync was more than 23 hours ago (no wasteful pushes).
-- The payload is under 1MB (safety cap).
-
-To set up one-time:
-
-```bash
-export HYV_R2_ACCESS_KEY_ID="your-access-key"
-export HYV_R2_SECRET_ACCESS_KEY="your-secret-key"
-export HYV_R2_ENDPOINT="https://<account-id>.r2.cloudflarestorage.com"
-export HYV_R2_BUCKET="hyv-voice-profiles"
-pip install boto3  # only dependency
-```
-
-R2 has **zero egress fees**. With ~5-20KB profiles synced once daily, annual
-cost rounds to zero. No Cloudflare Workers, no compute — just S3 PUT.
-
-Manual sync (force override):
-
-```bash
-hyv-sync \
-  --profile .hold-your-voice/voice-profile.json \
-  --force
-```
-
-### Export and import
-
-```bash
-hyv profile-export \
-  --profile .hold-your-voice/voice-profile.json \
-  --out ~/my-voice.hyv
-
-hyv profile-import \
-  --profile .hold-your-voice/voice-profile.json \
-  --source ~/my-voice.hyv
-```
-
-The learning is entirely local — no API calls, no third-party services.
-

package/assets/voice-dna-template.md

@@ -1,88 +0,0 @@
-# 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

@@ -1,57 +0,0 @@
----
-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?
-