How to keep a guide current.
A voice moves. Here is what to do when yours does, and how little it takes.
Read it once a quarter.
Open VOICE.md and read the banned list and the formats section. If every line still reads as yours, do nothing. If one line makes you wince, edit it; the files are text, and your edit is the guide now. Reinstall the edited file where it lives.
Re-interview on the topic.
A new product, a new audience, a new format you have started writing in. A re-interview asks five questions on that topic. Who it is for, one story, two stances, and how you would open a note about it. The answers merge into the guide as a new version, and every file is rebuilt. $9, five questions, about a minute each.
What a re-interview does well: adding a stories-bank entry, a stance, and a format for the new topic. What it does not do: rewriting the whole guide. For that, redo the interview.
Redo the interview.
A year on, a new role, or a guide that came out thin because the earlier interview was short. Record the eighteen questions again. A purchase includes up to three recordings of the full interview; a fresh guide replaces the previous one. Each makes a new version, and the text of earlier versions stays readable in your account.
Replace the file where it lives.
Claude: upload the new skill.zip; it replaces the old skill with the same name. Claude Code: overwrite voice-guide.md. ChatGPT: paste the new custom instructions, and replace VOICE.md in the project. Gemini: paste the new instructions and replace the knowledge file. The install guide has the steps.