Solo Factory Skills
30 executable skills. Pipeline: research → validate → scaffold → build → deploy → launch.
install all:
npx skills add fortunto2/solo-factory --allinstall one:
npx skills add fortunto2/solo-factory/researchmeta
/knowledge Needing methodology reference, asking about principles, harness engineering, SGR, launch playbook, agent memory, decision frameworks, or any topic covered in the solopreneur knowledge base. Also use when the user asks or /skill-audit Evaluating skill against best practices /memory-audit Need to optimize agent context loading
analysis
/research Need evidence before validation /swarm Want faster multi-angle alternative to /research /validate Need idea scoring with PRD output /stream Facing a high-stakes founder choice /sgr Need to design a schema-guided reasoning pipeline for an agent or API /you2idea-extract Mining video content for business opportunities
development
/scaffold Need project from PRD + stack template /setup After /scaffold before /plan to generate workflow config /plan Describing a feature/bug/refactor, or need task breakdown before building /build Track ID referenced, or plan tasks need execution /deploy After /build completes and project needs hosting /review After /build or /deploy completes
promotion
/launch Product is built and needs distribution strategy /landing-gen Need marketing page from PRD /content-gen Need social posts from PRD /video-promo Need video marketing material /community-outreach Need to find relevant threads for launch /reddit Need to participate in Reddit threads. NOT for thread discovery (/community-outreach) or social copy (/content-gen) /github-outreach Targeting users of competitor libraries. NOT for Reddit (/reddit) or social copy (/content-gen) /seo-audit Need website SEO health check /metrics-track Need analytics plan /legal Project needs compliance documents /humanize Text reads like AI-generated output with em dashes and stock phrases
utility
/init First session in solo-factory. Safe to re-run /factory First-time installation of the startup pipeline /pipeline Need multi-skill automation /retro After pipeline completes and needs quality assessment /audit Docs need health check /index-youtube Need searchable YouTube content /android-release Ship an Android app to testers or to Google Play, or push an update to an app already listed there. Use when the user says wants install attribution set up (Play referrer UTMs, Install Referrer API, an in-app counter and the matching Data safety form), or hits a Play policy deadline (). Leads with the MINIMAL tester-link workflow (fastest), then the FULL production listing, then UPDATE for an existing app. Carries the exact Play Console browser steps, signing/keystore setup, the testing-track comparison, required assets, and the gotchas (lintVitalRelease crash, 16 KB alignment, target API deadline) so you don't re-learn them /apple-app-icon Build an iOS 26+ layered app icon (.icon / Icon Composer) from a designer's SVG, generated by script rather than drawn by hand, and check every appearance without launching the app. Use when the user says or when an app still ships a folder of flattened PNGs /customer-finder Need an evidence-backed shortlist of potential first customers from public signals /diagnose Diagnosis loop for hard bugs and performance regressions — build a tight feedback loop first, hypothesise second. Use when user says or reports something throwing, failing, flaky, or slow /domain Check whether a product name is actually free — across domain zones (RDAP + whois), the App Store, Google Play, GitHub and trademarks — before buying anything. Use when the user says is picking a brand, or is about to buy a domain /grill Relentless one-question-at-a-time interview that stress-tests a plan, design, or decision before anything gets built. Use when user says or a plan still has soft spots. Also reachable by other skills that need an interview /i18n When UI strings are hardcoded and a second language is coming /ios-dev Build iPhone/iOS apps — native SwiftUI or Kotlin-Multiplatform hybrid. Use when scaffolding an iOS app, writing SwiftUI/ARKit/MapLibre features, wiring the Claude Code ↔ Xcode workflow, building or installing on a physical device, or setting up a project so it survives its first App Store upload (product name, orientations, encryption, dSYM, xcodeproj tracking). For TestFlight, submission, screenshots and store metadata use solo-ios-release instead /ios-release Ship an iPhone/iOS app to testers (TestFlight) or to the App Store, or push an update to an app already listed there. Use when the user says or wants store attribution set up (campaign links, `ct` tokens, App Analytics, an in-app counter and the matching App Privacy declaration). CLI-first via the `asc` tool (official App Store Connect API) — the browser is a fallback for the few things the API cannot do. Pair with the `ios-app` skill for the build/signing/archive checklist /model-shrink Take a trained neural model to devices — ONNX export, int8 quantization, Core ML conversion, on-device benchmarking, download-on-demand delivery. Use when user says or an ML feature needs to ship inside a mobile/web app /seo-cli Manage SEO and agent-readiness for all sites via the `seo` CLI — audit pages for SEO+GEO score, run `agent-audit` to check whether AI agents can discover and read a site (robots rules, Content-Signals, llms.txt, markdown negotiation, MCP cards), check Search Console analytics, submit sitemaps, ping IndexNow, inspect indexing. Covers Google, Bing, Yandex. Also points at superduper-analytics for who actually visited, which AI agents read the site, and what each campaign produced. Covers Bing Webmaster API (a second index, and the one ChatGPT and Copilot read). Use when the user asks about search performance, indexing, SEO/GEO score, agent-readiness, llms.txt, MCP, or wants to fix a site /swiftui-design-system Build and hold a SwiftUI design system — a 12-column grid, spacing/type/radius/motion scales, surface levels, a component gallery, and the guards that stop it drifting back. Use when the user says or when a screen's spacing and fonts were each chosen once and never against each other