db-bootstrap

Creates a standard Supabase project directory structure with migrations, seeds, tests, and config files.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill db-bootstrap-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-bootstrap
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/database/db-bootstrap
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill db-bootstrap-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up a new Supabase project involves creating many directories, config files, and boilerplate SQL by hand, which is error-prone and inconsistent across teams. This Skill scaffolds the entire standard structure in one guided flow. ## Core Features & Use Cases - Directory Scaffolding: Creates migrations, seeds, tests, rollback, snapshots, and docs folders with README conventions for each. - Three Setup Tiers: Choose Minimal (directories only), Standard (plus READMEs and config.toml), or Full (plus baseline schema with RLS policies and smoke tests). - Baseline Schema & Smoke Tests: Generates an example profiles table with triggers, row-level security policies, and a post-migration validation script. - Use Case: When starting a greenfield project on Supabase, run the bootstrap to get a migration workflow, rollback strategy, and migration log ready before writing your first schema. ## Quick Start Ask the agent to bootstrap a new Supabase project structure with the standard template for your project.

Frequently Asked Questions about db-bootstrap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a Supabase project structure for migrations?▼

Run the bootstrap flow to create supabase/ directories for migrations, seeds, tests, rollback, snapshots, and docs. Choose Minimal, Standard, or Full templates depending on whether you want READMEs, config.toml, and a baseline schema included.

What is the correct order for statements in a Supabase migration file?▼

The recommended order is extensions, tables with constraints, functions, triggers, RLS enablement and policies, then views. Migration files use the YYYYMMDDHHMMSS_description.sql naming convention.

Does the bootstrap work with an existing Supabase CLI project?▼

Yes, the bootstrap is compatible with the Supabase CLI. If a supabase/ folder already exists, you can back it up, bootstrap the new structure, and merge existing migrations manually.

How do I write idempotent seed data for PostgreSQL?▼

Use INSERT with ON CONFLICT (id) DO NOTHING so seeds can run repeatedly without duplicate key errors. Seeds are categorized as required, test, or reference data in the generated seeds README.

What should I do if the supabase directory already exists?▼

Back up the existing folder with mv supabase supabase.backup, run the bootstrap, then copy your old migrations into the new structure. Alternatively merge manually or choose a different directory.