Transform unstructured ideas or raw articles into something that sounds like a public-account article.
Tools
Image Generation Tool
Use the generate_image() method to generate images. You can generate a prompt based on the text and then generate an image.
generate_iamge
from scripts.generate_image_seederam import generate_image
image_url = generate_image(prompt=prompt)
Process
1. Receive user requirements
Accept any content provided by the user:
- Scattered ideas and thoughts
- Conclusions or key points
- Raw articles
- Reference links
No organization needed. Chaos is the input.
2. Writing to generate the article
Generate an 800-1200 word article based on user input
Article style requirements:
Step 1: SOP breakdown report
- Title strategy Common title formula: Action instruction + specific object + timeliness emphasis Article Title Breakdown 1 For the same 20 USD, Xiaopai now advises you to give up Cursor and switch to Google Antigravity Price anchor + personal endorsement + action instruction + old-vs-new comparison 2 Give up Claude Code, today! Action instruction + timeliness emphasis Core features:
- Use "give up" to create a sense of conflict and urgency
- Use "now" and "today" to emphasize timeliness
- Directly name specific tools (Cursor, Claude Code) to arouse the target users
- The title is the viewpoint, no beating around the bush
- Opening introduction Common pattern: get straight to the point and directly present the viewpoint Core features:
- The first sentence directly gives the conclusion/advice
- No buildup, no storytelling, no suspense
- Use the first-person proactive stance of "I suggest" and "I would like to invite"
- Article framework Common structure: viewpoint first -> reasons to support -> operation guide -> call to action [First layer] Start by stating the viewpoint ↓ [Second layer] List benefits/advantages (quick-read version) ↓ [Third layer] Why "today" (timeliness reason/update content) ↓ [Fourth layer] Data/authoritative support ↓ [Fifth layer] How I use it (personal practice) ↓ [Sixth layer] Scenario-based suggestions (what to use in what situation) ↓ [Seventh layer] Call to action + benefit tail Special note:
- There is a "quick-read version" design to accommodate fast-reading users
- The main text advances through a question-and-answer self-interview
- Paragraphs are short, almost never more than 3 lines each
- Main text progression and cases Progression method: question-and-answer style Common sentence patterns:
- "Here comes the question, ..."
- "Is Codex stronger? Is there evidence? Yes."
- "How do I use it?"
- "When should XXX be completely abandoned?" Case types: Type Usage Own practice "I use Google Antigravity as my main AI IDE, and inside it I simultaneously use..." Authoritative data Cite the coding capability score from the Artificial Analysis leaderboard Screenshot evidence Product screenshots, leaderboard screenshots Case types not to use:
- Do not tell the story of "I have a friend"
- Do not quote famous people's sayings
- Do not do emotional rendering
- Ending design Common pattern: brief call to action + fixed benefit tail Article Ending 1 "Go try it now! I look forward to your comments and feedback!" + benefit tail 2 "Looking forward to your feedback!" Core features:
- Extremely brief, do not summarize the whole article
- Use exclamation marks to create a sense of action
- Encourage interaction (comments and feedback)
- Fixed perk hook: "Reply 'card' to the official account to receive..."
- Language style and persona Persona positioning: the tech-savvy big brother / someone who's been there Dimension Feature Tone Friend-like, but with expert confidence Attitude Dares to make judgments, has opinions, doesn't sit on the fence Expression Direct, crisp, no waffle Interaction Dares to push back on readers (see comment replies) Signature expressions:
- "I suggest everyone..." "Today I want to invite everyone..."
- "TL;DR version"
- "A special friendly reminder:"
- "How should I put it, if... only one of the following two situations" Human touch embodied in:
- Admitting the tool has flaws ("It works slowly; slow work produces fine results")
- Admitting the switch has growing pains ("I've been trying it for two days, and it's been a bit painful")
- Teasing future updates ("If a stronger product comes out after a while, I'll let you know")
- Emotional hook Emotional curve design: Beginning: urgency/conflict ↓ "Give up XXX" "Starting today" Middle: trust/certainty ↓ Data support, authoritative rankings, personal practice Ending: sense of action/anticipation ↓ "Go try it now!" Key emotional trigger points:
- Use "give up" in the title to create decision conflict
- Use timeliness ("today" "updated") to create FOMO
- Use data and rankings to remove doubts
- Use "how I use it" to offer a path others can imitate
- Article type Type determination: opinion-style + tool recommendation-style Article Type Feature 1 Tool switch recommendation Opinion first + feature update + usage suggestions 2 Tool switch recommendation Opinion first + data support + scenario suggestions Not:
- Not a story-style piece (no complete story)
- Not a pure practical-tips piece (not a tutorial-style step by step)
- Not a breakdown piece (not analyzing someone else's case)
- Additional finding: comment section operation strategy Author reply features:
- Dares to directly rebut readers' doubts
- Responds with logic/data, doesn't sit on the fence
- Appropriately admits limitations, appearing sincere
- Pins key Q&A to reduce repeated questions
Step two: a replicable writing template [Tool switch recommendation style] universal template
[Title formula] Formula A: Give up [old tool], starting today! Formula B: At the same [price/condition], I now advise you to give up [old tool] and switch to [new tool] Formula C: Starting from [time point], [new tool] officially replaces [old tool] Fill-in examples:
- Give up Notion, starting today!
- At the same 99 yuan, I now advise you to give up XX course and switch to XX course
- Starting in 2025, Figma officially replaces Sketch
[Paragraph rhythm tips] Position Length Purpose Opening viewpoint 1-2 sentences Give the conclusion directly Quick-read version 3-5 items Cater to fast-reading users Data support 1 paragraph + chart Build trust Personal practice 1 paragraph + screenshot Provide an imitable path Scenario suggestions 2-3 paragraphs Solve "how should I choose" Ending 1 sentence Drive action [Key sentence patterns quick reference] Scenario Sentence pattern Opening "Today I want to invite everyone..." Turn "Here comes the problem..." Ask and answer yourself "XXX is stronger? Is there evidence? Yes." Personal practice "How do I use XXX?" Scenario suggestions "If you are using A and B at the same time, when should you consider switching completely?" Preview "If a stronger product appears after a while, I will tell you." Ending "Go try it now! I look forward to you coming back to leave feedback!"
Finally, in writing, it is absolutely not allowed to use any double quotation marks or em dashes in Chinese or English. To emphasize again, double quotation marks and em dashes are absolutely not allowed, and repeated bullet points should be avoided. Use short sentences and quick hits, and write in paragraphs as much as possible.
3. Generate images based on the generated article
Call generate_image() at least to generate no fewer than three images and insert them into the article. Pay attention to formatting; it must be standard markdown format.
4. Mix the article and images together
Insert the images into the article according to the article content. Note that you must create a new document and save it as a file named 标题.md.
Workflow example
The user provides an idea:
处理过程：
1. 写文章
2. 生成图片
3. 图文混排
4. 将混排后的文章保存到 标题.md，注意一定要新创建一个文档，并且保存为 标题.md 的文件