Documentation
supastarter for TanStack Startsupastarter for TanStack Start

Skills

Browse the AI agent skills included with supastarter for faster, more reliable coding with Cursor, Claude Code, Codex, and more.

Skills teach AI coding agents how to complete common supastarter tasks the right way. Instead of rediscovering project conventions on every prompt, agents follow curated workflows for features, auth, payments, database changes, tests, and more — so you get faster, more reliable results with less back-and-forth.

Want a skill for something that is not covered yet? Request it any time in the support Discord or by .

Setup & environment

  • Local environment setup (local-environment-setup) — Bootstrapping the TanStack Start monorepo locally with pnpm, PostgreSQL, optional MinIO, and root Vite environment variables.
  • Deploy and environment variables (deploy-and-env-vars) — Linking deployment projects, changing remote environment variables, creating preview/production deployments, or inspecting deployment configuration.
  • Adding a dependency (adding-a-dependency) — Installing a runtime or development package into a specific pnpm workspace while preserving the shared catalog and lockfile.

Building features

  • Add a feature module (add-a-feature-module) — Introducing a cohesive SaaS or marketing feature module with TanStack Router routes, Form state, Query state, and local aliases.
  • Add an organization-scoped feature (add-organization-scoped-feature) — Adding tenant-owned data or behavior that must enforce Better Auth organization membership and role boundaries.
  • Add an oRPC procedure (add-orpc-procedure) — Adding a typed oRPC endpoint, router entry, authorization middleware, and TanStack Query client integration.
  • Add a UI component (add-a-ui-component) — Adding a reusable Shadcn-style React component or Base UI wrapper to the shared UI workspace.
  • Add a marketing page or blog post (add-a-marketing-page-or-blog-post) — Adding a TanStack Router marketing page or localized MDX blog/legal content backed by Content Collections.
  • Add a notification (add-a-notification) — Adding a typed in-app and email notification kind with preferences, persistence, links, and localized settings labels.

Auth & payments

  • Add an auth flow or Better Auth plugin (add-auth-flow-or-better-auth-plugin) — Extending Better Auth server/client plugins, auth routes, session fields, email hooks, or sign-in flows.
  • Add a payment provider (add-a-payment-provider) — Implementing and selecting a payment provider adapter with checkout, portal, webhook, cancellation, and seat semantics.
  • Add or change a payment plan (add-or-change-a-payment-plan) — Changing configured billing plans, provider price IDs, checkout selection, pricing UI, or localized plan copy.

Data & integrations

  • Database schema change (database-schema-change) — Changing the active PostgreSQL Drizzle schema, generated Zod models, query layer, or generated migration artifacts.
  • Add a storage or AI integration (add-a-storage-or-ai-integration) — Extending the S3-compatible storage layer or AI SDK model/provider integration through typed server-side packages and oRPC.
  • Add or edit an email (add-or-edit-an-email) — Creating or changing a localized React Email template, subject mapping, preview props, and send call.
  • Add translations (add-translations) — Adding or changing use-intl message keys across SaaS, marketing, mail, shared scopes, locales, and locale-aware routing.

Quality & shipping

  • Writing unit tests (writing-unit-tests) — Adding Vitest unit or procedure tests for SaaS modules and the shared oRPC API package.
  • Writing E2E tests (writing-e2e-tests) — Adding or updating Playwright end-to-end coverage for the marketing or SaaS TanStack Start applications.
  • Verify changes (verify-changes) — Validating a repository change against Supastarter's formatting, lint, type-check, build, Vitest, and Playwright gates.
  • Debugging a failing CI run (debugging-a-failing-ci-run) — Diagnosing a failed GitHub Actions validation job and reproducing its exact pnpm command locally.
  • Reviewing a PR (reviewing-a-pr) — Performing a risk-focused code review of a pull request against repository conventions and validation evidence.
  • Update the docs (update-the-docs) — Updating repository-owned Fumadocs content or preparing an explicit handoff for Supastarter documentation maintained outside this repository.