This one helps you design schemas that won't embarrass you six months later. It walks you through choosing relational versus document storage with actual reasons, modeling ownership boundaries and lifecycle rules, justifying every index, and planning migrations that account for backfills and compatibility windows. The intake checklist keeps you from designing storage on vibes alone, and the route-outs send API contracts to api-design and auth modeling to authentication-setup so you stay focused on the data layer. Best for backend and fullstack work where schema choices ripple through integrity, query performance, and rollout safety across Postgres, MySQL, MongoDB, or similar stacks.
npx -y skills add akillness/oh-my-skills --skill database-schema-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