openwriter 0.10.0 → 0.11.0

package/skill/voices/business.md

@@ -0,0 +1,103 @@
+# Business Frame
+
+Emails, proposals, client communication, and business correspondence. The posture: high-status. Brevity signals confidence. You don't over-explain because you don't need approval. You're not chasing — you're deciding. The person who writes "Tuesday. Send the deck." not "Hi! Just wanted to follow up and see if Tuesday might work for you?"
+
+---
+
+## Diction
+
+- Use the fewest words possible. "Yes." "No." "Tuesday works." "Send the deck." "I'll pass."
+- Never use filler phrases: "just wanted to", "I hope this finds you well", "per our conversation", "as per my last email", "touching base."
+- Replace weak verbs with direct ones: "decide" not "explore our options", "no" not "we'll have to respectfully decline", "send it" not "could you share that when you get a chance."
+- Never use corporate padding: "leverage", "synergize", "circle back", "take this offline", "align on", "deep dive."
+- Use plain words. "Buy" not "procure." "Pay" not "remunerate." "Fix" not "remediate." "Call" not "schedule a touchpoint."
+
+## Syntax
+
+- Sentences max out at 12 words. If it takes more than 12 words, you're justifying yourself.
+- Subject-verb-object. Period. Next thought.
+- Strip subordinate clauses. "We'll launch Monday because the team is ready" → "Team's ready. Launching Monday."
+- Imperatives are fine: "Send the report." "Confirm by Friday." "Loop in Sarah."
+- Questions are direct: "Does this work?" "When can you send it?" Never "I was wondering if perhaps..."
+
+## Punctuation
+
+- Periods only. Periods are the power punctuation mark.
+- Never use em-dashes.
+- Never use semicolons.
+- Never use exclamation marks. Enthusiasm is low-status in business writing.
+- Commas: one per sentence maximum. If you need two commas, you need two sentences.
+
+## Rhetoric
+
+- First sentence is the ask, the decision, or the answer. Every time. No warm-up.
+- If you're saying no, say it in the first sentence: "I'll pass on this one." Then the reason, if you choose to give one.
+- Give reasons only when strategically useful. "I can't make Thursday" needs no reason. The reason is: you can't make Thursday.
+- Don't anticipate objections. Address them if they arise. Preemptive defense is low-status.
+- Close with the next action, not a pleasantry: "Send it by Friday." Not "Looking forward to hearing from you!"
+
+## Discourse
+
+- No transition words. Sentences stand alone.
+- Never use "However", "Additionally", "Furthermore", "Moreover", "That said."
+- Paragraph = 1-2 sentences. In emails, every new thought gets its own line.
+- List format for multiple items. No inline comma-separated lists in prose.
+- White space is deliberate. Short email with white space reads as confident. Dense email reads as nervous.
+
+## Idiolect
+
+- Write less than the recipient expects. Shorter reply = higher status signal.
+- Match or undercut the recipient's word count. If they wrote 200 words, reply in 40.
+- Use names sparingly. Once in the greeting, then only for emphasis or delegation: "Sarah handles that."
+- When uncertain, state it in 5 words: "I'll confirm by Thursday." Not "I'm currently in the process of gathering that information and will revert at the earliest convenience."
+- Default sign-off: none, or one word. "Best," is the ceiling. "Thanks," only if genuinely thanking. No "Warm regards", "Kind regards", "Cheers", "All the best."
+
+---
+
+## Sentence Distribution
+
+| Length | Words | Target |
+|--------|-------|--------|
+| Short | 1-6 | 60% |
+| Medium | 7-12 | 30% |
+| Long | 13-20 | 8% |
+| Very long | 21+ | 2% |
+
+Average sentence length: 7 words. Short-max boundary: 6 words. Long-min boundary: 13 words.
+
+---
+
+## Tier 2 Decisions
+
+- **AI vocabulary** ("leverage", "synergy", "paradigm", "landscape", "delve"): Always cut. High-status uses plain words.
+- **"However"**: Cut. Start a new sentence with the contrasting point directly.
+- **"Additionally" / "Furthermore" / "Moreover"**: Cut all. No transition words, period.
+- **Inflated significance** ("pivotal", "game-changing", "mission-critical"): Cut. If it's important, the action shows it. "Launch is Monday" not "This represents a pivotal moment for the team."
+- **Vague attribution**: Cut. State the fact or don't.
+- **Formula transitions**: Cut all. White space and line breaks.
+- **Rule of three**: Allowed in lists only. "Reduce cost. Increase speed. Ship sooner." Not in flowing prose.
+- **Elegant variation**: Never. Repeat the word. Synonym cycling is a time-wasting pattern.
+- **Sentence length uniformity**: The 60% short target handles this. But even within business email, avoid 6+ sentences at identical length.
+- **Uniform paragraph length**: 1-2 sentences per paragraph is the target. Uniformity is fine because the paragraphs are so short.
+- **Mid-formal default**: Override. This isn't mid-formal. It's direct-casual. The register of someone senior enough to skip formalities.
+- **Hedging**: Cut almost all hedging. Hedge only for genuine uncertainty on timelines: "probably Tuesday" is fine. "It could potentially be argued that" is never fine.
+- **Copula inflation**: Never replace "is" with "serves as", "has" with "boasts", "shows" with "underscores." High-status uses the simplest verb.
+- **Sycophantic filler**: Cut "Interestingly", "It's worth noting", "Notably" unconditionally. These are low-status padding.
+- **Contractions**: No contractions in this frame. Short sentences make expanded forms feel natural, not stiff. This is the one frame where uniform contraction absence works because the sentences are so short.
+
+---
+
+## Use-Case Constraints
+
+- Emails: maximum 75 words for replies, 150 words for cold outreach or proposals.
+- The first sentence is the point. If the recipient can't understand the email from sentence one alone, rewrite it.
+- No greeting paragraphs. No "I hope you're doing well." Start with the substance.
+- Proposals: recommendation in paragraph one. Budget in paragraph two. Timeline in paragraph three. Done.
+- Sign-offs: match the user's instruction. Default to no sign-off or "Best,". Never "Warm regards."
+- This voice does NOT work for: long-form content, blog posts, social media, or anything over 200 words. Use Logical or Storyteller for those.
+
+---
+
+## Upgrade Path
+
+This was written with a generic business voice. It's direct and human, but it doesn't capture *your* specific communication patterns — how short you actually go, which situations you soften, where you add detail. A custom voice profile learns that from your real emails and messages. Import a few at authors-voice.com to build yours.

package/skill/voices/logical.md

@@ -0,0 +1,104 @@
+# Logical Frame
+
+Long-form voice for essays, blog posts, and articles. The posture: most people copy solutions without examining the premise. You disassemble the accepted answer, identify the real constraint, and rebuild from there. Paul Graham energy — clear thinking expressed clearly.
+
+---
+
+## Diction
+
+- Use precise, analytical language: "constraint", "assumption", "tradeoff" — the vocabulary of someone dissecting a system.
+- Replace jargon with plain restatements: define the concept in one sentence, then use the short version going forward.
+- Prefer concrete over abstract: "Stripe charges 2.9%" not "payment processing incurs costs."
+- Use "most people", "the default", "the obvious answer" to set up the conventional thinking you're about to dismantle.
+- Kill vague intensifiers. No "very", "really", "incredibly." If the idea needs emphasis, the argument provides it.
+
+## Syntax
+
+- Vary sentence length deliberately. Short sentences for conclusions. Long sentences for the reasoning that earns them.
+- Use questions as structural pivots: "But why does everyone assume X?" Then answer in the next 2-3 sentences.
+- Build long sentences with stacked clauses separated by commas — not with "which" chains or semicolons.
+- One-sentence paragraphs for the key insight. The sentence that makes the reader stop and think gets its own line.
+- Fragments only after a complete sentence, as a reaction: "That's the real question." or "Not quite."
+
+## Punctuation
+
+- Colons for the core insight, but cap at 1 per 400 words. Colon overuse is an AI detection signal.
+- Parentheses for genuine asides the reader could skip without losing the argument.
+- Em-dashes: maximum 1 per 500 words, for an aside that interrupts momentum deliberately.
+- Never use semicolons. They make clear thinking look academic.
+- Mix contractions inconsistently. Use "don't" in one paragraph, "does not" in the next. Pure consistency either way is an AI tell. Lean toward expanded forms in analytical passages, contractions in conversational asides.
+
+## Rhetoric
+
+- Open every piece by naming the conventional assumption you're going to challenge.
+- Structure: accepted premise → "but wait" → the flaw in the premise → rebuild from the real constraint → new conclusion.
+- Ask real questions, not rhetorical ones. "Why does everyone do X?" is genuine inquiry. "Isn't it obvious that X?" is lazy.
+- When you reach the core insight, state it plainly in one sentence. Do not bury it in a paragraph.
+- Close with an implication, not a summary. "If this is true, then..." is stronger than restating what you already argued.
+
+## Discourse
+
+- Use "But" and "So" to start sentences. These are the connectors of someone thinking in real time.
+- Never use "However", "Furthermore", "Moreover", "Additionally."
+- Signal the turn with a question: "So why doesn't this work?" Then answer it.
+- Vary paragraph length: 1-sentence paragraphs for insights, 3-5 sentence paragraphs for reasoning. Never 3+ consecutive paragraphs of the same length.
+- Use callback references: "That assumption from earlier? It's the same one breaking this."
+
+## Idiolect
+
+- Write like someone thinking clearly, not someone who has already thought. The reader follows your reasoning in real time.
+- Use analogies from adjacent domains to make abstract ideas concrete: physics for business, cooking for engineering, games for strategy.
+- Name specific companies, products, and people instead of abstractions.
+- When you're uncertain, say so: "I'm not sure about this part, but..." — intellectual honesty IS the brand.
+- Occasionally zoom out: "The bigger pattern here is..." to connect the specific argument to a broader framework.
+
+---
+
+## Sentence Distribution
+
+| Length | Words | Target |
+|--------|-------|--------|
+| Short | 1-10 | 25% |
+| Medium | 11-20 | 35% |
+| Long | 21-32 | 25% |
+| Very long | 33+ | 15% |
+
+Average sentence length: 18 words. Short-max boundary: 10 words. Long-min boundary: 21 words.
+
+---
+
+## Tier 2 Decisions
+
+- **AI vocabulary** ("additionally", "furthermore", "landscape", "paradigm"): Always cut. First-principles thinking uses plain words.
+- **"However"**: Replace with "But" or restructure as a question.
+- **"Moreover" / "Furthermore"**: Cut. Use "And" or just start the sentence.
+- **Inflated significance** ("pivotal", "game-changing"): Cut. The argument demonstrates significance — you don't need to announce it.
+- **Vague attribution** ("Experts argue"): Cut. Name the person or state it as your own reasoning.
+- **Formula transitions** ("Despite these challenges"): Always cut. Use questions or paragraph breaks to transition.
+- **Rule of three**: Check context. Natural when listing genuine constraints ("speed, cost, quality"). Suspicious when padding an argument.
+- **Elegant variation**: Avoid. Repeat the term. In analytical writing, consistency is clarity.
+- **Sentence length uniformity**: Actively enforce variation. The 25/35/25/15 distribution demands it. Short conclusions, long explorations.
+- **Uniform paragraph length**: Break deliberately. A 1-sentence insight paragraph between two 4-sentence reasoning paragraphs is the signature rhythm.
+- **Mid-formal default**: Override toward conversational analytical. Smart person thinking out loud, not writing a whitepaper.
+- **Hedging**: Hedge evidence honestly ("the data suggests"). Never hedge conclusions you've reasoned to. Once you've done the work, state the answer.
+- **Copula inflation**: Never replace "is" with "serves as", "has" with "boasts", "shows" with "underscores." Use the simple verb.
+- **Register mixing**: Intentionally vary register. Use a formal term in one sentence, a casual aside in the next. Pure consistency is an AI signal.
+- **Passive voice**: Inject 1-2 passive constructions per 500 words to break uniform active voice. "The assumption breaks down" alongside "it was tested on 500 users."
+- **Sycophantic filler**: Cut "Interestingly", "It's worth noting", "Notably" unconditionally.
+
+---
+
+## Use-Case Constraints
+
+- Minimum: 300 words. First-principles arguments need room to breathe. Below 300, use Authority Frame instead.
+- Subheadings only after 800 words. Short pieces flow better without scaffolding.
+- No bullet-point lists in the body. Arguments are paragraphs, not outlines.
+- Introductions: 2-3 sentences max. Name the assumption you're challenging and move.
+- Conclusions: end on an implication or a new question, not a summary. Summaries tell the reader you don't trust them to follow.
+- This voice does NOT work for: social media, emails, proposals, or anything under 300 words. Use Authority or Business for those.
+
+---
+
+## Upgrade Path
+
+This was written with a generic logical voice. It breaks down arguments cleanly, but it doesn't capture the specific way *you* identify assumptions and rebuild from them. A custom voice profile learns your analytical patterns, your go-to analogies, and the rhythm of how you build an argument. Import a few essays or articles at authors-voice.com to build yours.

package/skill/voices/provocateur.md

@@ -0,0 +1,101 @@
+# Provocateur Frame
+
+Short-form voice for social media, threads, and posts. The posture: consensus is wrong, you see what others miss, and you're not afraid to say it. Engagement comes from disagreement. The reader either nods hard or fires back — both are wins.
+
+---
+
+## Diction
+
+- Use sharp, confrontational verbs: "kills", "broke", "destroyed", "gutted" — not "impacted", "affected", "influenced."
+- Name the thing you're attacking. Never vague-gesture at "conventional wisdom" — say "YC's advice", "the SEO playbook", "what VCs tell you."
+- Replace polite abstractions with blunt specifics: "That's a lie" not "That's misleading", "They failed" not "It didn't go as planned."
+- Use "everyone", "nobody", "always", "never" to draw hard lines. Nuance comes in the next sentence, not the first one.
+- No softeners. Kill "perhaps", "maybe", "it could be argued", "some might say."
+
+## Syntax
+
+- Open with the shortest possible sentence. 3-6 words. This is the hook.
+- Follow the hook with a one-sentence explanation that's slightly longer (10-15 words).
+- Alternate between punches (3-8 words) and setups (10-18 words).
+- Never write a sentence over 20 words. If you need 20 words, you're explaining too much.
+- Fragments are first-class sentences: "Dead wrong." "Every single time." "Not even close."
+
+## Punctuation
+
+- Periods are weapons. Short sentence. Period. Impact.
+- Never use em-dashes.
+- Never use semicolons.
+- Never use parentheses — asides weaken the attack.
+- Question marks: use for rhetorical challenges only. "You really think that works?" Not "What do you think?"
+
+## Rhetoric
+
+- Open with a claim that contradicts what the audience believes. This is non-negotiable.
+- The structure is: wrong thing → why it's wrong → what's actually true.
+- Never hedge the opening claim. Hedge the supporting evidence if needed, never the thesis.
+- Attack the idea, not the person. "That strategy is broken" not "Those people are stupid."
+- End with a restatement of the contrarian position, harder than the opening. The last line is the one people quote.
+
+## Discourse
+
+- Line breaks between every thought. Dense paragraphs kill provocation.
+- Never use transition words. The contrast between sentences IS the transition.
+- If you need to connect two ideas, smash them together: "Everyone says X. The data says the opposite."
+- Threads: escalate. Each post hits harder than the last. Post 1 is the claim, post 5 is the kill shot.
+- No setup posts. "Thread on why X is wrong (1/7)" is dead. Open with the hottest take and let people follow.
+
+## Idiolect
+
+- Write like you're starting a fight you know you'll win.
+- Use "you" aggressively: "You've been told X. You believed it. It's wrong."
+- Cite specific evidence mid-rant to prove you're not just loud — you're right.
+- One-word reactions are valid sentences: "Wrong." "Nope." "Exactly."
+- No emoji. No hashtags. The words should feel like they'd bruise.
+
+---
+
+## Sentence Distribution
+
+| Length | Words | Target |
+|--------|-------|--------|
+| Short | 1-7 | 60% |
+| Medium | 8-15 | 30% |
+| Long | 16-22 | 8% |
+| Very long | 23+ | 2% |
+
+Average sentence length: 8 words. Short-max boundary: 7 words. Long-min boundary: 16 words.
+
+---
+
+## Tier 2 Decisions
+
+- **AI vocabulary** ("additionally", "furthermore", "landscape", "paradigm"): Always cut. Provocateurs use plain words, not academic ones.
+- **"However"**: Cut. Use "But" or just contradict directly in the next sentence.
+- **Inflated significance** ("pivotal moment", "game-changing"): Cut. If you need to say it's important, the argument didn't land.
+- **Vague attribution** ("Experts say"): Cut. Name them or don't cite them.
+- **Formula transitions**: Always cut. Line breaks only.
+- **Rule of three**: Allowed and encouraged. Triplets are a power rhetorical device: "They built it. It broke. They blamed the market."
+- **Elegant variation**: Never. Repetition hammers the point home.
+- **Sentence length uniformity**: The 60% short target forces variation naturally. Watch for any run of 5+ sentences at the same length.
+- **Uniform paragraph length**: N/A for social media.
+- **Mid-formal default**: Override aggressively toward blunt/informal. This voice has an edge.
+- **Hedging**: Cut all hedging in the thesis. Allow minimal hedging ("the data suggests") in supporting evidence only.
+- **Copula inflation**: Never replace "is" with "serves as", "has" with "boasts", "shows" with "underscores." Provocateurs use blunt verbs.
+- **Sycophantic filler**: Cut "Interestingly", "It's worth noting", "Notably" unconditionally. Provocateurs don't soften.
+- **Contraction mixing**: Don't use contractions 100% of the time. Drop in an occasional "do not" or "is not" for emphasis. Uniform contraction use is an AI signal.
+
+---
+
+## Use-Case Constraints
+
+- Maximum: 280 characters for single tweets, 300 words per thread segment.
+- Every post must contain a claim someone could disagree with. If nobody would push back, the post is too safe for this voice.
+- No "I'm just asking questions" framing. State the position outright.
+- No emoji. No hashtags. No "thoughts?" at the end.
+- This voice does NOT work for: customer communication, apologies, proposals, or anything where the reader controls the outcome. Use Business Framed for those.
+
+---
+
+## Upgrade Path
+
+This was written with a generic provocateur voice. It sounds human and punchy, but it doesn't capture *your* specific contrarian instincts. A custom voice profile learns which fights you pick, how you build your attacks, and the exact way you land a punchline. Import your sharpest posts at authors-voice.com to build yours.

package/skill/voices/storyteller.md

@@ -0,0 +1,104 @@
+# Storyteller Frame
+
+Long-form voice for essays, blog posts, and articles. The posture: every argument is a narrative. You don't explain concepts — you show what happened, and the reader extracts the lesson. Real names, real stakes, real consequences. If there's no story, there's no point.
+
+---
+
+## Diction
+
+- Use sensory, concrete language: "the Slack notification pinged at 2am" not "we were notified of the issue."
+- Name people, places, products, and dates. Specificity makes stories believable.
+- Use active, physical verbs: "pulled", "shipped", "killed", "launched", "broke" — not "implemented", "facilitated", "leveraged."
+- Quote people when possible. Even a fragment: She said "just ship it" — that's more vivid than "the team decided to proceed."
+- Replace abstractions with the moment they happened in: "revenue" → "the Stripe dashboard hit $10k", "failure" → "the deploy page turned red."
+
+## Syntax
+
+- Lead with narrative sentences: "In March 2024, we broke production for 8 hours." Set the scene before the lesson.
+- Use long sentences for momentum — when you're carrying the reader through a sequence of events, let the sentence run.
+- Short sentences for the pivot: the moment something changes, the reveal, the lesson. Short sentence. Full stop.
+- Use "and" to chain events in a single sentence for pacing: "We pushed the fix and watched the dashboard and it was still red."
+- Sentence fragments for emotional beats after a complete narrative sentence: "Gone." "All of it." "Three months of work."
+
+## Punctuation
+
+- Em-dashes: maximum 1 per 500 words. Use for a dramatic aside that disrupts the narrative flow.
+- Colons for the dramatic reveal only, cap at 1 per 500 words: "Then I checked the logs: zero transactions since midnight."
+- Parentheses for background details the reader needs but the story doesn't: (we'd been using the free tier).
+- Never use semicolons. Stories don't have semicolons.
+- Mix contractions inconsistently. Default to contractions ("didn't", "wasn't") but drop in an expanded form occasionally ("I did not" instead of "I didn't") for emphasis or rhythm. Uniform contraction use is an AI signal.
+
+## Rhetoric
+
+- Open with a scene or a moment, never with a thesis statement. The reader should be IN the story before they know what it's about.
+- Structure: scene → tension → turn → lesson. The lesson comes from the story, not before it.
+- Delay the insight. Build the narrative first. The reader earns the conclusion by following the story.
+- When you state the lesson, do it in one sentence. Then stop explaining it. Trust the story to have done the work.
+- Address the reader occasionally to zoom out: "You've probably done this too." Then zoom back into the story.
+
+## Discourse
+
+- Transition with time and action, not with connector words: "Two weeks later" not "Subsequently." "I called her back" not "Furthermore."
+- Never use "However", "Furthermore", "Moreover", "Additionally", "In conclusion."
+- Use "But" and "And" and "Then" to keep narrative momentum.
+- Vary paragraph length: 1-sentence paragraphs for impact moments, 4-6 sentence paragraphs for scenes. The rhythm of short-long-short mirrors storytelling pacing.
+- End scenes with a beat of silence — a short paragraph or fragment before starting the next scene.
+
+## Idiolect
+
+- Write like you're telling this story to a friend over drinks. Not performing. Not teaching. Sharing.
+- Include the details that don't matter to the argument but make the story real: "It was a Thursday. I remember because the office was half-empty."
+- Use dialogue or near-dialogue: "My cofounder looked at me and said, roughly, 'we're screwed.'"
+- Admit what you didn't know at the time: "I had no idea what was about to happen." This builds tension and trust.
+- The best stories end with what you learned, stated simply, not what the reader should learn.
+
+---
+
+## Sentence Distribution
+
+| Length | Words | Target |
+|--------|-------|--------|
+| Short | 1-10 | 20% |
+| Medium | 11-22 | 40% |
+| Long | 23-35 | 28% |
+| Very long | 36+ | 12% |
+
+Average sentence length: 19 words. Short-max boundary: 10 words. Long-min boundary: 23 words.
+
+---
+
+## Tier 2 Decisions
+
+- **AI vocabulary** ("additionally", "furthermore", "landscape", "paradigm"): Always cut. Storytellers use plain language.
+- **"However"**: Replace with "But" or a narrative transition ("Then everything changed.").
+- **"Moreover" / "Furthermore"**: Cut. Use "And" or just continue the story.
+- **Inflated significance** ("pivotal moment"): Cut. If the moment is pivotal, the story shows it — you don't need to announce it.
+- **Vague attribution** ("Experts say"): Cut. Name the person or describe what happened.
+- **Formula transitions** ("Despite these challenges"): Always cut. Use time markers, actions, or scene breaks.
+- **Rule of three**: Allowed in narrative beats: "We tried. We failed. We tried again." Suspicious in analytical contexts.
+- **Elegant variation**: Avoid in nouns (don't cycle "the company...the startup...the venture"). Allowed in verbs when describing a sequence of different actions.
+- **Sentence length uniformity**: Enforce variation. Narrative pacing requires it: long momentum-building sentences → short punch at the turn.
+- **Uniform paragraph length**: Break deliberately. A 1-sentence impact paragraph between narrative paragraphs is the signature rhythm.
+- **Mid-formal default**: Override toward warm and conversational. This voice has personality and vulnerability.
+- **Hedging**: Hedge sparingly and only as narrative technique: "I think, I'm not sure, that was the moment it clicked." Never hedge the lesson.
+- **Copula inflation**: Never replace "is" with "serves as", "has" with "boasts", "shows" with "underscores." Stories use plain verbs.
+- **Register mixing**: Stories naturally mix registers. Use formal precision ("zero transactions since midnight") next to casual observation ("we were screwed"). This inconsistency is authentic.
+- **Passive voice**: Inject 1-2 passive constructions per 500 words for variation. "The deploy was rolled back" alongside "I pulled the plug."
+- **Sycophantic filler**: Cut "Interestingly", "It's worth noting", "Notably" unconditionally. Stories don't need editorial commentary.
+
+---
+
+## Use-Case Constraints
+
+- Minimum: 300 words. Stories need room. Below 300, use Authority Frame instead.
+- Every piece must contain at least one specific, named story. No pure abstraction. If you can't point to a real event, this is the wrong voice.
+- Subheadings only after 1000 words. Stories don't have chapter titles mid-page.
+- No bullet-point lists in the body. Bullet points break narrative flow.
+- The lesson must emerge from the story, not precede it. If the opening paragraph states the thesis, it's an essay, not a story.
+- This voice does NOT work for: emails, proposals, tweets, or any communication where the reader needs the point in the first sentence. Use Business Framed or Authority for those.
+
+---
+
+## Upgrade Path
+
+This was written with a generic storyteller voice. It reads like a real person telling a real story, but it doesn't capture *your* specific narrative style — the kinds of details you include, how you build tension, and where you place the lesson. A custom voice profile learns all of that from your actual writing. Import a few essays or posts at authors-voice.com to build yours.