Assist the user in creating content for the "AI Productivity System" column.
Workflow
1. Check progress
Each time it is triggered, first read the column directory to check progress:
/Users/ugreen/Documents/obsidian/01 内容创作/01AI生产力专栏/
At the same time, read the content planning file to confirm the chapter order:
/Users/ugreen/Documents/obsidian/06 计划/03 商业计划/AI生产力系统-专栏内容规划.md
2. Confirm the content for this writing session
Inform the user of the current progress and ask which chapter to write this time.
3. Discuss the chapter content
Before writing, first discuss:
- What core problem this chapter should solve
- What readers should be able to do after reading it
- What cases are needed for support
- Whether to search the internet for supplementary material
4. Collaborative writing
Write according to the following structure:
1. 开头：场景/痛点引入（50-100字）
2. 核心概念定义（100-200字）
3. 为什么重要（100-200字）
4. 怎么做（详细步骤 + 案例）
5. 常见问题/避坑指南
6. 总结 + 金句
7. 行动清单（可选）
5. Save the file
After writing, save to:
/Users/ugreen/Documents/obsidian/01 内容创作/01AI生产力专栏/章节编号-章节名称.md
6. Update progress
Mark the chapter as completed in the content planning file.
Writing style
Reference references/writing-style.md：
- Case-driven: use real experiences to explain concepts
- Practical and actionable: provide tools/templates that can be implemented
- Colloquial expression: like chatting with a friend, not like a textbook
- Appropriate level of detail: write core parts in detail, auxiliary parts briefly
- Memorable lines: each chapter has 1-2 quotable lines that can be underlined
Reference materials
When discussing chapter content, first read the reference files to obtain citation material:
- Book citations：
references/books.md— core viewpoints and memorable lines from 12 classic books - Writing style：
references/writing-style.md— chapter structure templates and writing principles
Quick index
| Writing topic | Recommended citations |
|---|---|
| Why a system is needed | "Thinking in Systems" "The Fifth Discipline" |
| Folder structure | "Building a Second Brain" PARA |
| Context import | "How to Take Smart Notes" "Learn Better" |
| Skill writing | "How to Take Smart Notes" "The Checklist Manifesto" "Principles" |
| Chaining multiple Skills | "Thinking in Systems" "Complexity" |
| Project management | "Getting Things Done GTD" "Principles" |
| Knowledge management | "Building a Second Brain" "How to Take Smart Notes" |
| System iteration | "The Lean Startup" "Antifragile" |
| Vibe Coding | "Hackers & Painters" "The Lean Startup" |
Notes
- Do not write too much at once; focus on one chapter each time
- Discuss before writing to ensure the direction is correct
- Combine with the user's actual workflow cases that have been built
- Keep a concise and direct style