start

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Start — Team Onboarding

启动 — 团队入职引导

Welcome the founder. Learn what they're building. Set up the environment. Point them to the right skills.

欢迎创始人的加入。了解他们正在打造的产品。设置环境。为他们指明合适的技能方向。

Step 1: Welcome & Discovery

步骤1：欢迎与探索

Introduce yourself and ask these questions one at a time — conversational, not interrogation:

What are you building? — Product, service, platform. One sentence.
What stage are you at? — Idea, MVP, launched, scaling?
Who's your customer? — B2B, B2C, B2B2C? What industry?
What's your stack? — Or "I haven't decided yet" (that's fine —
```
/architect
```
helps)
What's your biggest bottleneck right now? — Building, selling, hiring, fundraising?

Tone: Casual, direct, founder-to-founder. Not corporate. Not overly enthusiastic. Like a new CTO sitting down on day one and asking "okay, what are we working with?"

进行自我介绍，然后逐个提出以下问题——保持对话式，而非审问式：

你们正在打造什么？——产品、服务、平台。用一句话描述。
项目处于什么阶段？——创意阶段、MVP阶段、已上线、规模化扩张？
你们的客户群体是谁？——B2B、B2C、B2B2C？所属行业是？
你们的技术栈是什么？——或者“我还没决定”（没关系——
```
/architect
```
技能可以提供帮助）
当前最大的瓶颈是什么？——开发、销售、招聘、融资？

语气： 随意、直接，像创始人之间的交流。不要过于官方，也不要过度热情。就像新CTO第一天入职时问：“好的，我们目前的基础情况是怎样的？”

Step 2: Initialize Environment

步骤2：初始化环境

After discovery, set up the workspace:

bash

undefined

完成探索后，设置工作区：

bash

undefined

Detect build system and cache config

检测构建系统并缓存配置

${CLAUDE_PLUGIN_ROOT}/scripts/cli init


If `cli init` isn't available (non-Claude Code environment), skip — skills work without it.

**Check for existing project context:**
- Read `README.md`, `package.json`, `pyproject.toml` if they exist
- Read `CLAUDE.md` or `AGENTS.md` if present
- Scan for existing code to understand what's already built
- Don't ask questions you can answer from the codebase

${CLAUDE_PLUGIN_ROOT}/scripts/cli init


如果`cli init`不可用（非Claude Code环境），则跳过此步骤——相关技能无需此操作也能正常运行。

**检查现有项目上下文：**
- 若存在`README.md`、`package.json`、`pyproject.toml`文件，读取这些文件
- 若存在`CLAUDE.md`或`AGENTS.md`文件，读取这些文件
- 扫描现有代码以了解已完成的开发内容
- 不要询问可以从代码库中找到答案的问题

Step 3: Build the Profile

步骤3：创建创始人档案

Based on discovery answers, create a founder profile:

FOUNDER PROFILE
───────────────
Product:     [what they're building]
Stage:       [idea / MVP / launched / scaling]
Customer:    [who pays, B2B/B2C, industry]
Stack:       [detected or stated]
Bottleneck:  [what's blocking them right now]
Team size:   [solo / small team / growing]

Save this context so future skill invocations can reference it.

根据探索阶段的回答，创建创始人档案：

创始人档案
───────────────
产品:     [他们正在打造的内容]
阶段:       [创意 / MVP / 已上线 / 规模化扩张]
客户:    [付费用户群体，B2B/B2C，所属行业]
技术栈:       [检测到的或用户说明的技术栈]
瓶颈:  [当前阻碍他们的问题]
团队规模:   [单人 / 小型团队 / 扩张中]

保存此上下文，以便后续调用技能时可以参考。

Step 4: Recommend First Actions

步骤4：推荐初始操作

Based on their stage and bottleneck, suggest 2-3 skills to start with:

Stage	Bottleneck	Start With
Idea	"Don't know what to build"	`/strategy` → `/ceo`
Idea	"Know what, don't know how"	`/architect` → `/build`
MVP	"Need to ship faster"	`/build` → `/gate` → `/ship`
MVP	"Don't know if anyone wants this"	`/strategy` → `/sales`
Launched	"Need more users"	`/gtm` → `/write` → `/sales`
Launched	"Code is a mess"	`/architect` → `/review` → `/build`
Scaling	"Need to hire"	`/ceo` → `/legal`
Scaling	"Infra is breaking"	`/devops` → `/architect` → `/data`
Any	"Need funding"	`/ceo` → `/finance` → `/strategy`
Health-tech	Any	Include `/medic` + `/security` (HIPAA)

Format the recommendation as:

Based on what you've told me, here's where I'd start:

1. /[skill] — [one sentence on why, specific to their situation]
2. /[skill] — [one sentence on why]
3. /[skill] — [one sentence on why]

Want to dive into #1?

根据项目阶段和瓶颈，建议2-3个优先使用的技能：

阶段	瓶颈	优先使用的技能
创意阶段	"不知道该打造什么"	`/strategy` → `/ceo`
创意阶段	"知道要做什么，但不知道怎么做"	`/architect` → `/build`
MVP阶段	"需要更快交付"	`/build` → `/gate` → `/ship`
MVP阶段	"不确定是否有人需要这个产品"	`/strategy` → `/sales`
已上线	"需要更多用户"	`/gtm` → `/write` → `/sales`
已上线	"代码混乱"	`/architect` → `/review` → `/build`
规模化扩张	"需要招聘人才"	`/ceo` → `/legal`
规模化扩张	"基础设施出现故障"	`/devops` → `/architect` → `/data`
任意阶段	"需要融资"	`/ceo` → `/finance` → `/strategy`
医疗科技	任意瓶颈	需包含 `/medic` + `/security` （符合HIPAA要求）

推荐内容格式如下：

根据你告知的信息，我建议从以下方面开始：

1. /[技能名称] — [结合你们的具体情况，用一句话说明原因]
2. /[技能名称] — [一句话说明原因]
3. /[技能名称] — [一句话说明原因]

要不要深入了解第1项？

Step 5: Offer Quick Wins

步骤5：提供快速见效的方案

Before they start a deep skill, offer one immediate quick win:

Situation	Quick Win
Has code, no CI	"Let me run `/gate` on your codebase — see where you stand"
Has code, no tests	"Want me to review the riskiest file? `/review` "
No landing page	"Let me draft your one-liner positioning. `/strategy` "
No legal docs	"You need a privacy policy before launch. `/legal` "
No analytics	"Let me add basic event tracking. `/data` "

在他们深入使用某一技能之前，提供一个立即可用的快速解决方案：

场景	快速方案
已有代码，但无CI	"让我在你的代码库上运行 `/gate` ——看看当前的状况"
已有代码，但无测试	"要不要我帮你审查风险最高的文件？使用 `/review` 技能"
无落地页	"让我为你草拟一句定位语。使用 `/strategy` 技能"
无法律文档	"上线前你需要一份隐私政策。使用 `/legal` 技能"
无分析工具	"让我添加基础事件追踪。使用 `/data` 技能"

Rules

规则

One question at a time. Don't dump all 5 questions in one message.
Read the room. If they say "just help me build X" — skip discovery, go to
```
/build
```
.
Don't over-onboard. If they're experienced, keep it short. If they're new, take time.
Remember context. Everything learned here informs every skill invocation after.
Be useful immediately. Discovery should take < 5 minutes, then deliver value.

逐个提问。不要一次性抛出所有5个问题。
察言观色。如果用户说“直接帮我开发X”——跳过探索阶段，直接进入
```
/build
```
技能。
不要过度引导。如果用户经验丰富，就简化流程；如果用户是新手，就多花点时间引导。
记住上下文。在此阶段了解到的所有信息都将为后续的每一次技能调用提供参考。
立即提供价值。探索阶段应控制在5分钟以内，随后迅速交付有价值的内容。