save-idea

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

save-idea

Capture one thing fast, then get out of the way. Seven buckets, seven files, ONE repo (

<ideas-repo>

Bucket	File	What belongs there
Video idea	`<ideas-repo>/VIDEO-IDEAS.md`	A concept big enough for a full video
Topic	`<ideas-repo>/TOPICS.md`	Smaller stuff: podcast topics, guests, questions, AI observations
Marketing idea	`<ideas-repo>/MARKETING-IDEAS.md`	Marketing and distribution: how we get products in front of people
Startup idea	`<ideas-repo>/STARTUP-IDEAS.md`	A business/product idea — a candidate for the user's next startup
Conviction	`<ideas-repo>/CONVICTIONS.md`	A belief the user is CERTAIN about on AI-era building (startups, AI industry, agentic coding) — a conviction, not an idea
Mini project	`<ideas-repo>/mini-projects.md`	A small technical/cool project to build — just cool shit, not a startup candidate
Article idea	`<ideas-repo>/ARTICLE-IDEAS.md`	A topic for the user's daily public articles (X, blog, YouTube community, email)

Note: a technical insight can go in the startup bucket too — some technical insights could lead to a startup idea. A cool thing to build that is NOT a business idea goes in mini projects.

快速捕捉单个内容，随后退出操作。七个分类，七个文件，统一存入一个仓库（

<ideas-repo>

）：

分类	文件	存入内容
视频想法	`<ideas-repo>/VIDEO-IDEAS.md`	足以支撑完整视频的概念
主题内容	`<ideas-repo>/TOPICS.md`	小型内容：播客主题、嘉宾人选、问题、AI相关观察
营销想法	`<ideas-repo>/MARKETING-IDEAS.md`	营销与推广：如何将产品推向受众
创业想法	`<ideas-repo>/STARTUP-IDEAS.md`	商业/产品想法——可能成为用户下一个创业项目的候选
坚定信念	`<ideas-repo>/CONVICTIONS.md`	用户对AI时代构建（创业、AI行业、智能体编码）的笃定信念——是信念，而非想法
小型项目	`<ideas-repo>/mini-projects.md`	小型技术类/有趣的项目——仅为有趣的创意，而非创业候选项目
文章想法	`<ideas-repo>/ARTICLE-IDEAS.md`	用户日常发布文章的主题（X平台、博客、YouTube社区、邮件）

注意：技术见解也可存入创业分类——部分技术见解可能催生创业想法。不属于商业想法的有趣创意项目存入小型项目分类。

Workflow

工作流程

Get the text. Everything after
```
/save-idea
```
is the entry. Keep the user's wording verbatim — never rephrase, shorten, or "improve" it. (One exception: startup ideas get tightened per their repo's rules — see step 4.)
Route it.
- Starts with
```
video:
```
  → video idea (strip the prefix).
- Starts with
```
topic:
```
  → topic (strip the prefix).
- Starts with
```
marketing:
```
  → marketing idea (strip the prefix).
- Starts with
```
startup:
```
  → startup idea (strip the prefix).
- Starts with
```
mini:
```
  → mini project (strip the prefix).
- Starts with
```
article:
```
  → article idea (strip the prefix).
- Convictions have NO prefix (deliberate, the user's decision 2026-08-18) — route them by judgment only.
- No prefix → judge: a belief stated as a certainty about AI-era building (startups, AI industry, agentic coding) → conviction; business/product idea → startup idea; a small technical/cool project to build (not a company) → mini project; a way to get an existing product in front of people → marketing idea; full video concept → video idea; smaller thought or observation → topic. Only if genuinely ambiguous, ask the user one short question.
Read the target file and find the last entry number. Next number = last + 1.
- ```
TOPICS.md
```
  ,
```
MARKETING-IDEAS.md
```
  ,
```
ARTICLE-IDEAS.md
```
  ,
```
CONVICTIONS.md
```
  , and
```
mini-projects.md
```
  start at 1.
```
VIDEO-IDEAS.md
```
  continues from an old Google Doc.
- ```
STARTUP-IDEAS.md
```
  : continue from the last idea in the STARTUP IDEAS list. Gaps in its numbering are normal — discarded ideas live in
```
startup/review/DISCARDED.md
```
  , which has its own separate numbering. Ignore it; never reuse a gap number.
- Never renumber anything.
Append the entry.
- Video ideas, topics, marketing ideas & article ideas — append at the bottom of the file, wording verbatim, context lines tab-indented under the numbered line:

NNNN. Idea title exactly as the user said it
	source: <repo>, Cursor chat "Chat title", 2026-07-15
	any extra links or notes the user gave

Startup ideas — insert after the last numbered idea, keeping the trailing
```
----
```
separator and discarded-ideas note as the last lines of the file. Format per
```
<ideas-repo>/startup/AGENTS.md
```
: one tight entry,
```
N. Title — one-line explanation.
```
Rewrite for clarity and concision but stay loyal to the user's wording and voice. Blank line between entries. Source line indented with 4 spaces (that file uses spaces, not tabs):

69. Idea title — one-line explanation in the user's voice.
    - source: <repo>, Cursor chat "Chat title", 2026-08-01

Convictions — append at the bottom of
```
CONVICTIONS.md
```
, same tight style as startup ideas:
```
N. Punchy conviction — one-line why.
```
Tighten for punch but stay loyal to the user's wording and voice. Blank line between entries, source line indented with 4 spaces:

1. Punchy conviction — one-line why.
    - source: <repo>, Cursor chat "Chat title", 2026-08-18

Mini projects — append at the bottom of
```
mini-projects.md
```
, wording verbatim. Blank line between entries. Source line indented with 4 spaces (that file uses spaces, not tabs):

10. Idea title exactly as the user said it
    - source: <repo>, Cursor chat "Chat title", 2026-08-24

Build the source line.
- Repo: the folder the skill was invoked from, as
```
~/...
```
  path (check
```
git rev-parse --show-toplevel
```
  ; if not a repo, use the cwd).
- Chat: agent name plus chat title or session ID if the runtime exposes one (e.g.
```
Cursor chat "Fixing task sync"
```
  ,
```
Claude Code session abc123
```
  ). If unknown, just the agent name.
- Date: today, YYYY-MM-DD.
Commit and push the repo. Always use
```
git -C
```
so the current working directory never matters — never
```
cd
```
, never launch another agent for this:

bash

git -C <ideas-repo> pull --rebase --autostash origin main
git -C <ideas-repo> add VIDEO-IDEAS.md TOPICS.md MARKETING-IDEAS.md ARTICLE-IDEAS.md STARTUP-IDEAS.md CONVICTIONS.md mini-projects.md
git -C <ideas-repo> commit -m "Add idea 4839 on graph engineering video"
git -C <ideas-repo> push origin main

Stage ONLY the idea file(s) you touched. Never
```
git add -A
```
— unrelated work must not get swept in.

Commit message:

Add idea NNNN on <short description>

(or

Add topic NNNN on ...

Add marketing idea NN on ...

Add startup idea NN on ...

Add conviction NN on ...

Add mini project NN on ...

). Multiple entries → list the numbers.

If the pull or push fails, report the exact error to the user and stop. Never force-push.

Confirm back to the user: the exact entry text, its number, which file it went to, and that it was pushed.

获取文本：
```
/save-idea
```
之后的所有内容即为条目内容。完全保留用户的措辞——绝不改写、缩短或“优化”内容。（唯一例外：创业想法需根据其仓库规则精简——见步骤4。）
分类路由：
- 以
```
video:
```
  开头 → 视频想法（移除前缀）。
- 以
```
topic:
```
  开头 → 主题内容（移除前缀）。
- 以
```
marketing:
```
  开头 → 营销想法（移除前缀）。
- 以
```
startup:
```
  开头 → 创业想法（移除前缀）。
- 以
```
mini:
```
  开头 → 小型项目（移除前缀）。
- 以
```
article:
```
  开头 → 文章想法（移除前缀）。
- 坚定信念无前缀（用户于2026-08-18特意设定）——仅通过判断进行分类。
- 无前缀 → 判断分类：若为关于AI时代构建（创业、AI行业、智能体编码）的笃定信念 → 坚定信念；若为商业/产品想法 → 创业想法；若为小型技术类/有趣的项目（非公司项目）→ 小型项目；若为现有产品的推广方式 → 营销想法；若为完整视频概念 → 视频想法；若为小型想法或观察 → 主题内容。仅当确实存在歧义时，向用户提出一个简短问题。
读取目标文件并找到最后一条条目的编号。下一个编号 = 最后编号 + 1。
- ```
TOPICS.md
```
  、
```
MARKETING-IDEAS.md
```
  、
```
ARTICLE-IDEAS.md
```
  、
```
CONVICTIONS.md
```
  和
```
mini-projects.md
```
  从编号1开始。
```
VIDEO-IDEAS.md
```
  延续旧Google文档的编号。
- ```
STARTUP-IDEAS.md
```
  ：延续STARTUP IDEAS列表中的最后一个想法编号。编号存在间隔是正常情况——已废弃的想法存于
```
startup/review/DISCARDED.md
```
  ，该文件有独立编号体系。忽略间隔，绝不复用空缺编号。
- 绝不重新编号任何内容。
追加条目：
- 视频想法、主题内容、营销想法及文章想法——追加至文件底部，完全保留原措辞，上下文行缩进在编号行下方：

NNNN. 完全保留用户表述的想法标题
	source: <repo>, Cursor chat "聊天标题", 2026-07-15
	用户提供的额外链接或备注

创业想法——插入至最后一条编号想法之后，保留末尾的
```
----
```
分隔符和废弃想法说明作为文件最后一行。按照
```
<ideas-repo>/startup/AGENTS.md
```
的格式：简洁条目，
```
N. 标题 — 一行说明。
```
为清晰简洁改写，但需忠实于用户的措辞和语气。条目之间留空行。来源行使用4个空格缩进（该文件使用空格而非制表符）：

69. 想法标题 — 符合用户语气的一行说明。
    - source: <repo>, Cursor chat "聊天标题", 2026-08-01

坚定信念——追加至
```
CONVICTIONS.md
```
底部，格式与创业想法一致：
```
N. 有力的信念表述 — 一行理由说明。
```
精简表述以增强冲击力，但需忠实于用户的措辞和语气。条目之间留空行，来源行使用4个空格缩进：

1. 有力的信念表述 — 一行理由说明。
    - source: <repo>, Cursor chat "聊天标题", 2026-08-18

小型项目——追加至
```
mini-projects.md
```
底部，完全保留原措辞。条目之间留空行。来源行使用4个空格缩进（该文件使用空格而非制表符）：

10. 完全保留用户表述的想法标题
    - source: <repo>, Cursor chat "聊天标题", 2026-08-24

生成来源行：
- 仓库：调用该技能时所在的文件夹，格式为
```
~/...
```
  路径（可通过
```
git rev-parse --show-toplevel
```
  获取；若不在仓库中，则使用当前工作目录）。
- 聊天：智能体名称加上聊天标题或会话ID（若运行时提供）（例如
```
Cursor chat "修复任务同步"
```
  ,
```
Claude Code session abc123
```
  ）。若未知，则仅填写智能体名称。
- 日期：当天日期，格式为YYYY-MM-DD。
提交并推送仓库。始终使用
```
git -C
```
命令，确保当前工作目录不影响操作——绝不使用
```
cd
```
，绝不为此调用其他智能体：

bash

git -C <ideas-repo> pull --rebase --autostash origin main
git -C <ideas-repo> add VIDEO-IDEAS.md TOPICS.md MARKETING-IDEAS.md ARTICLE-IDEAS.md STARTUP-IDEAS.md CONVICTIONS.md mini-projects.md
git -C <ideas-repo> commit -m "Add idea 4839 on graph engineering video"
git -C <ideas-repo> push origin main

仅暂存你修改过的想法文件。绝不使用
```
git add -A
```
——避免纳入无关工作内容。

提交信息：

Add idea NNNN on <简短描述>

（或

Add topic NNNN on ...

Add marketing idea NN on ...

Add startup idea NN on ...

Add conviction NN on ...

Add mini project NN on ...

）。若有多条条目，列出所有编号。

若拉取或推送失败，向用户报告确切错误并停止操作。绝不强制推送。

向用户确认：告知用户确切的条目文本、编号、存入的文件以及已完成推送。

Rules

规则

Append only. Never edit, reorder, or renumber existing entries.
Multiple ideas in one invocation → one numbered entry each.
Committing and pushing the idea files is REQUIRED and pre-authorized by the user (26-07-2026; startup bucket 01-08-2026; convictions bucket 18-08-2026; mini-projects bucket 24-08-2026). This is a deliberate exception to the global "never push to GitHub by yourself" rule in
```
<global-agents-file>
```
. Do not "fix" this back — the whole point is that the user never has to commit idea entries by hand.
The exception covers
```
VIDEO-IDEAS.md
```
,
```
TOPICS.md
```
,
```
MARKETING-IDEAS.md
```
,
```
ARTICLE-IDEAS.md
```
(added 26-08-2026),
```
STARTUP-IDEAS.md
```
,
```
CONVICTIONS.md
```
, and
```
mini-projects.md
```
only. Any other change in the repo is still the user's to commit.
All idea capture was centralized into
```
<ideas-repo>
```
on 2026-08-14 (the user's decision). The old
```
<old-startup-repo>
```
repo is frozen pending archive — NEVER write or push there. Startup support material now lives in
```
<ideas-repo>/startup/
```
.
NEVER write to
```
<ideas-repo>/startup/review/DISCARDED.md
```
— only the user moves ideas there.
If
```
TOPICS.md
```
or
```
MARKETING-IDEAS.md
```
is missing, recreate it with its one-line header, then append entry 1.
If
```
mini-projects.md
```
is missing, recreate it with its header (
```
# MINI PROJECTS
```
plus the one-line quote about cool shit to build), then append entry 1.

Indent context lines to match the target file: real tabs in

VIDEO-IDEAS.md

TOPICS.md

, and

MARKETING-IDEAS.md

, 4 spaces in

STARTUP-IDEAS.md

CONVICTIONS.md

, and

mini-projects.md

仅允许追加。绝不编辑、重新排序或重新编号现有条目。
单次调用中包含多个想法时，每个想法对应一条编号条目。
提交并推送想法文件是必需操作，且已获得用户预先授权（2026-07-26；创业分类2026-08-01；信念分类2026-08-18；小型项目分类2026-08-24）。这是对
```
<global-agents-file>
```
中“绝不自行推送至GitHub”全局规则的特意例外。请勿“修正”此规则——核心目的是让用户无需手动提交想法条目。
该例外仅适用于
```
VIDEO-IDEAS.md
```
、
```
TOPICS.md
```
、
```
MARKETING-IDEAS.md
```
、
```
ARTICLE-IDEAS.md
```
（2026-08-26新增）、
```
STARTUP-IDEAS.md
```
、
```
CONVICTIONS.md
```
和
```
mini-projects.md
```
。仓库中的任何其他修改仍需用户自行提交。
所有想法捕捉于2026-08-14集中至
```
<ideas-repo>
```
（用户决定）。旧仓库
```
<old-startup-repo>
```
已冻结待归档——绝不向其中写入或推送内容。创业相关支持材料现存放于
```
<ideas-repo>/startup/
```
。
绝不向
```
<ideas-repo>/startup/review/DISCARDED.md
```
写入内容——仅用户可将想法移至此处。
若
```
TOPICS.md
```
或
```
MARKETING-IDEAS.md
```
缺失，重新创建并添加一行标题，随后追加编号1的条目。
若
```
mini-projects.md
```
缺失，重新创建并添加标题（
```
# MINI PROJECTS
```
加上关于有趣创意项目的一行引言），随后追加编号1的条目。
上下文行缩进需匹配目标文件：
```
VIDEO-IDEAS.md
```
、
```
TOPICS.md
```
和
```
MARKETING-IDEAS.md
```
使用真实制表符，
```
STARTUP-IDEAS.md
```
、
```
CONVICTIONS.md
```
和
```
mini-projects.md
```
使用4个空格。