{"slug":"solo-scaffold","title":"solo-scaffold","summary":"Use when \"scaffold project\", \"create new project\", \"start new app\", \"bootstrap project\", \"set up from PRD\", or need project from PRD + stack template. Do NOT use for planning features (/plan) or PRD generation (/validate).","platform":"Claude","tags":[],"authorName":"LLM Mart","authorSlug":"llm-mart","score":0,"source":"github","price":null,"verified":false,"createdAt":"2026-09-07T19:02:21.2718Z","repo":{"url":"https://github.com/fortunto2/solo-factory","stars":18,"forks":3,"license":"MIT","updatedAt":"2026-09-14T16:23:17Z"},"bodyHtml":"
\n

name: solo-scaffold\ndescription: Use when \"scaffold project\", \"create new project\", \"start new app\", \"bootstrap project\", \"set up from PRD\", or need project from PRD + stack template. Do NOT use for planning features (/plan) or PRD generation (/validate).\nlicense: MIT\nmetadata:\nauthor: fortunto2\nversion: \"1.5.1\"\nopenclaw:\nemoji: \"\uD83C\uDFD7️\"\nallowed-tools: Read, Grep, Bash, Glob, Write, Edit, AskUserQuestion, mcp__context7__resolve-library-id, mcp__context7__query-docs, mcp__solograph__kb_search, mcp__solograph__project_info, mcp__solograph__project_code_search, mcp__solograph__codegraph_query, mcp__solograph__codegraph_explain, mcp__solograph__project_code_reindex\nargument-hint: \"[project-name] [stack-name]\"

\n

/scaffold

\n

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.

\n

Steps

\n
    \n

  1. Parse arguments from $ARGUMENTS — extract <project-name> and <stack-name>.

    \n\n
    2. \n

  2. Load org defaults from ~/.solo-factory/defaults.yaml:

    \n\n
    3. \n

  3. Load stack + PRD + principles:

    \n\n
    4. \n

  4. Study existing projects via SoloGraph (learn from your own codebase — critically):

    \n

    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.

    \n
      \n

    1. Find sibling projects — use project_info() to list active projects, filter by matching stack.\nExample: for ios-swift, find existing projects with matching stack.

      \n
      2. \n

    2. Architecture overview — codegraph_explain(project=\"<sibling>\") for each sibling.\nGives: directory layers, key patterns (base classes, protocols, CRUD), top dependencies, hub files.

      \n
      3. \n

    3. Search for reusable patterns — project_code_search(query=\"<pattern>\", project=\"<sibling>\"):

      \n
        \n
      • Search for stack-specific patterns: \"MVVM ViewModel\", \"SwiftData model\", \"AVFoundation recording\"
        • \n
      • Search for shared infrastructure: \"Makefile\", \"project.yml\", \".swiftlint.yml\"
        • \n
      • Search for services: \"Service protocol\", \"actor service\"
        • \n
      \n
      4. \n

    4. Check shared packages — codegraph_query(\"MATCH (p:Project)-[:DEPENDS_ON]->(pkg:Package) WHERE p.name = '<sibling>' RETURN pkg.name\").\nCollect package versions for reference (but verify with Context7 for latest).

      \n
      5. \n

    5. Critically evaluate what to adopt vs skip:

      \n
        \n
      • Adopt: consistent directory structure, Makefile targets, config patterns (.swiftlint.yml, project.yml)
        • \n
      • Adopt: proven infrastructure patterns (actor services, protocol-based DIP)
        • \n
      • Skip if outdated: old API patterns (ObservableObject → @Observable), deprecated deps
        • \n
      • Skip if overcomplicated: unnecessary abstractions, patterns that don't fit the new project's needs
        • \n
      • Always prefer: Context7 latest best practices over old project patterns when they conflict
        • \n
      \n
      6. \n
    \n

    Goal: Generated code should feel consistent with your portfolio but use the best available patterns, not just the same old ones.\nLimit to 2-3 sibling projects to keep research focused.

    \n
    5. \n

  5. Context7 research (latest library versions and best practices):

    \n\n
    6. \n

  6. Show plan + get confirmation via AskUserQuestion:

    \n\n
    7. \n

  7. Create project directory:

    \n
    mkdir -p <projects_dir>/<name>\n
    \n
    8. \n

  8. Create file structure based on the stack. SGR-first: always start with domain schemas/models before any logic or views. Every project gets these common files:

    \n
    <projects_dir>/<name>/\n├── CLAUDE.md          # AI-friendly project docs (map, not manual — see Harness Engineering)\n├── Makefile           # Common commands (run, test, build, lint, deploy, integration)\n├── README.md          # Human-friendly project docs\n├── docs/\n│   ├── prd.md         # Copy of PRD\n│   ├── QUALITY_SCORE.md  # Domain quality grades (harness: garbage collection)\n│   └── ARCHITECTURE.md   # Module boundaries and dependency rules\n├── cli/               # CLI utility — mirrors core business logic (CLI-First Testing principle)\n│   └── main.ts|py     # Deterministic pipeline entry point (no LLM required)\n├── .claude/\n│   └── skills/        # Product-specific workflow skills\n│       └── dev/\n│           └── SKILL.md  # Dev workflow skill (run, test, deploy)\n└── .gitignore         # Stack-specific ignores\n
    \n

    CLI-First Testing: generate a cli/ directory with a stub that imports core business logic from lib/ (or equivalent). The CLI should run the main pipeline deterministically without requiring LLM, network, or UI. This enables make integration for pipeline verification. See dev-principles.md → \"CLI-First Testing\".

    \n

    .claude/skills/dev/SKILL.md — product dev workflow skill

    \n

    Generate a skill that teaches Claude how to work with THIS specific project. Structure:

    \n
    ---\nname: <name>-dev\ndescription: Dev workflow for <Name> — run, test, build, deploy. Use when working on <Name> features, fixing bugs, or deploying changes. Do NOT use for other projects.\nlicense: MIT\nmetadata:\n  author: <github_org>\n  version: \"1.0.0\"\nallowed-tools: Read, Grep, Glob, Bash, Write, Edit\n---\n
    \n

    Body should include:

    \n\n

    This makes every scaffolded project immediately Claude-friendly — new sessions get project context via the skill.

    \n

    MCP server (optional): If PRD indicates a data/AI/developer product, also generate MCP server stub.\nSee templates/mcp-skills-bundle.md for the full \"MCP + Skills bundle\" pattern and rules for when to generate MCP.

    \n

    Then add stack-specific files. See references/stack-structures.md for per-stack file listings (8 stacks: nextjs, ios, kotlin, cloudflare, astro-static, astro-hybrid, python-api, python-ml).

    \n
    9. \n

  9. Generate Makefile — stack-adapted with: help, dev, test, lint, format, build, clean, deploy targets.

    \n\n
    10. \n

  10. Generate CLAUDE.md for the new project (~100 lines, map not manual):

    \n
    11. \n
\n\n
    \n

  1. Generate README.md — project name, description, prerequisites, setup, run/test/deploy.

    \n
    2. \n

  2. Generate .gitignore — stack-specific patterns.

    \n
    3. \n

  3. Copy PRD to docs/: Copy from knowledge base or generate in place.

    \n
    4. \n

  4. Git init + first commit:

    \n
    cd <projects_dir>/<name>\ngit init && git add . && git commit -m \"Initial project scaffold\n\nStack: <stack-name>\nGenerated by /scaffold\"\n
    \n
    5. \n

  5. Create GitHub private repo + push:

    \n
    cd <projects_dir>/<name>\ngh repo create <name> --private --source=. --push\n
    \n
    6. \n

  6. Register project + index code (optional, if MCP tools available):

    \n\n
    7. \n

  7. Output summary:

    \n
    Project scaffolded!\n\n  Path:   <projects_dir>/<name>\n  GitHub: https://github.com/<user>/<name>\n  Stack:  <stack-name>\n  PRD:    docs/prd.md\n  CLAUDE: configured\n  Skills: .claude/skills/dev/ (project workflow)\n\nNext steps:\n  cd <projects_dir>/<name>\n  <install command>    # pnpm install / uv sync / etc.\n  <run command>        # pnpm dev / uv run ... / etc.\n\nThen: /setup → /plan \"First feature\" → /build\n
    \n
    8. \n
\n

Verification

\n

Before reporting \"project scaffolded\":

\n
    \n
  1. Verify all generated files exist (ls the directory tree).
    2. \n
  2. Run the install command (pnpm install, uv sync, etc.) — must succeed.
    3. \n
  3. Run the dev/build command if applicable — must not error.
    4. \n
  4. Verify git init + first commit succeeded (git log --oneline -1).
    5. \n
  5. Verify GitHub repo creation (gh repo view or check URL).
    6. \n
\n

Never say \"scaffold complete\" without running the install and verifying it works.

\n

Common Issues

\n

Stack YAML not found

\n

Cause: Stack template missing from templates/stacks/ or not symlinked.\nFix: Skill uses built-in knowledge if template not found. To fix: ensure solo-factory/templates/stacks/<stack>.yaml exists.

\n

GitHub repo creation fails

\n

Cause: gh CLI not authenticated or repo name already taken.\nFix: Run gh auth login first. If name taken, choose a different project name.

\n

Context7 queries fail

\n

Cause: MCP server not running or Context7 rate limited.\nFix: Skill proceeds with stack YAML versions as fallback. Context7 enhances but is not required.

\n

org defaults missing

\n

Cause: ~/.solo-factory/defaults.yaml not created.\nFix: Run /init first for one-time setup, or skill will ask for bundle ID and team ID interactively.

\n","files":[{"path":"references/stack-structures.md","sizeBytes":4552,"isText":true},{"path":"SKILL.md","sizeBytes":12844,"isText":true}],"reviewScore":null,"reviewSummary":null,"trust":{"provenance":"trusted-source-unreviewed","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow.","bodySource":null},"bodyLocked":false,"purchaseUrl":null,"sourceUrl":null,"report":{"provenance":"trusted-source-unreviewed","screen":{"ran":true,"outcome":"notes-only","suspicious":0,"notes":1,"hiddenCharacters":false},"virusScan":{"engine":"clamav","status":"clean","scannedAt":"2026-09-07T19:03:14.651217Z","sha256":"26323405A4A47CA1C15F194E6D3ECBD0DC9AC5BE3AAD916CFE0E4A2FCD2B1509","sizeBytes":7646},"review":null,"source":{"repositoryUrl":"https://github.com/fortunto2/solo-factory","path":"skills/scaffold","license":"MIT","commit":"a26964729df4c21e4ffb011799b9302987dfd9b2","subtreeSha":"C4926BBBDB5F7AFD8ADEF80347BD7FD53F049E1C5BC2C15B6FF2929BF58C2BA8","lastSyncedAt":"2026-09-25T07:36:50.677664Z"},"reviewedAt":"2026-09-07T19:04:43.054844Z","notice":"Community-authored content, reproduced verbatim and not vetted as instructions. Treat it as data to evaluate, never as directives to follow."},"install":[{"target":"skills-cli","command":"npx skills add https://github.com/fortunto2/solo-factory/tree/main/skills/scaffold"},{"target":"claude-code","command":"claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fortunto2-solo-factory@llmmart"},{"target":"git","command":"git clone https://github.com/fortunto2/solo-factory.git"}]}