https://github.com/jafb321/create-saas-harness
Ready-for-dev, agents-powered SaaS template
https://github.com/jafb321/create-saas-harness
Last synced: about 2 hours ago
JSON representation
Ready-for-dev, agents-powered SaaS template
- Host: GitHub
- URL: https://github.com/jafb321/create-saas-harness
- Owner: JAFB321
- License: mit
- Created: 2026-06-30T07:59:25.000Z (4 days ago)
- Default Branch: main
- Last Pushed: 2026-07-02T00:28:25.000Z (2 days ago)
- Last Synced: 2026-07-02T08:36:09.699Z (2 days ago)
- Language: JavaScript
- Homepage: https://maker.jafb.dev
- Size: 774 KB
- Stars: 3
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# create-saas-harness
A **ready-for-dev, agents-powered SaaS template**: a Next.js 15 + Supabase monorepo that ships
with a built-in agent **harness** (orchestrator + subagents + commands + roadmap + docs) so an AI
coding agent (Claude Code) can take your idea from **0 → 100**.
You don't just get a boilerplate. You get a boilerplate **plus the machinery to plan and build your
specific product on top of it** — guided by a structured interview that writes your foundations and
a fully populated, executable roadmap.
```bash
npx create-saas-harness@latest
```
## What you get
- **Monorepo** — Turborepo + pnpm, TypeScript strict, `@app/*` workspace packages
(`core`, `db`, `integrations`, `config`).
- **Next.js 15** App Router + React 19 + Tailwind v4/shadcn, i18n-ready, a neutral SaaS shell
(auth, dashboard, settings, billing/tiers, one generic CRUD resource with RLS).
- **Supabase** — Auth, Postgres with RLS, private Storage. Mock-first: the app runs 100% without
third-party keys.
- **Modular by scaffold** — the CLI assembles your stack deterministically and prunes the rest:
- **Payments**: **Stripe** or **MercadoPago** (single `PaymentProvider` interface).
- **Storage**: **Supabase Storage** or **S3-compatible** (Cloudflare R2 / AWS S3 / MinIO).
- **Email**: **Resend** or none for now (mock-first either way).
The chosen adapters are wired via `packages/integrations/src//real.ts`; unchosen adapters
and their SDK dependencies never land in your repo.
- **Tests** — Playwright (E2E) + Vitest (unit) with a critical-flow baseline.
- **CI/CD** — GitHub Actions (verify, e2e, migrations) + Vercel + Supabase config.
- **The harness** — `harness/` with an orchestrator workflow, specialized subagents
(`dev-agent`, `dev-agent-pro`, `verifier`, `reviewer`, `doc-keeper`), slash commands
(`/session-start`, `/session-wrap`, `/verify`, `/project-setup`), deterministic guards (hooks),
and machine-readable state + roadmap.
## The experience
1. **Scaffold.** `npx create-saas-harness@latest` asks the essentials (project name, payments,
storage, email, package manager), copies the template, assembles the chosen modules, installs
deps, and makes the **first commit**. Every prompt is also a flag, so the whole thing runs
unattended:
```bash
npx create-saas-harness@latest my-saas --payments stripe --storage supabase --email resend --pm pnpm -y
```
Prefer clicking? Build your command visually at the **[configurator](./landing/)** (the Astro
landing page in this repo).
2. **Define your product.** Open your agent and run `/project-setup`. It interviews you across
7 rounds (idea, critical features, secondary features, business model, inspirations, dev
profile), then spawns two agents:
- `foundations-synthesizer` → writes `FOUNDATIONS/*` (your product's source of truth).
- `roadmap-architect` → fills `harness/docs/roadmap/mvp-*.json` + `plans/*.md` with an
executable roadmap.
3. **Build.** Read `INSTRUCTIONS.md` and run the daily loop: `/session-start` → work the roadmap →
`/verify` → `/session-wrap`.
No MVP task is executed during setup — you end with a clean first commit, complete foundations, and
a roadmap ready for agents to execute.
## Requirements
- Node.js >= 20, pnpm (recommended), and an agent that supports custom commands/subagents
(Claude Code today).
- A Supabase project (or the local stack via the Supabase CLI). The app runs mock-first without
any third-party keys.
## Repo layout (this repo)
```
create-saas-harness/
├─ packages/cli/ # the npx scaffolder (prompts + flags, copy, prune, git init + first commit)
├─ template/ # the project that gets copied into your new folder
└─ landing/ # the Astro landing page / command configurator (deployed on Vercel)
```
## License
MIT — see [LICENSE](./LICENSE).