This one teaches you to think through database architecture decisions rather than just copy-pasting schema patterns. It covers the full stack: choosing between PostgreSQL, Neon, Turso, or SQLite based on your deployment context, picking the right ORM (Drizzle, Prisma, Kysely), designing normalized schemas, planning indexes, and avoiding N+1 queries. The approach is deliberately opinionated about not defaulting to PostgreSQL for everything and actually asking about requirements first. It's structured as a decision framework with selective reading guides, so you're not wading through irrelevant docs about Prisma when you're using Drizzle. Honestly refreshing to see database guidance that starts with context instead of assuming everyone needs a full Postgres cluster.
npx -y skills add vudovn/antigravity-kit --skill database-design --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
prisma/skills
firebase/agent-skills
Dexploarer/hyper-forge
itsmostafa/aws-agent-skills
prisma/skills