solo-init

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

/init

One-time founder onboarding. Asks key questions, generates personalized configuration files. Everything stored as readable markdown/YAML — edit anytime.

Two layers of config:

~/.solo-factory/defaults.yaml
— org-level (bundle IDs, GitHub org, Apple Team ID). Shared across all projects.
.solo/
in project — founder philosophy, dev principles, STREAM calibration, selected stacks. Per-project but usually the same.

The templates in

solo-factory/templates/

are defaults. This skill personalizes them based on your answers.

Run once after installing solo-factory. Safe to re-run — shows current values and lets you update them.

创始人首次配置引导。通过询问关键问题，生成个性化配置文件。所有内容均以易读的Markdown/YAML格式存储，可随时编辑。

两层配置结构：

~/.solo-factory/defaults.yaml
— 组织级别（Bundle ID、GitHub组织、Apple团队ID）。所有项目共享。
.solo/
（项目目录下）—— 创始人理念、开发原则、STREAM校准方案、选定技术栈。按项目存储，但通常保持一致。

solo-factory/templates/

中的文件为默认模板。本功能会根据你的回答对模板进行个性化调整。

安装solo-factory后运行一次即可。可安全重复运行——会显示当前配置值并允许你进行更新。

Output Structure

输出结构

~/.solo-factory/
└── defaults.yaml              # Org defaults (bundle IDs, GitHub, Team ID)

.solo/
├── manifest.md                # Your founder manifesto (generated from answers)
├── stream-framework.md         # STREAM calibrated to your risk/decision style
├── dev-principles.md          # Dev principles tuned to your preferences
└── stacks/                    # Only your selected stack templates
    ├── nextjs-supabase.yaml
    └── python-api.yaml

Steps

步骤

1. Check existing config

1. 检查现有配置

Read
```
~/.solo-factory/defaults.yaml
```
— if exists, show current values
Check if
```
.solo/
```
exists in project path
If both exist, ask: "Reconfigure from scratch?" or "Keep existing and skip?"
If neither exists, continue to step 2

读取
```
~/.solo-factory/defaults.yaml
```
——若存在，显示当前值
检查项目路径下是否存在
```
.solo/
```
目录
若两者均存在，询问：“是否从头重新配置？”或“保留现有配置并跳过？”
若均不存在，继续执行步骤2

2. Determine project path

2. 确定项目路径

$ARGUMENTS

contains a path, use it. Otherwise use current working directory.

若

$ARGUMENTS

包含路径，则使用该路径；否则使用当前工作目录。

3. Ask org defaults (AskUserQuestion, 5 questions)

3. 询问组织级默认配置（AskUserQuestion，共5个问题）

See

references/questions.md

→ "Round 0: Org Defaults" for full question specs.

详见

references/questions.md

→ "Round 0: Org Defaults" 获取完整问题说明。

4. Create org defaults

4. 创建组织级默认配置

bash

mkdir -p ~/.solo-factory

Write

~/.solo-factory/defaults.yaml

yaml

undefined

bash

mkdir -p ~/.solo-factory

写入

~/.solo-factory/defaults.yaml

：

yaml

undefined

Solo Factory — org defaults

Used by /scaffold and other skills for placeholder replacement.

Re-run /init to update these values.

org_domain: "<answer from 3.1>" apple_dev_team: "<answer from 3.2>" github_org: "<answer from 3.3>" projects_dir: "<answer from 3.4>" knowledge_base_repo: "<answer from 3.5>"

undefined

org_domain: "<answer from 3.1>" apple_dev_team: "<answer from 3.2>" github_org: "<answer from 3.3>" projects_dir: "<answer from 3.4>" knowledge_base_repo: "<answer from 3.5>"

undefined

5. Ask Round 1 — Philosophy & Values (AskUserQuestion, 4 questions)

5. 询问第一轮问题——理念与价值观（AskUserQuestion，共4个问题）

See

references/questions.md

→ "Round 1: Philosophy & Values" for full question specs.

详见

references/questions.md

→ "Round 1: Philosophy & Values" 获取完整问题说明。

6. Ask Round 2 — Development Preferences (AskUserQuestion, 4 questions)

6. 询问第二轮问题——开发偏好（AskUserQuestion，共4个问题）

See

references/questions.md

→ "Round 2: Development Preferences" for full question specs.

详见

references/questions.md

→ "Round 2: Development Preferences" 获取完整问题说明。

7. Ask Round 3 — Decision Style & Stacks (AskUserQuestion, 3 questions)

7. 询问第三轮问题——决策风格与技术栈（AskUserQuestion，共3个问题）

See

references/questions.md

→ "Round 3: Decision Style & Stacks" for full question specs.

详见

references/questions.md

→ "Round 3: Decision Style & Stacks" 获取完整问题说明。

8. Load default templates + generate personalized files

8. 加载默认模板并生成个性化文件

See

references/generation-rules.md

for:

Template source locations
Output file structure (defaults.yaml, manifest.md, stream-framework.md, dev-principles.md, stacks/)
Personalization rules per file (how answers map to generated content)
Stack template mapping (answer → YAML file)

详见

references/generation-rules.md

获取：

模板源位置
输出文件结构（defaults.yaml、manifest.md、stream-framework.md、dev-principles.md、stacks/）
各文件的个性化规则（回答如何映射到生成内容）
技术栈模板映射（回答→YAML文件）

10. Verify Solograph MCP (optional check)

10. 验证Solograph MCP（可选检查）

Try running
```
uvx solograph --help
```
or check if MCP tools are available
If available: "Solograph detected — code graph ready"
If not: "Tip: install Solograph for code search across projects (
```
pip install solograph
```
or
```
uvx solograph
```
)"

尝试运行
```
uvx solograph --help
```
或检查MCP工具是否可用
若可用：“检测到Solograph——代码图谱已就绪”
若不可用：“提示：安装Solograph以实现跨项目代码搜索（
```
pip install solograph
```
或
```
uvx solograph
```
）”

11. Summary

11. 总结

Solo Factory initialized!

Org config:
  Config:         ~/.solo-factory/defaults.yaml
  org_domain:     <value>
  apple_dev_team: <value>
  github_org:     <value>
  projects_dir:   <value>

Founder profile:
  Manifest:       .solo/manifest.md
  Dev Principles: .solo/dev-principles.md
  STREAM:          .solo/stream-framework.md
  Stacks:         .solo/stacks/ (N stacks)

These files are yours — edit anytime.
Other skills read from .solo/ automatically.

Next steps:
  /validate "your idea"          — validate with your manifest
  /scaffold app nextjs-supabase  — scaffold with your stack

Solo Factory initialized!

Org config:
  Config:         ~/.solo-factory/defaults.yaml
  org_domain:     <value>
  apple_dev_team: <value>
  github_org:     <value>
  projects_dir:   <value>

Founder profile:
  Manifest:       .solo/manifest.md
  Dev Principles: .solo/dev-principles.md
  STREAM:          .solo/stream-framework.md
  Stacks:         .solo/stacks/ (N stacks)

These files are yours — edit anytime.
Other skills read from .solo/ automatically.

Next steps:
  /validate "your idea"          — validate with your manifest
  /scaffold app nextjs-supabase  — scaffold with your stack

Edge cases

边缘情况

See

references/generation-rules.md

→ "Edge Cases" for full list.

详见

references/generation-rules.md

→ "Edge Cases" 获取完整列表。

Common Issues

常见问题

Templates directory not found

模板目录未找到

Cause: solo-factory not installed as submodule or templates moved. Fix: Skill generates from inline knowledge if templates missing. To fix permanently, ensure

solo-factory/templates/

exists.

原因： solo-factory未作为子模块安装，或模板已被移动。 解决方法： 若模板缺失，本功能会基于内置知识生成内容。如需永久修复，请确保

solo-factory/templates/

目录存在。

Stacks not copied to .solo/

技术栈未复制到.solo/目录

Cause: Stack selection answer didn't map to a template file. Fix: Check available stacks in

templates/stacks/

. Re-run

/init

and select from the list.

原因： 技术栈选择的回答未匹配到对应的模板文件。 解决方法： 查看

templates/stacks/

中的可用技术栈。重新运行

/init

并从列表中选择。

defaults.yaml already exists

defaults.yaml已存在

Cause: Previously initialized. Fix: Skill detects existing config and asks whether to reconfigure. Choose "Reconfigure from scratch" to overwrite.

原因： 之前已完成初始化。 解决方法： 本功能会检测到现有配置，并询问是否重新配置。选择“Reconfigure from scratch”以覆盖现有配置。