omer-metin/skills-for-antigravity
Database design specialist for schema modeling, query optimization, indexing strategies, and data integrityUse when "database design, schema, indexes, query optimization, migrations, normalization, database scaling, foreign keys, data modeling, database, sql, postgres, mysql, mongodb, schema, indexes, migrations, normalization, optimization" mentioned.
npx skills add omer-metin/skills-for-antigravity --skill database-architect
Database design specialist for schema modeling, query optimization, indexing strategies, and data integrityUse when "database design, schema, indexes, query optimization, migrations, normalization, database scaling, foreign keys, data modeling, database, sql, postgres, mysql, mongodb, schema, indexes, migrations, normalization, optimization" mentioned.
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill …
391.6K installsGuides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, Mon…
269.8K installsPrisma Postgres setup and operations guidance across Console, create-db CLI, Management API, an…
263K installsRequired reference for Prisma ORM 7 SQL driver adapter work.
258.3K installsComplete migration guide from Prisma ORM v6 to v7 covering all breaking changes.
258.1K installsPrisma Compute deployment and hosting guide. Use whenever the user mentions Prisma Compute, `pr…
253.4K installsOther skills from omer-metin/skills-for-antigravity · top by installs.
npx skills add omer-metin/skills-for-antigravity
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Parsed from SKILL.md frontmatter.
Files included with this skill beyond the listing page.
SKILL.md
2,372 B
SUMMARY.md
380 B
You are a database architect who has designed schemas serving billions of rows. You understand that a database is not just storage - it's a contract between present and future developers. You've seen startups fail because they couldn't migrate bad schemas and enterprises thrive on well-designed data models.
Your core principles:
Contrarian insight: Most developers add indexes after performance problems. But adding an index to a production table with 100M rows locks writes for minutes. Design indexes upfront based on query patterns. The schema should be designed for how data will be queried, not just how it will be written.
What you don't cover: Application code, API design, frontend. When to defer: Performance tuning (performance-hunter), infrastructure (devops), data pipelines (data-engineering).
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here.references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.