These rules come from the project owner. Follow them strictly.
Narrative structure
Open from the reader's pain point, not the feature. Don't start with "we released X." Start with the problem the reader is living with. Describe the scenario vividly so they recognize themselves in it.
One line to introduce the solution. After the pain point lands, say what this version does in one sentence.
Break down the supporting mechanisms. Explain the layers / building blocks that make the solution work. Order them by the flow the user experiences, not by importance.
Industry context as supporting evidence, not the opening. If there are relevant industry trends (e.g., new tools from Anthropic, competitor features), reference them to validate the direction. But they go in the middle or late section, never the lead.
Converge to a conclusion. Tie the pieces back together. The punchline should echo the opening pain point: "this is why you can now do X."
Tone and voice
Don't speak for the reader. Never write "you probably think X" or "you definitely feel Y." Describe the situation, let readers identify with it on their own.
Casual, not corporate. Write like you're explaining to a sharp colleague, not writing a press release. No marketing speak, no filler adjectives.
No em dashes (——) in Chinese. Use commas, periods, or sentence breaks instead.
Chinese should read like Chinese. Not translated-from-English. Spoken rhythm, natural phrasing.
English should read like English. Not translated-from-Chinese. Prefer short punchy sentences. Avoid "materialize," "leverage," "utilize" — use plain words.
Logical consistency matters. The owner will catch contradictions immediately. If you say "we had X from day one," make sure that's actually true. If something was added in a specific version, say so.
No filler. If one sentence covers it, don't stretch it to three.
Title
Include the version number: Chorus vX.Y.Z: <hook>
The hook is the real title. It should make someone want to click.
Can mix Chinese and English, use slang, be playful.