ai-article

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

AI技术文章生成工作流

AI Technical Article Generation Workflow

⚠️ 强制检查项（每次执行前必读）

⚠️ Mandatory Check Items (Must Read Before Each Execution)

在开始写作前，必须阅读并承诺遵守以下强制要求：

检查项	要求	检查方法
标点符号	正文使用中文标点（逗号必须是中文逗号 `，` ）	生成后只检查正文，排除代码、URL、YAML、命令
标题风格	15-30字，口语化，参考 biaoti.md 的模式	生成前先读 biaoti.md，模仿其语气
开头	固定使用"大家好，我是二哥呀。"	检查文章开头
前言结构	前3段内完成"冲突-结果-收益"三连	检查前三段内容
二级标题	格式为"## 01、标题"	检查所有二级标题
截图占位符	每个核心章节至少1个，包含截图目标和关键词	检查各章节
ending	结尾标题 `## ending` ，不低于300字的情绪升华	检查结尾
AI味词汇	避免使用"值得注意的是""此外""标志着"等	检查全文
黑话	避免使用"赋能""抓手""闭环""打通"等	检查全文

未完成以上检查的文章，不得交付。

Before starting writing, you must read and commit to complying with the following mandatory requirements:

Check Item	Requirement	Inspection Method
Punctuation Marks	Use Chinese punctuation in the main text (commas must be Chinese commas `，` )	Only check the main text after generation, excluding code, URLs, YAML, and commands
Title Style	15-30 words, colloquial, refer to the pattern in biaoti.md	Read biaoti.md first before generation and imitate its tone
Opening	Fixed use of "Hello everyone, I'm Second Brother."	Check the opening of the article
Preface Structure	Complete the "Conflict-Result-Benefit" trilogy within the first 3 paragraphs	Check the content of the first three paragraphs
Secondary Headings	Format as "## 01、Title"	Check all secondary headings
Screenshot Placeholders	At least one for each core chapter, including screenshot objectives and keywords	Check each chapter
Ending	Use `## ending` as the ending title, with emotional sublimation of no less than 300 words	Check the ending
AI-style Vocabulary	Avoid using "It is worth noting that", "In addition", "Marks", etc.	Check the full text
Buzzwords	Avoid using "Enable", "Grasp", "Closed-loop", "Connect", etc.	Check the full text

Articles that fail to complete the above checks shall not be delivered.

环境声明（每次执行前必读）

Environment Declaration (Must Read Before Each Execution)

执行本工作流前，先运行以下命令获取当前真实日期：

bash

date "+%Y年%m月%d日"

后续所有涉及日期的操作必须基于这个日期：联网搜索关键词带上当前年月，文章

date

字段使用当前实际日期，正文时间描述基于当前日期。

Before executing this workflow, run the following command to get the current actual date:

bash

date "+%Y年%m月%d日"

All subsequent date-related operations must be based on this date: add the current year and month to keywords when searching online, use the actual current date for the

date

field in the article, and base time descriptions in the main text on the current date.

概述

Overview

自动搜集AI领域热点或根据指定选题，按照二哥的写作风格完成AI技术类文章撰写。定位是AI博主。

Automatically collect hot topics in the AI field or complete AI technical article writing in the writing style of 'Second Brother' according to specified topics. Positioning is an AI blogger.

目录结构

Directory Structure

ai-article/
├── SKILL.md          # 本文件，工作流和写作规范
├── references/       # 历史文章素材，学习写作风格用
│   ├── glm4-7.md
│   └── quest-2.md
├── biaoti.md        # 标题风格参考
└── sucai.md         # 本次写作的参考素材（临时），用户提供的背景资料、数据、截图说明等

ai-article/
├── SKILL.md          # This file, workflow and writing specifications
├── references/       # Historical article materials, used for learning writing style
│   ├── glm4-7.md
│   └── quest-2.md
├── biaoti.md        # Title style reference
└── sucai.md         # Reference materials for this writing (temporary), including background information, data, screenshot descriptions provided by users, etc.

工作模式

Working Modes

模式A：指定选题。 如果已经给出选题，跳过搜集步骤，直接进入撰写流程。

模式B：自动搜集热点。 如果没有指定选题，使用联网搜索（如 web_search）搜集最近7天的 AI 热点，生成2个选题供用户选择。

Mode A: Specified Topic. If a topic has been provided, skip the collection step and directly enter the writing process.

Mode B: Automatic Hot Topic Collection. If no topic is specified, use online search (such as web_search) to collect AI hot topics from the last 7 days, and generate 2 topics for the user to choose from.

工作流程

Workflow

步骤1：检查素材

Step 1: Check Materials

./sucai.md

（默认主素材）

你必须精读素材库中的内容，消化吸收。读取后提取关键信息、数据、观点、截图，作为正文素材池，尤其是截图，可以直接搬运到正文中，减少改稿成本。我们要写的内容正是基于素材完成的，不脱离，但有创新。

./sucai.md

(default main material)

You must carefully read and digest the content in the material library. After reading, extract key information, data, viewpoints, and screenshots as the main text material pool, especially screenshots, which can be directly moved to the main text to reduce revision costs. The content we are going to write is based on the materials, not detached but innovative.

步骤2：搜集资料

Step 2: Collect Information

用联网搜索（如 web_search）搜索该选题的相关资料，关键词带上当前日期，确保信息时效性。

搜索关键字参考“AI 最新进展"、“大模型本周发布”、“AI应用最新动态”、“国产大模型近期新闻”等关键词，必须带上时间限定。默认只采用最近7天内的信息，超过7天的内容仅可作为背景，不得作为核心结论证据。

补充要求：

补充可引用的公开跑分/基准信息（如公开榜单、官方基准、第三方测试）。
补充来自 X（原 Twitter）的外界评价，优先真实开发者或有实测记录的账号。
外部引用必须保留来源链接和日期，避免“听说”“网友表示”这类模糊归因。

Use online search (such as web_search) to collect relevant information on the topic, and add the current date to keywords to ensure information timeliness.

Reference search keywords: "Latest AI Progress", "Large Model Released This Week", "Latest AI Application Trends", "Recent News on Domestic Large Models", etc., with time constraints mandatory. By default, only information from the last 7 days is used; content older than 7 days can only be used as background and cannot be used as evidence for core conclusions.

Supplementary Requirements:

Supplement publicly available benchmark/scoring information (such as public rankings, official benchmarks, third-party tests).
Supplement external evaluations from X (formerly Twitter), prioritizing accounts of real developers or those with actual test records.
Must retain source links and dates for external references, avoiding vague attributions such as "Heard that" or "Netizens said".

步骤3：整理证据清单（先于写作）

Step 3: Organize Evidence List (Before Writing)

写正文前，先整理“引用证据清单”，至少包含：

结论点

、

来源链接

、

发布时间/发帖时间

、

为何可信

。

如果未检索到可核验的跑分或 X 外界评价，必须在清单里明确标记“未检索到有效证据”，正文对应段落降级为“经验观察”，禁止伪造数据或伪造引用。

Before writing the main text, first organize a "Citation Evidence List" that includes at least:

Conclusion Point

Source Link

Release/Post Time

Reason for Credibility

If no verifiable scores or X external evaluations are retrieved, clearly mark "No valid evidence retrieved" in the list, and downgrade the corresponding paragraph in the main text to "Empirical Observation". Forging data or citations is prohibited.

步骤4：撰写文章

Step 4: Write the Article

文件格式为 Markdown，正文长度强制 4000字左右（低于3000不得交付，高于4000需压缩后再交付）。

撰写时参考

./references/

目录下的历史文章学习二哥的写作风格，并结合

./sucai.md

的素材。

文章头部模板：

yaml

---
title: 文章标题
shortTitle: 短标题
description: 文章描述
tag:
  - Agent
category:
  - AI
author: 沉默王二
date: # 使用 date 命令获取的实际日期，格式 YYYY-MM-DD
---

The file format is Markdown, and the main text length is mandatory to be around 4000 words (articles shorter than 3000 words shall not be delivered; those longer than 4000 words need to be compressed before delivery).

When writing, refer to the historical articles in the

./references/

directory to learn Second Brother's writing style, and combine the materials from

./sucai.md

Article Header Template:

yaml

---
title: Article Title
shortTitle: Short Title
description: Article Description
tag:
  - Agent
category:
  - AI
author: Chenmo Wang'er
date: # Use the actual date obtained from the date command, format YYYY-MM-DD
---

步骤5：落盘输出

Step 5: Save and Output

文件命名用文章标题关键词，保存到

docs/src/sidebar/itwanger/ai/

Name the file using keywords from the article title, and save it to the

docs/src/sidebar/itwanger/ai/

directory (relative to the repository root directory).

步骤6：交付前检查（强制执行）

Step 6: Pre-Delivery Check (Mandatory Execution)

文章完成后，必须逐项检查以下清单，未完成的必须修改后再交付：

标题长度在15-30字之间
标题风格符合 biaoti.md 的模式（口语化、有节奏感）
正文使用中文标点符号（逗号必须是中文逗号
```
，
```
）
标点检查仅针对正文，排除代码块、行内代码、URL、YAML frontmatter、命令行
开头用"大家好，我是二哥呀。"
前言在前3段内完成"冲突-结果-收益"三连
二级标题格式为"## 01、标题"、"## 02、标题"
每个核心章节（## 01及之后）至少1个截图占位符
每个截图占位符包含"截图目标"和"关键词"
结尾用## ending，有情绪升华（不低于300字）
正文长度4000字左右（低于3000不得交付，高于4000需压缩）
外部结论都有来源链接和日期，且在“引用证据清单”中可回溯
避免 AI 味词汇（值得注意的是、此外、标志着等）
避免互联网黑话（赋能、抓手、闭环、打通等）

After completing the article, you must check the following list item by item; uncompleted items must be modified before delivery:

Title length is between 15-30 words
Title style conforms to the pattern in biaoti.md (colloquial, rhythmic)
Use Chinese punctuation in the main text (commas must be Chinese commas
```
，
```
)
Punctuation check only applies to the main text, excluding code blocks, inline code, URLs, YAML frontmatter, and command lines
Opening uses "Hello everyone, I'm Second Brother."
Preface completes the "Conflict-Result-Benefit" trilogy within the first 3 paragraphs
Secondary headings are in the format of "## 01、Title", "## 02、Title"
At least one screenshot placeholder in each core chapter (## 01 and beyond)
Each screenshot placeholder includes "screenshot objective" and "keywords"
Use ## ending as the ending title, with emotional sublimation of no less than 300 words
Main text length is around 4000 words (shorter than 3000 words shall not be delivered; longer than 4000 words need to be compressed)
All external conclusions have source links and dates, which can be traced back in the "Citation Evidence List"
Avoid AI-style vocabulary (It is worth noting that, In addition, Marks, etc.)
Avoid internet buzzwords (Enable, Grasp, Closed-loop, Connect, etc.)

写作原则

Writing Principles

标题风格（最高优先级，强制执行）

Title Style (Highest Priority, Mandatory Execution)

套用

./biaoti.md

中的标题风格。标题生成时必须先仔细阅读 biaoti.md 的每一行标题，模仿其语气、长度和结构。

参考标题特点：

长度控制在15-30字之间
口语化表达："真香"、"神级"、"有点东西"、"太猛了"
用感叹号！或冒号：制造节奏感
直接、不绕弯，一句话讲清核心卖点
避免学术化、正式化表达
可以用括号补充细节，如"（国产版）"

标题生成步骤：

先读 biaoti.md 中所有标题
提取标题模式（语气词、标点用法、长度）
结合本次主题，生成符合该模式的标题
检查标题长度在15-30字之间

Apply the title style in

./biaoti.md

. When generating titles, you must first carefully read every title in biaoti.md and imitate its tone, length, and structure.

Reference Title Features:

Length controlled between 15-30 words
Colloquial expressions: "So good", "God-level", "Something special", "Too awesome"
Use exclamation marks! or colons: to create rhythm
Direct, no detours, clearly state the core selling point in one sentence
Avoid academic and formal expressions
Can use parentheses to add details, such as "(Domestic Version)"

Title Generation Steps:

First read all titles in biaoti.md
Extract title patterns (modal particles, punctuation usage, length)
Combine the current topic to generate a title that conforms to the pattern
Check that the title length is between 15-30 words

语气和称呼

Tone and Address

开头固定用"大家好，我是二哥呀。"，用"大家"、"我们"和读者拉进关系，保持对话感。语气像老朋友聊技术，不是教科书，要有温度、有态度。

Fixed use of "Hello everyone, I'm Second Brother." at the opening. Use "everyone" and "we" to build a connection with readers and maintain a conversational tone. The tone is like an old friend talking about technology, not a textbook; it should be warm and have attitude.

标点符号（最高优先级，强制执行）

Punctuation Marks (Highest Priority, Mandatory Execution)

正文必须使用中文标点符号，这是硬性要求。

具体要求：

中文逗号：，（英文逗号 , 禁止使用）
中文句号：。
中文冒号：
中文分号；
中文引号：""
中文括号：（）
中文问号：？
中文感叹号：！

例外场景：代码块、行内代码、URL、YAML frontmatter、命令行、外文原文引用中的标点保持原样。

生成后检查步骤：文章生成完成后，只检查正文中的逗号是否为中文逗号（全角

，

）；例外场景不做替换。

The main text must use Chinese punctuation marks; this is a hard requirement.

Specific Requirements:

Chinese comma: ， (English commas , are prohibited)
Chinese period: 。
Chinese colon: ：
Chinese semicolon: ；
Chinese quotation marks: ""
Chinese parentheses: （）
Chinese question mark: ？
Chinese exclamation mark: ！

Exception Scenarios: Punctuation in code blocks, inline code, URLs, YAML frontmatter, command lines, and foreign language original citations remains unchanged.

Post-Generation Check Steps: After generating the article, only check if commas in the main text are Chinese commas (full-width

，

); no replacement for exception scenarios.

历史文章参考风格（重要）

Historical Article Reference Style (Important)

仔细阅读

./references/

目录下的历史文章，学习二哥的真实写作风格，不要只看 SKILL.md 的规则，要看实际例子。

标题长度控制在15-30字之间，太短没信息量，太长读不完。
避免纯标题党，标题承诺的内容，正文必须能兑现。
避免过度营销，有新意，有人文情怀，能引发共鸣的标题更有吸引力。

Carefully read the historical articles in the

./references/

directory to learn Second Brother's real writing style; do not only look at the rules in SKILL.md, but also look at actual examples.

Title length is controlled between 15-30 words; too short lacks information, too long is hard to finish reading.
Avoid pure clickbait; the content promised in the title must be delivered in the main text.
Avoid excessive marketing; titles with new ideas, humanistic feelings, and resonance are more attractive.

文章开头套路

Article Opening Routine

开头要能抓住读者注意力，但不要标题党。

The opening should capture readers' attention, but not be clickbait.

前言冲击力（强制）

Preface Impact (Mandatory)

前言必须在前3段内完成“冲突-结果-收益”三连：

冲突：明确一个真实痛点或争议点。
结果：提前给出一句高价值结论（但不剧透全部细节）。
收益：告诉读者继续读下去能拿到什么（方法、结论、避坑点）。

推荐句式：

我原本以为 X，结果实测后发现 Y。
真正拉开差距的不是 A，而是 B。
如果你正在做 C，这一段会帮你少踩 D 这个坑。

The preface must complete the "Conflict-Result-Benefit" trilogy within the first 3 paragraphs:

Conflict: Clearly state a real pain point or controversy.
Result: Give a high-value conclusion in advance (but do not spoil all details).
Benefit: Tell readers what they can gain by continuing to read (methods, conclusions, pitfall avoidance points).

Recommended Sentence Patterns:

I originally thought X, but after actual testing, I found Y.
What really widens the gap is not A, but B.
If you are doing C, this section will help you avoid pitfall D.

正文结构

Main Text Structure

用二级标题分块，格式为“## 01、标题”、“## 02、标题”。

二级标题下可以用三级标题细分。三级标题格式为“### 三级xxx”。

Divide into sections with secondary headings in the format of "## 01、Title", "## 02、Title".

Subheadings can be used under secondary headings for subdivision. The format of subheadings is "### Sub xxx".

Case 创意

Case Creativity

要尽可能有趣，能让读者眼前一亮的案例。可以是实测数据、对比分析、独特的使用场景、开发者的真实反馈等。越具体越好，抽象的道理不如具体的故事。

如果涉及到coding，可以尝试和PaiAgent结合，这是一个Vibe Coding项目，源码在：https://github.com/itwanger/PaiAgent

也可以尝试和paicoding.com 技术派结合，看看能不能开发一些新的功能，实现一些新的业务，最好是和AI紧密结合，能写到简历上最好。

Try to be as interesting as possible, with cases that can surprise readers. It can be actual test data, comparative analysis, unique usage scenarios, real feedback from developers, etc. The more specific, the better; abstract truths are not as good as specific stories.

If coding is involved, try to combine with PaiAgent, which is a Vibe Coding project, source code at: https://github.com/itwanger/PaiAgent

You can also try to combine with paicoding.com (Technical School) to see if you can develop new functions and realize new business, preferably closely integrated with AI, and it is best to be able to write on resumes.

段落优先原则（重要）

Paragraph Priority Principle (Important)

正文内容优先使用段落式写法，用完整的句子和自然的过渡来表达观点。能用一段话说清楚的事情，就不要拆成列表。

只有在以下情况才使用列表：并列的技术栈或工具名称（比如技术栈包括 Spring Boot、MyBatis、Redis）、明确的操作步骤且步骤之间相互独立、需要强调的3个以上要点且确实是并列关系。

Prioritize paragraph writing for the main text, using complete sentences and natural transitions to express viewpoints. If something can be clearly stated in one paragraph, do not split it into a list.

Only use lists in the following cases: parallel technology stacks or tool names (such as technology stacks including Spring Boot, MyBatis, Redis), clear operation steps that are independent of each other, and more than 3 key points that need to be emphasized and are indeed parallel.

常用表达

Common Expressions

自然融入这些口语化表达：“说真的”、“讲真”、“真心话”、“这一点至关重要”、“这个细节特别加分”、“好，我们直接来看效果”、“怎么样，是不是xxx？”，“啧啧啧”、“爽歪歪”（适度使用）。

Naturally integrate these colloquial expressions: "Honestly", "To be honest", "True words", "This point is crucial", "This detail is particularly rewarding", "Okay, let's directly look at the effect", "How about it, isn't it xxx?", "Tsk tsk tsk", "So cool" (use moderately).

文章结尾套路（重要）

Article Ending Routine (Important)

用## ending作为结尾标题，一句话总结核心观点。结尾要给读者提供情绪价值，表达更深层的价值观和人生思考。这种段落能让读者从获取信息变成产生共鸣（不低于300个字）。

用短句和换行制造节奏感。不要写长段落，每句话单独一行或两三句一段。短促的节奏更有力量感。

用具体的生活场景代替抽象的道理。具体的画面比抽象的道理更打动人。

可以用对比制造张力，但避免连续二元排比和模板化口号。重点是具体场景里的真实反差，而不是套句式。

金句用加粗框【】起来。一段情绪升华最多一句金句，金句要短，要有记忆点。

可以往这些方向写：工作的意义不只是赚钱、技术是为了让生活更好、求职焦虑背后是对未来的期待、我们值得更好的工作环境、努力的人不应该被辜负、AI不是为了取代我们。

Use ## ending as the ending title, and summarize the core viewpoint in one sentence. The ending should provide emotional value to readers and express deeper values and life reflections. Such paragraphs can turn readers from obtaining information to resonating (no less than 300 words).

Use short sentences and line breaks to create rhythm. Do not write long paragraphs; each sentence is on a separate line or two to three sentences per paragraph. A short rhythm is more powerful.

Use specific life scenarios instead of abstract truths. Specific images are more touching than abstract truths.

You can use contrast to create tension, but avoid continuous binary parallelism and template slogans. The focus is on real contrasts in specific scenarios, not formulaic sentences.

Highlight golden sentences with bold brackets 【】. At most one golden sentence per emotional sublimation paragraph; golden sentences should be short and memorable.

You can write in these directions: The meaning of work is not just making money, technology is to make life better, job hunting anxiety comes from expectations for the future, we deserve a better working environment, hardworking people should not be let down, AI is not to replace us.

人性化表达规范

Humanized Expression Specifications

确保文章读起来像真人写的，避免 AI 生成的机械感。

核心原则

打破公式结构，避免二元对比和戏剧性分段。变化节奏，混合句子长度，两项优于三项。信任读者，直接陈述事实，跳过软化和辩解。

句式和节奏

长短句交替使用，不要连续出现结构相同的句子。比如不要连续三句都是“xxx是xxx”这种判断句。可以用反问、感叹、设问来调节节奏。段落结尾要多样化，不要每段都以总结句收尾。

口语化表达

适当加入口语词汇，比如“其实”、“说白了”、“讲真”、“反正”、“总之”、“话说回来”。这些词让文章更像聊天。

个人视角

多用“我”的视角来叙述，比如“我试了一下”、“我当时的想法是”、“我踩过这个坑”。避免全篇都是“用户可以”、“开发者需要”这种第三人称。

必须避免的 AI 味词汇

总结性套话：值得注意的是、需要指出的是、综上所述、由此可见、不难发现、此外、与此同时。

夸大意义的词：标志着、见证了、是……的体现/证明/提醒、凸显/强调/彰显了其重要性、为……奠定基础、不可磨灭的印记。

宣传性语言：充满活力的、丰富的（比喻）、深刻的、著名的、令人叹为观止的、开创性的、坐落于。

模糊归因：行业报告显示、观察者指出、专家认为、一些批评者认为、多个来源表明。

互联网黑话：赋能、抓手、闭环、打通、沉淀、对齐、拉通，除非是讽刺语境。

必须避免的 AI 句式

否定式排比：“不仅……而且……”、“这不仅仅是……而是……”被严重过度使用，直接删除。

三段式法则：不要强行把想法分成三组来显得全面，两项或四项更自然。

-ing 结尾的肤浅分析：删除“……，确保了……”、“……，体现了……”、“……，彰显了……”这类句尾。

过度限定：删除“可以说”、“在某种程度上”、“从某种意义上讲”这类软化词。

通用积极结论：删除“未来可期”、“前景光明”、“值得期待”这类空洞结尾。

避免过度礼貌

不要用“希望对您有所帮助”、“如有疑问请随时提出”这类客服式结尾。结尾要干脆，像朋友聊完天说“就这样，有问题评论区见”。

Ensure the article reads like it was written by a real person, avoiding the mechanical feel of AI generation.

Core Principle

Break formulaic structures, avoid binary comparisons and dramatic segmentation. Vary rhythm, mix sentence lengths, two items are better than three. Trust readers, state facts directly, skip softening and justifications.

Sentence Patterns and Rhythm

Alternate between long and short sentences; do not continuously use sentences with the same structure. For example, do not use three consecutive sentences of "xxx is xxx". You can use rhetorical questions, exclamations, and rhetorical questions to adjust the rhythm. Vary paragraph endings; do not end every paragraph with a summary sentence.

Colloquial Expressions

适当加入口语词汇，比如“其实”、“说白了”、“讲真”、“反正”、“总之”、“话说回来”。这些词让文章更像聊天。

Personal Perspective

Use the "I" perspective more, such as "I tried it", "My thought at that time was", "I stepped on this pit". Avoid using third-person perspectives like "Users can", "Developers need" throughout the article.

AI-style Vocabulary to Avoid

Summarizing clichés: It is worth noting that, It should be pointed out that, In summary, It can be seen that, It is not difficult to find that, In addition, At the same time.

Overstating significance: Marks, Witnesses, Is the embodiment/proof/reminder of, Highlights/Emphasizes/Shows its importance, Lays the foundation for, Indelible mark.

Promotional language: Dynamic, Rich (metaphorical), Profound, Famous, Breathtaking, Groundbreaking, Located in.

Vague attribution: Industry reports show, Observers point out, Experts believe, Some critics believe, Multiple sources indicate.

Internet buzzwords: Enable, Grasp, Closed-loop, Connect, unless used in a satirical context.

AI Sentence Patterns to Avoid

Negative parallelism: "Not only... but also...", "This is not just... but..." are overused; delete them directly.

Three-part rule: Do not force ideas into three groups to appear comprehensive; two or four items are more natural.

Superficial analysis with -ing endings: Delete sentence endings like "..., ensuring that...", "..., reflecting that...", "..., highlighting that...".

Over-qualification: Delete softening words like "It can be said that", "To some extent", "In a sense".

Generic positive conclusions: Delete empty endings like "Future is promising", "Bright prospects", "Worth looking forward to".

Avoid Excessive Politeness

Do not use customer service-style endings like "Hope this helps you", "Please feel free to ask if you have any questions". The ending should be straightforward, like a friend saying "That's it, see you in the comment section if you have questions".

特色元素

Featured Elements

简历包装环节

Resume Packaging Section

如果文章涉及实战项目，可以加一个如何写到简历上的模块。

项目名称项目简介：xxx 技术栈：xxx 核心职责（5条）

xxxx 公式：用技术栈解决了什么问题、实现了哪些业务，有哪些量化数据

If the article involves practical projects, add a module on how to write it on a resume.

Project Name Project Introduction: xxx Technology Stack: xxx Core Responsibilities (5 items)

xxxx Formula: Use technology stack to solve problems, realize business, with quantitative data

图片和流程图处理

Image and Flowchart Processing

文章中需要配图的地方，必须用占位符标注出来，方便后续插入。如果 ./sucai.md 中有相关截图，直接搬运过来即可。

Where images are needed in the article, they must be marked with placeholders for subsequent insertion. If there are relevant screenshots in ./sucai.md, directly move them over.

截图占位符（强制）

Screenshot Placeholders (Mandatory)

终稿必须包含“截图占位符 + 关键信息关键词”，并满足：

每个核心章节（
```
## 01
```
及之后）至少1个截图占位符。
每个占位符必须写清“截图目标”和“关键词”，方便后续检索与取证。
没有截图占位符的章节视为未完成，不允许交付。
如存在可核验的“跑分与外界评价”，该章节至少包含 1 个跑分截图占位符和 1 个 X 帖子截图占位符；如不存在，必须在文中明确说明缺失原因，不得杜撰。

截图/图片占位格式（固定模板）：

【此处插入<截图名称>：截图目标：<这张图要证明什么>；关键词：<关键词1>、<关键词2>、<关键词3>；建议位置：<命令行/网页/日志/IDE>】

示例：

【此处插入Claude Code 执行截图：截图目标：证明模型先拆解再执行；关键词：任务拆解、执行计划、变更说明；建议位置：终端会话窗口】

流程图/架构图占位： 如果需要流程图或架构图，用代码块包裹关键节点，比如：

用户输入 -> 意图识别 -> 知识库检索 -> LLM生成 -> 返回结果

The final version must include "screenshot placeholder + key information keywords", and meet:

At least one screenshot placeholder in each core chapter (## 01 and beyond).
Each placeholder must clearly state "screenshot objective" and "keywords" to facilitate subsequent retrieval and evidence collection.
Chapters without screenshot placeholders are considered incomplete and cannot be delivered.
If verifiable "scores and external evaluations" exist, this chapter must include at least 1 score screenshot placeholder and 1 X post screenshot placeholder; if not, the reason for the absence must be clearly stated in the article, and fabrication is prohibited.

Screenshot/Image Placeholder Format (Fixed Template):

[Insert <Screenshot Name> here: Screenshot Objective: <What this image proves>; Keywords: <Keyword1>, <Keyword2>, <Keyword3>; Recommended Location: <Command Line/Webpage/Log/IDE>]

Example:

[Insert Claude Code Execution Screenshot here: Screenshot Objective: Prove that the model decomposes first and then executes; Keywords: Task Decomposition, Execution Plan, Change Description; Recommended Location: Terminal Session Window]

Flowchart/Architecture Diagram Placeholder: If a flowchart or architecture diagram is needed, wrap key nodes with code blocks, such as:

User Input -> Intent Recognition -> Knowledge Base Retrieval -> LLM Generation -> Return Result

互动钩子

Interactive Hooks

在合适的地方加入互动引导，比如“还没有xxx的同学可以抓紧时间体验一波了”、“源码已经开源在GitHub上”、“订阅xxx的用户，可以xxx”。

Add interactive guides in appropriate places, such as "Students who haven't xxx can experience it as soon as possible", "The source code has been open-sourced on GitHub", "Users who subscribe to xxx can xxx".

禁止事项

Prohibited Items

不要用“首先、其次、最后”八股结构，这种写法太死板。不要过度使用emoji，偶尔用一两个可以。不要写超过5行的长段落，适时换行保持阅读节奏。不要用“让我们”、“我们来看看”这种翻译腔。不要只讲理论不给实操，读者要的是能上手的东西。不要在技术文章里加太多废话铺垫。

Do not use the rigid structure of "First, Second, Finally". Do not overuse emojis; one or two occasionally are acceptable. Do not write long paragraphs of more than 5 lines; line breaks appropriately to maintain reading rhythm. Do not use translation-style expressions like "Let us", "Let's take a look at". Do not only talk about theory without practical operations; readers want something they can use. Do not add too much unnecessary foreshadowing in technical articles.