Back to Details

co-founder-setup

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

setup: turn an empty folder into your business brain

初始化：将空文件夹转变为你的业务大脑

One interview. Three artifacts. Everything else in this collection reads what you build here.
                    /co-founder:co-founder-setup
                           |
          one interview, ~8 questions, 15-20 minutes
                           |
         +-----------------+-----------------+
         |                 |                 |
     AGENTS.md          vault/          voice file
    (the charter)    (empty, ready)   (how you sound)
         |                 |                 |
    every skill       every lesson      every piece of
    reads this        lands here        content matches it
The founder is non-technical. Explain each move in plain English as you make it, and let them watch the files appear. The wow is "it made ME something", not "it ran a script".
一次访谈，三项成果物。本集合中的所有后续操作都会基于此处生成的内容运行。
                    /co-founder:co-founder-setup
                           |
          一次访谈，约8个问题，耗时15-20分钟
                           |
         +-----------------+-----------------+
         |                 |                 |
     AGENTS.md          vault/          语音文件
    (商业章程)    (已就绪的空目录)   (匹配你的语气风格)
         |                 |                 |
    所有skill都会读取此文件   所有内容将存放在这里   生成的内容都会匹配此风格
创始人通常是非技术背景，因此在执行每一步时都要用通俗易懂的英文解释，让他们可以亲眼看到文件生成的过程。核心亮点是“它为我创建了专属内容”，而非“它运行了一个脚本”。

Step 0: Preflight

步骤0：预检

Read 
${CLAUDE_SKILL_DIR}/../../CONVENTIONS.md
, then look at the current folder before touching anything. Setup is the only skill that may create or repair the founder-system signature defined there.
  • Empty or near-empty folder: proceed fresh.
  • A charter or vault from a previous run already exists: this is a re-sync, not a setup. Say so, then update only what changed (new skills into the trigger map, stale paths, renamed files). Everything the founder wrote stays.
  • The folder holds unrelated work (someone's codebase, a downloads dump): stop and ask where their business folder should live. Recommend a fresh folder named after the business.
For every re-sync, STOP and read 
references/migrations.md
. Detect 
.co-founder-version
, show one proposed migration patch, and get the explicit yes before changing founder files. A fresh setup writes the current marker only after the complete scaffold passes its done check.
Done when: you know which of the three modes you are in, the version is known, and the founder knows what is about to happen.
先读取
${CLAUDE_SKILL_DIR}/../../CONVENTIONS.md
，然后在执行任何操作前查看当前文件夹状态。初始化是唯一可创建或修复该文件中定义的创始人系统标识的skill。
  • 空文件夹或接近空的文件夹：全新初始化。
  • 已存在之前生成的章程或vault：执行重新同步，而非全新初始化。告知用户这一点，然后仅更新变更内容（将新skill添加到触发映射、修正失效路径、重命名文件）。创始人编写的所有内容均保留。
  • 文件夹中包含无关内容（如他人的代码库、下载文件）：停止操作并询问用户的业务文件夹应存放在何处。建议创建一个以业务名称命名的新文件夹。
对于每一次重新同步，必须先读取
references/migrations.md
。检测
.co-founder-version
文件，展示一个建议的迁移补丁，在修改创始人文件前必须获得明确的同意。全新初始化仅在完整搭建完成并通过检查后，才会写入当前版本标识。
完成标志：明确当前处于三种模式中的哪一种，确认版本号，并且创始人清楚即将执行的操作。

Step 1: Detect the harness

步骤1：检测运行环境

Check which instruction files this environment reads.
  • AGENTS.md
    or 
    CLAUDE.md
    already present: you will extend, not overwrite.
  • Neither: you will create 
    AGENTS.md
    as the source of truth and link 
    CLAUDE.md
    to it. On Windows, where links need admin rights, create a two-line 
    CLAUDE.md
    containing 
    @AGENTS.md
    instead.
Done when: you know exactly which file(s) step 4 will write.
检查当前环境读取哪些指令文件。
  • 已存在
    AGENTS.md
    或
    CLAUDE.md
    ：将对其进行扩展，而非覆盖。
  • 两者都不存在：将创建
    AGENTS.md
    作为唯一可信源，并将
    CLAUDE.md
    链接到它。在Windows系统中，由于创建链接需要管理员权限，因此创建两行内容的
    CLAUDE.md
    ，内容为
    @AGENTS.md
    。
完成标志：明确步骤4将写入哪些文件。

Step 2: The interview

步骤2：创始人访谈

One question per turn. Every question ships with a 
Working hypothesis:
so the founder reacts instead of composing from scratch; it is an interview candidate, not cleared advice. Facts you can find yourself, find yourself; only decisions reach the founder.
The eight questions, in order:
  1. What is the business called, what does it sell, and to whom? The name plus one sentence each. Push past vague ("coaching") to concrete ("a 6-week pricing course for freelance designers").
  2. What stage? Pre-revenue, or making money, and roughly what monthly range. Ranges are fine, exact numbers are not required.
  3. The one goal for this quarter. A single sentence. If they give three, ask which one wins.
  4. Pricing and margins, if known. Skippable: pre-revenue founders skip it without shame. Whatever lands here powers the cash lens later.
  5. Non-negotiables. Two or three lines they will not cross: a price floor, a channel they refuse, a brand line. These become their laws.
  6. Primary writing format. X/posts or newsletter/email. These are the installed v1 pack; choose the one the founder will publish consistently. Additional channel packs appear here only after they are installed, so setup never promises craft the collection cannot run.
  7. How they sound. Ask for 2-3 samples of their real writing (posts, emails). No samples: three adjectives plus one writer they admire. Either route feeds the voice file.
  8. Where the vault lives. Recommend: right here, this folder. The business folder IS the vault.
A skipped question is recorded as skipped, never guessed at.
Before any answer becomes durable, apply the shared durable claim admission gate. Direct answers are recorded as 
Founder-stated: unverified
unless another checked source verifies them. Writing samples can support observed voice traits; adjectives without samples remain founder-stated and cannot produce 
status: high
.
Apply the shared parameter gate to every missing range, target, cadence, confidence grade, and capacity input. Ask when it blocks setup; otherwise record the skip or working hypothesis as unverified. A plausible default does not become founder context.
Ask before you assert: never present a quantity, duration, sample size, date, or causal motive in prose before asking the founder for it or citing a receipt for it.
每次只问一个问题。每个问题都附带
Working hypothesis:
，让创始人基于假设做出回应，而非从零开始构思；这是访谈的引导假设，而非确定的建议。可自行获取的信息自行查找；仅需创始人做决策的问题才询问他们。
按顺序提出以下8个问题：
  1. 你的业务名称是什么？销售什么产品/服务？面向哪些客户？ 包含名称及各一句话描述。避免模糊表述（如“咨询服务”），要具体明确（如“面向自由设计师的6周定价课程”）。
  2. 业务处于什么阶段？ 未盈利，或已盈利，以及大致的月收入范围。只需提供范围，无需精确数字。
  3. 本季度的核心目标是什么？ 用一句话表述。如果用户给出三个目标，询问哪一个是首要目标。
  4. 定价与利润率（若已知）。 可跳过：未盈利的创始人无需勉强回答。此处的信息将用于后续的现金流分析。
  5. 不可妥协的原则。 列出2-3条底线：如最低定价、拒绝合作的渠道、品牌红线。这些将成为业务的“规则”。
  6. 主要写作格式。 社交平台帖子（X/posts）或新闻稿/邮件。这是v1版本预装的内容包；选择创始人会持续使用的格式。其他渠道包仅在安装后才会显示，因此初始化过程不会承诺本集合未支持的功能。
  7. 你的语言风格。 要求提供2-3个你真实写作的样本（帖子、邮件）。若无样本，则提供3个形容词加一位你欣赏的作者。两种方式都将用于生成语音文件。
  8. vault的存放位置。 建议：就放在当前文件夹。业务文件夹即为vault。
跳过的问题会记录为“已跳过”，绝不猜测答案。
在将任何答案永久保存前，需通过共享的可信度验证机制。直接回答将记录为
Founder-stated: unverified
，除非有其他可信来源验证。写作样本可用于支持观察到的语言风格；无样本的形容词仍标记为创始人陈述，无法获得
status: high
。
对所有缺失的范围、目标、节奏、置信度等级和能力输入应用共享参数验证机制。若验证机制阻碍初始化则询问用户；否则记录为跳过或未验证的初步假设。合理的默认值不会成为创始人的上下文信息。
断言前先询问： 在向创始人展示数量、时长、样本量、日期或因果动机前，必须先询问创始人或引用可信来源。

Arithmetic consistency gate

算术一致性验证

Before confirmation, separate direct inputs from derived numbers. Normalize currency, unit, and time period, then recompute every derived value from the stated inputs with explicit arithmetic. For example, 
2 clients × €800/client/month = €1,600/month
; a stated total of €1,800 conflicts. Show any mismatch as one equation and ask which input should change. Do not round, average, silently repair, or present the derived total as confirmed while the mismatch remains.
Done when: every charter placeholder has either an answer in the founder's words or an explicit skip, and every derived number recomputes exactly from its confirmed inputs.
确认前，将直接输入与推导数值分开。统一货币、单位和时间周期，然后从已确认的输入值重新计算每个推导数值，并明确列出计算过程。例如：
2个客户 × 800欧元/客户/月 = 1600欧元/月
；若用户陈述的总额为1800欧元则存在冲突。将任何不匹配以等式形式展示，并询问应修改哪个输入值。不得四舍五入、取平均值、默默修正，或在不匹配未解决的情况下将推导总额展示为已确认。
完成标志：章程的每个占位符要么填入创始人的原话，要么明确标记为跳过，且每个推导数值都能从已确认的输入值精确重新计算得出。

Step 3: Confirm back

步骤3：信息确认

Present the whole elicited profile on one screen: identity, stage, goal, laws, writing format, voice notes, direct metrics, and each derived metric with its formula. Ask for one explicit yes.
Any correction: integrate it, re-present the full profile, and wait for the yes again. A revision is never a confirmation.
Done when: the founder has said yes to the exact profile you are about to write.
在一个页面上展示所有收集到的信息：业务身份、阶段、目标、规则、写作格式、语言风格说明、直接指标，以及每个推导指标的计算公式。请求用户明确确认。
若有任何修正：整合修正内容，重新展示完整信息，再次等待用户确认。修订不等于确认。
完成标志：创始人已明确确认即将写入的完整信息。

Step 4: Write the charter

步骤4：撰写章程

STOP. Read 
references/charter-template.md
now: it holds the exact section order, the placeholder map, and the line budget. Writing the charter from memory produces a generic file, and a generic charter is the one failure this skill exists to prevent.
Fill the template with the founder's own words from step 2. Target under 150 lines. Then create the link per step 1's finding.
Done when: 
AGENTS.md
exists, 
CLAUDE.md
resolves to it, and every section carries their content, with zero unfilled placeholders.
暂停操作。立即读取
references/charter-template.md
：该文件包含确切的章节顺序、占位符映射和行数限制。凭记忆撰写章程会生成通用文件，而通用章程正是本skill要避免的唯一失败情况。
用步骤2中创始人的原话填充模板。目标行数控制在150行以内。然后根据步骤1的结果创建链接。
完成标志：
AGENTS.md
已存在，
CLAUDE.md
可链接到它，且每个章节都包含创始人的内容，无空占位符。

Step 5: Scaffold the vault and the voice file

步骤5：搭建vault与语音文件

STOP. Read 
references/vault-scaffold.md
now: it holds the folder tree, the note frontmatter schema, the hub seeds, the README text, and the worked example page. The scaffold's value is its exact shape; improvising it breaks steward and recall later.
Create the tree, write 
index.md
and 
log.md
with their genesis entries, place the plain-English README, seed the seven hub notes, and write the voice file to 
wiki/business/voice.md
from the step-2 samples. Ship the worked example at the exact path 
wiki/learnings/example-learning-shape.md
, list it in 
index.md
, link it from 
hub/learnings.md
, and tell the founder they can delete it.
The seven hub notes use the fixed filenames from the reference. Also seed 
queue.md
, 
inbox-ledger.md
, 
wiki/business/metrics.md
, 
wiki/business/offer.md
, and the 
wiki/business/content/
and 
wiki/business/reviews/
folders. These are runtime contracts, not optional examples. Put only founder-confirmed answers from interview questions 2 and 4 into dated metrics rows with 
setup confirmation
as the source. A derived row is eligible only when its stored formula recomputes exactly from named confirmed input rows; write that formula in the Calculation column. An unresolved mismatch writes neither the total nor a receipt. Setup creates offer.md as an empty shape with 
offer_state: draft
; offer alone writes its audience, promise, price, and terms.
Create the vault's 
scripts/
directory. Copy 
${CLAUDE_SKILL_DIR}/references/graph-audit
into it byte-for-byte as 
scripts/graph-audit
and preserve executable mode (or set it where the filesystem supports executable bits). This shipped program is part of the Ready signature; setup never recreates its logic from prose.
During this step, 
log.md
contains exactly the allowed genesis row 
## [date] setup | vault created
. Do not invent a 
scaffold
verb. Do not write 
.co-founder-version
yet; the marker certifies the complete Step 6 system, not a partial tree.
Done when: the tree matches the reference exactly, both root ledgers and canonical business files exist, the worked example is indexed and linked, and 
log.md
carries only its genesis row.
暂停操作。立即读取
references/vault-scaffold.md
：该文件包含文件夹结构、笔记前置元数据 schema、核心笔记种子、README文本和示例页面。搭建的价值在于其精确的结构；随意修改会破坏后续的管理和检索功能。
创建文件夹结构，写入带有初始记录的
index.md
和
log.md
，添加通俗易懂的README，生成7个核心笔记种子，并根据步骤2的样本将语音文件写入
wiki/business/voice.md
。将示例页面放在确切路径
wiki/learnings/example-learning-shape.md
，在
index.md
中列出它，从
hub/learnings.md
链接到它，并告知创始人可删除该示例。
7个核心笔记使用参考文件中指定的固定文件名。同时生成
queue.md
、
inbox-ledger.md
、
wiki/business/metrics.md
、
wiki/business/offer.md
，以及
wiki/business/content/
和
wiki/business/reviews/
文件夹。这些是运行时约定，而非可选示例。仅将访谈问题2和4中创始人确认的答案放入带日期的指标行，来源标记为
setup confirmation
。只有当推导行的存储公式能从已命名的确认输入行精确重新计算时，才允许生成推导行；在“计算方式”列中写入该公式。若存在未解决的不匹配，则不写入总额或来源记录。初始化会创建空结构的offer.md，标记为
offer_state: draft
；只有offer skill才会写入受众、承诺、定价和条款。
创建vault的
scripts/
目录。将
${CLAUDE_SKILL_DIR}/references/graph-audit
逐字节复制到该目录，命名为
scripts/graph-audit
，并保留可执行权限（或在文件系统支持的情况下设置可执行权限）。此程序是Ready标识的一部分；初始化绝不能根据文字描述重新创建其逻辑。
在此步骤中，
log.md
只能包含允许的初始记录：
## [date] setup | vault created
。不得使用“scaffold”等自定义动词。暂不写入
.co-founder-version
；该标识仅用于证明步骤6的完整系统已就绪，而非部分结构已完成。
完成标志：文件夹结构与参考文件完全一致，根目录账本和标准业务文件均已存在，示例页面已建立索引和链接，且
log.md
仅包含初始记录。

Step 6: Land the first artifact and hand off

步骤6：生成首个成果物并交接

Write a short vision stub to 
wiki/business/vision-stub.md
with base-five frontmatter (
type: business
, 
status: stated
) and five body lines from the interview answers: what the business is, who it serves, the quarter's goal, and the founder's laws in brief. List it in 
index.md
, link it from 
hub/business.md
, and append exactly 
## [date] vision | stub for <quarter goal>
to 
log.md
.
Run the final scaffold check: charter/link; README, index, log, baton, both ledgers; all seven fixed hub notes; every fixed wiki folder; the executable 
graph-audit
validator script; voice, metrics, offer, vision stub, and the worked example. For a fresh setup, 
log.md
must contain exactly two event rows in order: 
## [date] setup | vault created
, then 
## [date] vision | stub for <quarter goal>
. A missing row or any other verb fails the check. Keep 
.co-founder-version
absent until the mandatory filing gate below passes.
向
wiki/business/vision-stub.md
写入简短的愿景草稿，包含5项前置元数据（
type: business
, 
status: stated
），以及从访谈答案中提取的5行内容：业务定位、服务对象、季度目标、创始人规则摘要。在
index.md
中列出它，从
hub/business.md
链接到它，并在
log.md
末尾添加确切记录：
## [date] vision | stub for <quarter goal>
。
执行最终搭建检查：章程/链接；README、index、log、引导文件、两个账本；所有7个固定核心笔记；所有固定wiki文件夹；可执行的
graph-audit
验证脚本；语音文件、指标文件、offer文件、愿景草稿和示例页面。 对于全新初始化，
log.md
必须按顺序包含两条事件记录：
## [date] setup | vault created
，然后是
## [date] vision | stub for <quarter goal>
。缺少任何一条记录或使用其他动词均视为检查失败。在通过以下强制验证前，不得写入
.co-founder-version
。

Mandatory filing gate

强制验证机制

  1. Run 
    scripts/graph-audit
    across the complete fresh or migrated vault.
  2. Fix every violation and rerun it. Write 
    .co-founder-version
    containing 
    1.0.0
    and declare setup done only after it exits zero.
Then close with exactly this shape:
  1. Show what was built: the three artifacts, one line each.
  2. Name the ONE next command: run 
    /co-founder:vision
    to turn the stub into the real thing.
  3. Name the sequence once: vision sets direction, plan creates the first initiative, then sprint becomes the daily entry point. Do not present sprint as executable before plan exists.
Never end on plumbing. End on what they own now that they did not own twenty minutes ago.
Done when: the two exact log rows and version marker exist, and the founder knows their three artifacts, the vision → plan → sprint sequence, and the one next command.
  1. 在完整的全新初始化或迁移后的vault上运行
    scripts/graph-audit
    。
  2. 修复所有违规问题并重新运行。只有当脚本返回0时，才写入包含
    1.0.0
    的
    .co-founder-version
    并宣布初始化完成。
然后按以下确切格式结束流程：
  1. 展示已生成的内容：三项成果物，每项一行。
  2. 指定唯一的下一步指令：运行
    /co-founder:vision
    将草稿转换为正式愿景。
  3. 说明一次流程顺序：愿景设定方向，计划创建首个行动项，然后sprint成为日常入口。在计划未生成前，不得将sprint展示为可执行指令。
绝不要以技术细节收尾。要强调用户现在拥有了20分钟前没有的专属内容。
完成标志：两条确切的日志记录和版本标识已存在，且创始人清楚三项成果物、愿景→计划→sprint的流程顺序，以及下一步指令。