Get Started

Scripts

Root-level commands you will run every day.

What It Does

The root package.json scripts coordinate build/dev/lint/typecheck/test and database workflows across the monorepo.

When To Use

Starting local development.
Running CI-equivalent checks locally.
Generating DB artifacts.

Prerequisites

Run from monorepo root.
Install dependencies first.

Important

This page describes the standard kit integration path; adapt app-specific paths and config names when your project differs.

How To Use

Core development

pnpm dev
pnpm build
pnpm test
pnpm typecheck

Code quality (Biome)

pnpm lint
pnpm lint:fix
pnpm format
pnpm format:fix
pnpm check

Database and Supabase

creatorem generate-sql
pnpm run supabase:start
pnpm run supabase:stop
pnpm run db:reset
pnpm run db:types

db:reset

db:reset regenerates the SQL migration file from the app selection and setup, then resets the local Supabase database with that generated SQL.

db:types

Run db:types when the local Supabase Docker instance is started. It generates TypeScript database types and refreshes Drizzle schemas from the currently generated and applied SQL migration state.

MCP Context

capability: repo_task_execution
entrypoints:
  - package.json scripts
inputs:
  - task_type
outputs:
  - workspace_build_or_validation_result
constraints:
  - commands assume workspace tooling installed
  - db tasks assume supabase cli + docker availability
side_effects:
  - may generate artifacts and cache files

Agent Recipe

Use pnpm check && pnpm typecheck before proposing commits.
For database changes, run creatorem generate-sql then validation commands.
Use pnpm dev for multi-app local development.

Troubleshooting

If supabase:start fails, start Docker and retry.
If type errors reference stale DB types, run pnpm run db:types.

Filter API

Typed filter architecture used to compose kit features into apps with high modularity.

Database

Supabase + SQL workflow used by the kit.

How is this guide?

Last updated on 3/23/2026