It's not about whether the rewriting is good or bad, it's about whether the rewriting is right—right for this platform, this channel, this scenario.
Five Scenarios
Technical Documentation
The core is just one thing: accuracy before rhetoric, clarity before excitement.
One paragraph conveys only one information point. One sentence has only one main clause. Don't touch code, URLs, or API paths. First check the target project's own AGENTS.md and glossary; don't mechanically replace.
Different content's openings answer different questions:
- Entry page/introduction page → what it covers, who it's for, where to start reading
- API documentation → method/path/parameter types + units + default values + limits
- UI copy → button text states the action + target, error messages state the impact + recovery
- Operation manual → prerequisites + steps + failure handling + recovery method
Banned words: empower, lever, closed loop, precipitate, align, benchmark, connect, open up, insight, track, tone, campaign, momentum, backstop, land on disk, wrap up, pass through. These words obscure the actual action; say directly what it actually refers to.
Ad Copy
The core framework is AIDA: Attention→Interest→Desire→Action.
Eight headline styles:
- Judgment type: topic + key moment. For example, "2026, the watershed for asset allocation"
- Promise type: audience + result + method. For example, "3 strategies that even beginners can use to beat inflation"
- Narrative type: one/ten years + audience + experience. For example, "Ten years of a retail investor"
- Pain point type: don't want to/don't understand + pain point + solution. For example, "Don't want to be the sucker anymore? Read this first"
- Counterintuitive type: counter to common sense + why. For example, "People who buy funds are all pretty good at enduring"
- Data type: specific number + conclusion. For example, "A-shares single-day turnover 3.6 trillion"
- Suspense type: a vivid event + suspense. For example, "That person still watching the K-line at 3 a.m."
- Comparison type: A vs B + choice. For example, "Three years of dollar-cost averaging vs chasing rallies and selling on dips"
Banned in headlines: revisiting, a brief discussion of, also on, thoughts on..., ...'s. These words hint that "this is an internal discussion/old topic," which is a repelling signal to new readers.
Body structure: create curiosity or resonance in the first 3 seconds, use data/stories/analogies in the middle to prove value, and end with a clear verb + low barrier to action as a call to action.
CTA comparison:
- ✅ "Alright, go try it" / "After reading this, empty your shopping cart"
- ❌ "Upgrade immediately" / "The future is promising"
PPT Presentation
Core principle: one page, one point. Each page has only one core message.
Visual hierarchy: one main color takes 60-70%, 1-2 secondary colors, one accent color. Don't divide all colors equally.
Sandwich structure: dark title + light content + dark ending. Or go all dark throughout; don't be half dark and half light.
If you can use an image, don't use a table; if you can use a table, don't pile on text. No more than 6 lines per page, no more than 20 characters per line.
Color reference:
- Business report → navy + ice blue + white
- Startup fundraising → dark green + moss gray + off-white
- Product launch → coral red + gold + navy
- Tech sharing → charcoal gray + white charcoal + pure black
Speaker notes: no more than 50 characters per page, write "what to say" not "what to talk about", and mark when to turn the page.
Social media
The content logic is completely different on different platforms:
Xiaohongshu: title no more than 20 characters, keywords first. Body text 300-800 characters, make good use of emoji for paragraph markers. Start by directly highlighting the pain point, keep the middle dense with useful content, and guide interaction at the end.
WeChat Official Account: title 15-30 characters, spark curiosity or resonance. The first 3 sentences decide everything. Leave an aftertaste or a call to action at the end.
Zhihu: use a question in the title with long-tail keywords. The content should have logical depth, not follow a formula.
Douyin: the first 3 seconds must grab attention. Every sentence must drive emotion. Strongly colloquial, suitable for voiceover.
Jike: short sentences + topic tags. Insights, complaints, interaction. Don't write long essays.
The tone also varies by platform: Xiaohongshu is like chatting with a friend, WeChat Official Account is sincere and has judgment, Zhihu is professional and logical, Douyin is strongly colloquial, and Jike is insights and complaints.
Release Notes
Core: oriented toward user-visible changes, extracted from git log, not written from memory.
Structure template:
## Breaking Changes
## New Features
## Fixes & Improvements
## Deprecations
Rules:
- Group by user-visible features, not by internal functions. "Starts faster" is not called "performance optimization"
- Extract from git log, read feat:/fix: commits. Do not write from memory
- One entry should state only one change. Do not pile them up
- Bilingual project: English block and Chinese block side by side, not mixed line by line
Prohibited: "Polish" / "细节打磨" / "Misc improvements" — users cannot understand them.
Collaboration with other skills
After the packaging workshop is done, you can optionally do scenario adaptation before publishing:
packaging-workshop（包装工坊） → scene-fit（场景适配，可选） → 发布
Typical usage:
- "This post is suitable for Xiaohongshu" → Xiaohongshu adaptation
- "Help me change it into technical documentation format" → technical documentation adaptation
- "Write a PPT for a product launch" → PPT adaptation
- "Generate Release Notes from git log" → Release Notes adaptation
Output
Directly output the text after scenario adaptation, with one sentence explaining which scenario it was adapted to.
Do not do this
- Sacrifice factual accuracy to adapt to a scenario
- Change data, version numbers, API paths, and other machine-readable content
- Use the exaggerated techniques of advertising copy in technical documentation
- Use stacked technical terminology in advertising copy
scene-fit v1.1.0 — five scenarios, zero content loss