solo-scaffold
Generate complete project from PRD + stack template — directory structure, configs, CLAUDE.md, git repo, and GitHub push. Use when user says "scaffold project", "create new project", "start new app", "bootstrap project", or "set up from PRD". Uses SoloGraph for patterns and Context7 for latest versions. Do NOT use for planning features (use /plan) or PRD generation (use /validate).
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/fortunto2/solo-scaffold/scaffold
Scaffold a complete project from PRD + stack template. Creates directory structure, configs, CLAUDE.md, git repo, and pushes to GitHub. Studies existing projects via SoloGraph for consistent patterns, uses Context7 for latest library versions.
Steps
-
Parse arguments from
$ARGUMENTS— extract<project-name>and<stack-name>.- If not provided or incomplete, use AskUserQuestion to ask for missing values.
- Show available stacks from
templates/stacks/*.yaml(source of truth). If MCPproject_infoavailable, also show detected stacks from active projects. List stack names with one-line descriptions from each YAML'sdescriptionfield. - Project name should be kebab-case.
-
Load org defaults from
~/.solo-factory/defaults.yaml:- Read
org_domain(e.g.com.mycompany),apple_dev_team,github_org,projects_dir - If file doesn't exist, ask via AskUserQuestion:
- "What is your reverse-domain prefix for bundle IDs?" (e.g.
com.mycompany) - "Apple Developer Team ID?" (optional, leave empty if no iOS)
- "What is your reverse-domain prefix for bundle IDs?" (e.g.
- Create
~/.solo-factory/defaults.yamlwith answers for future runs - Replace
<org_domain>,<apple_dev_team>,<github_org>placeholders in all generated files
- Read
-
Load stack + PRD + principles:
- Look for stack YAML: search for
stacks/<stack>.yamlin plugin templates (viakb_searchor Glob). - If stack YAML not found, use built-in knowledge of the stack (packages, structure, deploy).
- Check if PRD exists:
docs/prd.mdor search current directory forprd.md- If not: generate a basic PRD template
- Look for dev principles: search for
dev-principles.mdor use built-in SOLID/DRY/KISS/TDD principles.
- Look for stack YAML: search for
-
Study existing projects via SoloGraph (learn from your own codebase — critically):
Before generating code, study active projects with the same stack. Don't blindly copy — existing projects may have legacy patterns or mistakes. Evaluate what's actually useful.
a. Find sibling projects — use
project_info()to list active projects, filter by matching stack. Example: forios-swift, find existing projects with matching stack.b. Architecture overview —
codegraph_explain(project="<sibling>")for each sibling. Gives: directory layers, key patterns (base classes, protocols, CRUD), top dependencies, hub files.c. Search for reusable patterns —
project_code_search(query="<pattern>", project="<sibling>"):- Search for stack-specific patterns: "MVVM ViewModel", "SwiftData model", "AVFoundation recording"
- Search for shared infrastructure: "Makefile", "project.yml", ".swiftlint.yml"
- Search for services: "Service protocol", "actor service"
d. Check shared packages —
codegraph_query("MATCH (p:Project)-[:DEPENDS_ON]->(pkg:Package) WHERE p.name = '<sibling>' RETURN pkg.name"). Collect package versions for reference (but verify with Context7 for latest).
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-fortunto2-solo-scaffold": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
solo-swarm
Launch 3 parallel research agents (market, users, tech) to investigate an idea from multiple angles simultaneously. Use when user says "swarm research", "parallel research", "investigate fast", "3 agents", "team research", or wants faster alternative to /research. Produces research.md. Do NOT use for solo research (use /research) or idea scoring (use /validate).
solo-build
Execute implementation plan tasks with TDD workflow, auto-commit, and phase gates. Use when user says "build it", "start building", "execute plan", "implement tasks", "ship it", or references a track ID. Do NOT use for planning (use /plan) or scaffolding (use /scaffold).
solo-metrics-track
Set up PostHog metrics plan with event funnel, KPI benchmarks, and kill/iterate/scale decision thresholds. Use when user says "set up metrics", "track KPIs", "PostHog events", "funnel analysis", "when to kill or scale", or "success metrics". Do NOT use for SEO metrics (use /seo-audit).
solo-audit
Health check knowledge base for broken links, missing frontmatter, tag inconsistencies, and coverage gaps. Use when user says "audit KB", "check frontmatter", "find broken links", "tag cleanup", or "knowledge base quality". Do NOT use for SEO audits (use /seo-audit) or code reviews.
solo-seo-audit
SEO health check for any URL — analyzes meta tags, OG, JSON-LD, sitemap, robots.txt, SERP positions, and scores 0-100. Use when user says "check SEO", "audit this page", "SEO score", "check meta tags", or "SERP position". Do NOT use for generating landing content (use /landing-gen) or social media posts (use /content-gen).