solo-init
Skill18 starsChanged 4 months agoMITView on GitHub
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 packages
In this repository62 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- solo-android-releaseSkill
- solo-apple-app-iconSkill
- solo-auditSkill
- solo-boardSkill
- solo-buildSkill
- solo-community-outreachSkill
- solo-content-genSkill
- solo-creator-growthSkill
- solo-customer-finderSkill
- solo-deep-researchSkill
- solo-deploySkill
- solo-diagnoseSkill
- solo-domainSkill
- solo-factorySkill
- solo-github-outreachSkill
- solo-gmail-cliSkill
- solo-grillSkill
- solo-hackathonSkill
- solo-humanizeSkill
- solo-i18nSkill
- solo-index-youtubeSkill
- solo-ios-devSkill
- solo-ios-releaseSkill
- solo-kaggle-gpuSkill
- solo-kindleSkill
- solo-knowledgeSkill
- solo-landing-genSkill
- solo-launchSkill
- solo-legalSkill
- solo-memory-auditSkill
- solo-metrics-trackSkill
- solo-mirrorSkill
- solo-model-shrinkSkill
- solo-music-reels-cutSkill
- solo-open-datasetSkill
- solo-paperSkill
- solo-pdf-printSkill
- solo-pipelineSkill
- solo-planSkill
- solo-redditSkill
- solo-researchSkill
- solo-retroSkill
- solo-reviewSkill
- solo-scaffoldSkill
- solo-secretsSkill
- solo-seo-auditSkill
- solo-seo-cliSkill
- solo-setupSkill
- solo-sgrSkill
- solo-skill-auditSkill
- solo-skill-shelfSkill
- solo-stem-splitSkill
- solo-streamSkill
- solo-supervoxSkill
- solo-swiftui-design-systemSkill
- solo-transcribeSkill
- solo-validateSkill
- solo-video-editSkill
- solo-video-promoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 3 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Run once after installing solo-factory.
- Very specific: line 51
Read ~/.solo-factory/defaults.yaml — if exists, show current values
- Very specific: line 52
Check if .solo/ exists in project path
- Distinctive: line 53
If both exist, ask: "Reconfigure from scratch?" or "Keep existing and skip?"
- Distinctive: line 54
If neither exists, continue to step 2
- Very specific: line 58
If $ARGUMENTS contains a path, use it.
- Distinctive: line 106
If available: "Solograph detected — code graph ready"
- Very specific: line 107
If not: "Tip: install Solograph for code search across projects (pip install solograph or uvx solograph)"
- Very specific: line 147
Fix: Check available stacks in templates/stacks/.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/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.yamlOther skills read from these:
/scaffoldreadsdefaults.yamlfor<org_domain>,<apple_dev_team>placeholders +.solo/stacks/for stack templates/validatereadsmanifest.mdfor manifesto alignment check/setupreadsdev-principles.mdfor workflow config/streamreadsstream-framework.mdfor 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
mkdir -p ~/.solo-factoryWrite ~/.solo-factory/defaults.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 running
uvx solograph --helpor 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 solographoruvx solograph)"
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 stackEdge 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

