Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Universalize: remove project-specific references, add SearXNG recommendation
What This Skill Does
Onboards a solo founder by asking structured questions across four rounds and generating personalized configuration files. Creates org-level defaults (bundle IDs, GitHub org, Apple Team ID) and a per-project .solo/ directory with a founder manifesto, dev principles, STREAM decision framework, and selected stack templates. Other skills in the solo-factory system read from these files automatically.
Centralizes founder configuration once so dependent skills like /scaffold, /validate, /setup, and /stream can pull from consistent, personalized defaults without prompting the user again.
When to use it
- First-time setup after installing solo-factory
- Updating org defaults like Apple Team ID or GitHub org across all projects
- Selecting and storing preferred tech stacks (Next.js, Python API, etc.) for reuse
- Calibrating a personal decision-making framework before starting a new product
- Regenerating config after a shift in dev philosophy or team structure
Example Workflow
Here's how your AI assistant might use this skill in practice.
User says: set up solo factory
- 1Check ~/.solo-factory/defaults.yaml and .solo/ for existing config, ask whether to reconfigure if found
- 2Ask five org-defaults questions: org domain, Apple Team ID, GitHub org, projects dir, knowledge base repo
- 3Ask four philosophy and values questions, then four development preference questions
- 4Ask three decision style and stack selection questions
- 5Generate ~/.solo-factory/defaults.yaml and .solo/manifest.md, stream-framework.md, dev-principles.md, and selected stack YAMLs under .solo/stacks/
- 6Optionally check for Solograph MCP and print a tip if not found
.solo/ directory and ~/.solo-factory/defaults.yaml created with personalized content, summary printed with next-step commands