Skip to content

install-order.md

Latest commit

 

History

History
98 lines (78 loc) · 1.68 KB

install-order.md

File metadata and controls

98 lines (78 loc) · 1.68 KB

Install Order

Install order keeps source modules from becoming a pile of unrelated files. For traction, start with the API SaaS path: foundations, identity, API access, usage/credits, webhooks, billing, then adapters.

The practical first command is:

pnpm stackfoundry add recipe api-saas-starter --target ./my-app --dry-run

Agent Workflow

agent-ready-installs
  -> inspect recipe
  -> dry-run install
  -> review diff
  -> verify target app

Foundation

next-saas-shell
  -> settings-layout
  -> command-menu
  -> drizzle-postgres
  -> tenant-context

Identity

auth-core
  -> account-modes
  -> clerk-auth / auth-better-auth
  -> orgs-rbac
  -> invites
  -> permission-matrix

Monetization

billing-core
  -> stripe-billing
  -> entitlements
  -> plan-gating
  -> usage-metering
  -> quota-enforcement
  -> credit-wallet
  -> invoices / billing-portal

Developer Platform

api-keys
  -> api-errors
  -> rate-limits
  -> usage-metering
  -> quota-enforcement
  -> credit-wallet
  -> api-docs
  -> webhook-inbox
  -> webhook-delivery
  -> idempotency-keys

Operations

admin-console
  -> audit-log
  -> support-console
  -> system-health
  -> incident-management
  -> status-page

Provider Adapters

Provider adapters are installed after the source-owned domain module they adapt:

billing-core -> stripe-billing / autumn-billing
api-keys -> unkey-api-keys
rate-limits -> unkey-rate-limits
email-templates -> resend-email
feature-flags -> posthog-analytics
file-uploads -> vercel-blob / cloudflare-r2

When in doubt, inspect a recipe first:

pnpm stackfoundry recipe api-saas-starter