learn-voicelisted

Derives a writing-style.md proposal from writing samples you supply -- your own sent messages, a mail export, a folder of exported threads, a text dump -- and shows the full proposed file before anything is written. Use when the user says "learn how I write", "build my writing style from my old messages", "work out my voice from these", or asks why their writing-style.md is still empty. It reads only samples the user states are their own writing, records style rules and never facts about people or projects, and writes nothing without approval of the exact content. On a file that already holds anything it shows a diff instead of overwriting. Run explicitly with /daikenja:learn-voice -- it never fires on its own. Not for recording how somebody else likes to be written to (that is /daikenja:remember-persona) and not for the rest of first-time setup (that is /daikenja:setup-user).
by-carlos/daikenja · ★ 0 · AI & Automation · score 69

Install: claude install-skill by-carlos/daikenja

# Learn voice `writing-style.md` is the user's own description of how they write. Every drafting skill layers it on top of the default voice in `${CLAUDE_PLUGIN_ROOT}/docs/voice.md`. Until now it had no author but the user, typing it out by hand, so for most people it stays the blank template and every message comes out in the default voice. This skill fills that gap in the only way that is safe. The user supplies samples of their own writing, this skill derives candidate style rules from them, shows the complete proposed file, and writes it only if the user approves that exact content. **Slash-only on purpose.** It reads the user's own prose and writes a file outside the project. Nothing about "make this sound like me" should make it fire on its own -- the user runs `/daikenja:learn-voice` when they mean to. `disable-model-invocation: true` is set for that reason. Throughout this skill, `writing-style.md` means whatever `profile.writing_style` resolves to -- a local file by default, or a Google Drive file. Step 5 and Step 7 are where the two differ; everything else is the same work on the same prose. ## Where this sits next to `setup-user` `setup-user` Step 5 states a rule that this skill deliberately does not share: *"Already there. Leave it alone... Never inspect or overwrite user prose."* That rule is load-bearing for `setup-user` being safe to re-run, and **it is unchanged**. `setup-user` still tests only whether the file exists, still copies the blank template on