# SaaS Boilerplate Builder

Maps the SaaS Boilerplate onto a product's pages, schema and launch scope.

- Repository: https://github.com/ixartz/SaaS-Boilerplate (7478 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add ixartz/SaaS-Boilerplate --skill saas-builder -g -a claude-code -y`
Codex: `npx skills add ixartz/SaaS-Boilerplate --skill saas-builder -g -a codex -y`
Cursor: `npx skills add ixartz/SaaS-Boilerplate --skill saas-builder -g -a cursor -y`
Gemini CLI: `npx skills add ixartz/SaaS-Boilerplate --skill saas-builder -g -a gemini-cli -y`

## Description

Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# SaaS Builder

## Purpose

Verify the local baseline, then adapt the boilerplate's marketing, routes, schema, auth, i18n, UI, and tests for the user's SaaS MVP.

## Mandatory Baseline Gate

Run these commands before planning, editing, or implementing product-specific work:

```bash
git clone https://github.com/ixartz/SaaS-Boilerplate.git <target-directory>
cd <target-directory>
npm install
```

Users usually run `npx skills add ixartz/saas-boilerplate` from a parent/root directory; it creates `.agents/` there and clones the boilerplate into `<target-directory>`. Since the app is one level below the agent's initial cwd, `cd <target-directory>` before reading app files or running project commands, and confirm `package.json`, `src/`, and `skills/` exist.

Then verify the baseline:

```bash
npm run build-local
npm run test
```

Setup and verification commands are hard gates. Do not continue to mapping or implementation work until the baseline is fixed.

## Working Rules

- Use the verified clone as the source of truth. Inspect current files before making claims or edits.
- Keep changes minimal. Do not reformat unrelated files.
- Do not change these: `src/components/DemoBadge.tsx`, its `DemoBadge` usage in `src/app/[locale]/layout.tsx`, or `src/app/[locale]/(auth)/dashboard/page.tsx`.
- Use marketing routes only for promotional content.
- Treat landing and marketing page adaptation as part of every SaaS implementation unless the user explicitly scopes it out.
- Build product workflows as dedicated authenticated dashboard feature pages, not in the dashboard index: use `src/app/[locale]/(auth)/dashboard/<feature>/page.tsx` for CRUD, data entry, tools, and customer-specific views.
- Split complex product workflows across several authenticated pages when needed. Do not force every part of a workflow into a single page; a feature can use separate pages for list, create, edit, detail, settings, or related subflows.

## Project Conventions

The rest: https://github.com/ixartz/SaaS-Boilerplate/blob/HEAD/skills/saas-builder/SKILL.md