nextbase-nextjs-supabase-starter

Convert existing React components, UI libraries, poorly made components, or design implementations to shadcn/ui components. Use when converting Material-UI, Ant Design, Chakra UI, or custom components to shadcn/ui, migrating from other component libraries, translating Figma/design mockups to shadcn components, refactoring existing React code to use shadcn/ui patterns, or fixing poorly written/structured components by rebuilding them with shadcn/ui. Also use when asked to rebuild, recreate, reimplement, clean up, or improve components using shadcn/ui.

Code generation and conversion for Next.js 16 applications using Cache Components (PPR). Use when the user requests to "convert to use cacheComponents" at project or page level, create new Next.js pages/components with proper caching directives, split pages into cached and dynamic sections with Suspense boundaries, or work with Next.js 16's new caching model including use cache, cacheLife, Suspense, and anonymous Supabase clients for cache-friendly data fetching.

Generate comprehensive pgTap tests for Supabase PostgreSQL databases. Use when asked to write database tests for RLS policies, triggers, functions, data integrity, cascading deletes, or any pgTap/Supabase testing. Triggers include "write pgTap tests", "test RLS policies", "create trigger tests", "test database function", "write cascade tests", "test data integrity".

Expert guidance for building UI components with shadcn/ui library. Use when creating, customizing, or working with shadcn/ui components in React/Next.js projects. Covers component installation, theming, variants, animations, accessibility, form handling, and integration patterns. Trigger on requests like "create shadcn component", "add shadcn form", "customize shadcn theme", "shadcn dialog", "shadcn data table", or any UI development using shadcn/ui components.

Enforce the Nextbase Supabase schema-first migration workflow. Use when changing database structure, RLS policies, functions, triggers, enums, indexes, extensions, generated database types, or any files under apps/database/supabase; especially when asked to create, update, fix, or review database migrations. Requires editing or creating declarative schema files first, generating migrations with the Supabase CLI, and never manually creating or editing migration SQL files.