solo-setup
Skill18 starsChanged 4 months agoMITView on GitHub
Use when "set up workflow", "configure TDD", "wire up dev workflow", or after /scaffold before /plan to generate workflow config. Do NOT use for founder setup (/init) or scaffolding (/scaffold).
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-initSkill
- 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-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, 4 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
After /scaffold creates a project, before /plan.
- Distinctive: line 28
If MCP tools are not available, fall back to reading local files only.
- Very specific: line 33
If $ARGUMENTS is provided, look for a project with that name in the current directory or projects_dir from ~/.solo-factory/defaults.yaml.
- Distinctive: line 35
Verify the directory exists and has CLAUDE.md.
- Distinctive: line 36
If not found, ask via AskUserQuestion.
- Very specific: line 39
If docs/workflow.md exists, warn and ask whether to regenerate.
- Very specific: line 50
If MCP kb_search available: search for stack template and dev-principles.
- Distinctive: line 52
If neither available: derive all info from CLAUDE.md + package manifest (sufficient).
- Very specific: line 119
Fix: Run /scaffold first, or ensure you're in the project root with CLAUDE.md.
≈ “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
/setup
Auto-generate project workflow config from existing PRD and CLAUDE.md. Zero interactive questions — all answers extracted from project data that already exists after /scaffold.
When to use
After /scaffold creates a project, before /plan. Creates docs/workflow.md so /plan and /build can work.
MCP Tools (use if available)
project_info(name)— get project details, detected stackkb_search(query)— search for dev principles, manifest, stack templatesproject_info(name)— project stack and dependencies
If MCP tools are not available, fall back to reading local files only.
Steps
- Detect project root:
- If
$ARGUMENTSis provided, look for a project with that name in the current directory orprojects_dirfrom~/.solo-factory/defaults.yaml. - Otherwise use current working directory.
- Verify the directory exists and has
CLAUDE.md. - If not found, ask via AskUserQuestion.
- If
- Check if already initialized:
- If
docs/workflow.mdexists, warn and ask whether to regenerate.
- If
- Read project data (parallel — all reads at once):
CLAUDE.md— tech stack, architecture, commands, Do/Don'tdocs/prd.md— problem, users, solution, features, metrics, pricingpackage.jsonorpyproject.toml— exact dependency versionsMakefile— available commands- Linter configs (
.eslintrc*,eslint.config.*,.swiftlint.yml,ruff.toml,detekt.yml)
- Read ecosystem sources (optional — enhances quality):
- Detect stack name from CLAUDE.md (look for "Stack:" or the stack name in tech section).
- If MCP
kb_searchavailable: search for stack template and dev-principles. - Otherwise: look for
stacks/<stack>.yamlanddev-principles.md+dev-principles-my.md(personal extensions) in.solo/or plugin templates directory (if accessible). - If neither available: derive all info from CLAUDE.md + package manifest (sufficient).
- Detect languages from package manifest:
package.json→ TypeScriptpyproject.toml→ Python*.xcodeprojorPackage.swift→ Swiftbuild.gradle.kts→ Kotlin
- Create docs directory if needed:
mkdir -p docs - Generate
docs/workflow.md: Based on dev-principles (from MCP/KB or built-in defaults):# Workflow — {ProjectName} ## TDD Policy **Moderate** — design first (data model, edge cases, contracts), then code and tests together at agreed seams. No agent-run red-green ritual. Write tests for: - Business logic and validation - API route handlers - Complex algorithms Tests optional for: UI components, one-off scripts, prototypes. Regression check: the stack's mutation tool (mutmut / Stryker / cargo-mutants) on changed business logic at the end of a phase, where installed. Switch to **Strict** only if a human writes or reviews each failing test before the implementation. ## Test Framework {from package manifest devDeps: vitest/jest/pytest/xctest} ## Commit Strategy **Conventional Commits** Format: `<type>(<scope>): <description>` Types: feat, fix, refactor, test, docs, chore, perf, style ## Verification Checkpoints **After each phase completion:** 1. Run tests — all pass 2. Run linter — no errors 3. Run build — successful (if applicable) 4. Manual smoke test ## Branch Strategy - `main` — production-ready - `feat/<track-id>` — feature branches - `fix/<description>` — hotfixes - Update
CLAUDE.md— add workflow reference to Key Documents section if not present. - Show summary and suggest next step:
Setup complete for {ProjectName}! Created: docs/workflow.md — TDD moderate, conventional commits Next: /plan "Your first feature"
Common Issues
CLAUDE.md not found
Cause: Project not scaffolded or running from wrong directory.
Fix: Run /scaffold first, or ensure you're in the project root with CLAUDE.md.
workflow.md already exists
Cause: Previously set up. Fix: Skill warns and asks whether to regenerate. Existing file is preserved unless you confirm overwrite.
Wrong test framework detected
Cause: Multiple test frameworks in devDependencies.
Fix: Skill picks the first found. Edit docs/workflow.md manually to specify the correct framework.
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.

