Skip to content
Back to skills

Flisk Recipe Saas

ASecurity

Recipe for "build me a SaaS with login and billing" with Flisk - a web app, an accounts API with a database for sign-up and login, and a billing API, in one stack started with `flisk up`. Use with the flisk-build skill when the user asks for a SaaS, a members area, subscriptions, sign-up or payments.

  • 54 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 21, 2026
developmentbashdockerapidatabasefrontendbackend

Works with

  • claude code
  • cli
  • api
  • mcp

Security analysis

A100/100

Scanned November 21, 2026

npx -y skills add flisk-sh/flisk --skill flisk-recipe-saas --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Flisk Recipe Saas?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Flisk Recipe Saas
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/flisk-sh-flisk-recipe-saas-flisk/badge)](https://www.skillsdirectory.com/skills/flisk-sh-flisk-recipe-saas-flisk)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: flisk-recipe-saas
description: Recipe for "build me a SaaS with login and billing" with Flisk - a web app, an accounts API with a database for sign-up and login, and a billing API, in one stack started with `flisk up`. Use with the flisk-build skill when the user asks for a SaaS, a members area, subscriptions, sign-up or payments.
license: MIT
compatibility: Requires the flisk CLI, Docker and Tilt on the local machine. Does not deploy.
metadata:
  author: flisk-sh
  version: "1.0"
---

# Recipe: a SaaS with login and billing

**Parts:** a web app, an accounts API (sign-up, login, sessions), and a billing API (plans and subscriptions). Both APIs store data in the stack's Postgres.

## Steps

```bash
flisk doctor
flisk project --yes
flisk resource web --type frontend --stack saas --yes
flisk resource accounts-api --type backend --stack saas --feature drizzle --yes
flisk resource billing-api --type backend --stack saas --feature drizzle --yes
flisk up saas --dry-run
flisk up saas --json &        # wait for {"ok":true}
flisk networks --stack saas --raw
```

## App code

- `accounts-api`: `POST /signup`, `POST /login`, `GET /me`. Hash passwords (`Bun.password.hash`). Sign session tokens with `JWT_SECRET`, which Flisk generates into the project `.env` and passes to the container. Do not invent a new secret file.
- `billing-api`: `GET /plans`, `POST /subscribe`, `GET /subscription`. Verify the caller's token with the same `JWT_SECRET`.
- Payments: without the user's test keys, record subscriptions in the database and say that no real payment provider is connected. If the user gives a provider's **test** key, list its name under `secrets.required` in `services/saas/billing-api/service.json` and put the value in the project `.env`, never in code.
- `web`: sign-up and login forms, a plans page, and a "your plan" page.

## Done when

Each answers 200: the `web` health URL, `/api/accounts/health`, `/api/accounts/health/db`, `/api/billing/health` and `/api/billing/health/db` on `api.<project>.localhost:<port>`. Also sign up and log in once with `curl` and show the user it worked.

Then tell the user the web app URL, the two API URLs, that payments are not connected to a real provider (unless they are), and that `flisk down` stops everything.

## MCP tools

If a `mcp__flisk__*` tool is missing, run `flisk connect claude` in the project folder and restart Claude Code. The CLI commands in this skill work without MCP as well.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in development →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.