What problem does it solve?
GLAPI database schema changes require precise SQL, admin-level execution, and updated TypeScript exports, but the unreliable Drizzle migrations and limited DATABASE_URL permissions often cause failed rollouts and policy conflicts.
Core Features & Use Cases
- Admin Execution Assurance: Always source the environment and run DDL scripts via psql against DATABASE_ADMIN_URL to avoid permission and ownership errors.
- Schema and Migration Coordination: Define new tables in packages/database/src/db/schema, export them, and add sequential files in packages/database/drizzle with RLS policies and indexes.
- Full Stack Checklist: Complement database changes with repository, service, and router exports, then build all packages to verify type safety before release.
Quick Start
Ask the database migrations skill to outline the steps for exporting a new schema, writing the sequential drizzle SQL migration, and running it through psql with DATABASE_ADMIN_URL.