skills.rest
uesleinasch
uesleinaschCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

database-design

Guide teams through database schema, indexing, and ORM design decisions.

Updated Mar 31, 2026
Search Tags:#design#indexing#database#serverless#schema#orm#normalization
One-click install
npx skills add https://github.com/uesleinasch/unac-agents --skill database-design-uesleinasch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: database-design
Source: https://github.com/uesleinasch/unac-agents/tree/main/skills-shared/database-design
Command: npx skills add https://github.com/uesleinasch/unac-agents --skill database-design-uesleinasch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill guides teams through thoughtful database design, helping decide schemas, indexing strategies, ORM choices, and deployment patterns to avoid common pitfalls and improve long-term maintainability.

Core Features & Use Cases

  • Selective Reading Rule: Read only files relevant to the request to avoid over-reading and ensure focused analysis.
  • Decision Checklist: A structured set of criteria to validate normalization, keys, relationships, and indexing before committing to a design.
  • Anti-Patterns & Guidance: Highlights common mistakes (over-normalization, missing indexes, inappropriate ORM usage) with practical alternatives.

Quick Start

Analyze a new project's data requirements and output a recommended database design, including schema choices, indexing strategy, and ORM fit.

Frequently Asked Questions about database-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a database schema for a new software project?▼

Database schema design is guided by a structured decision checklist that validates normalization, keys, relationships, and indexing to ensure robust project data modeling and architecture.

What's the best way to choose an ORM for my database architecture?▼

The best way to choose an ORM is through thoughtful selection that balances performance and maintainability, avoiding inappropriate ORM usage by validating fit against your specific database deployment patterns.

When do I need database normalization and proper indexing in schema design?▼

You need database normalization and proper indexing in schema design when building software projects of varying scale to enforce best practices, avoid common anti-patterns, and improve long-term maintainability.

Can I use serverless database choices for projects of varying scale and deployment models?▼

Yes, serverless database choices apply across software projects of varying scale and deployment models, guiding teams through thoughtful decisions to balance performance and maintainability.

What are common database design anti-patterns and how do I avoid them?▼

Common database design anti-patterns include over-normalization, missing indexes, and inappropriate ORM usage, which you avoid by applying practical alternatives and a structured validation checklist.

Related Skills

Explore More Software Engineering Skills→
HechaoYannetHechaoYannet

create-architecture

Generate a master architecture document from GDDs, ADRs, and governance constraints.

Community
Advanced
MacPhobosMacPhobos

Neon Serverless Postgres Skill

Create and manage Neon Serverless Postgres databases with connection strings and ORM integrations.

Community
Advanced
AreteDriverAreteDriver
4

web-backend-builder

Build backend APIs with FastAPI, Flask, or Express, including database design and JWT authentication.

Community
Advanced
pascallammerspascallammers
1

database-design

Design normalized relational and NoSQL database schemas with indexes and migrations.

Community
Advanced