Use when "set up solo factory", "initialize profile", "configure defaults", "first time setup", "onboard me", or first session in solo-factory. Safe to re-run. Do NOT use for project scaffolding (/scaffold).
Installs into .claude/skills of the current project.
Sponsors
SSkills DirectorySkills Directory
Is that skill safe to install?
SSkills DirectorySkills Directory
Know which skills are safe β weekly.
Are you the author of Init?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/fortunto2-init)
---
name: solo-init
description: Use when "set up solo factory", "initialize profile", "configure defaults", "first time setup", "onboard me", or first session in solo-factory. Safe to re-run. Do NOT use for project scaffolding (/scaffold).
license: MIT
metadata:
author: fortunto2
version: "2.2.0"
openclaw:
emoji: "π¬"
allowed-tools: Read, Grep, Bash, Glob, Write, Edit, AskUserQuestion
argument-hint: "[project-path]"
---
# /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.
## 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
```
Other skills read from these:
- `/scaffold` reads `defaults.yaml` for `<org_domain>`, `<apple_dev_team>` placeholders + `.solo/stacks/` for stack templates
- `/validate` reads `manifest.md` for manifesto alignment check
- `/setup` reads `dev-principles.md` for workflow config
- `/stream` reads `stream-framework.md` for decision framework
## Steps
### 1. Check existing config
- 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
### 2. Determine project path
If `$ARGUMENTS` contains a path, use it. Otherwise use current working directory.
### 3. Ask org defaults (AskUserQuestion, 5 questions)
See `references/questions.md` β "Round 0: Org Defaults" for full question specs.
### 4. Create org defaults
```bash
mkdir -p ~/.solo-factory
```
Write `~/.solo-factory/defaults.yaml`:
```yaml
# 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>"
```
### 5. Ask Round 1 β Philosophy & Values (AskUserQuestion, 4 questions)
See `references/questions.md` β "Round 1: Philosophy & Values" for full question specs.
### 6. Ask Round 2 β Development Preferences (AskUserQuestion, 4 questions)
See `references/questions.md` β "Round 2: Development Preferences" for full question specs.
### 7. Ask Round 3 β Decision Style & Stacks (AskUserQuestion, 3 questions)
See `references/questions.md` β "Round 3: Decision Style & Stacks" for full question specs.
### 8. Load default templates + generate personalized files
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)
### 10. Verify Solograph MCP (optional check)
- Try `~/.solo/bin/solograph --version` (or `command -v solograph`), or check if MCP tools are available
- If available: "Solograph detected: search over code, sessions and notes ready"
- If not: "Tip: install Solograph for code search across projects (one binary: https://github.com/fortunto2/solograph#install)"
### 11. Summary
```
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.
## 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.
### Stacks not copied to .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.
### defaults.yaml already exists
**Cause:** Previously initialized.
**Fix:** Skill detects existing config and asks whether to reconfigure. Choose "Reconfigure from scratch" to overwrite.