Claude Cursor opencode Skill

database-design

Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download vodailocz-kilo-kit-mcp-skills_engineering_database-design-0448e6c.zip · 6 KB

Install

skills CLI npx skills add https://github.com/VoDaiLocz/kilo-kit-mcp/tree/main/skills/engineering/database-design
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install vodailocz-kilo-kit-mcp@llmmart
Git git clone https://github.com/VoDaiLocz/kilo-kit-mcp.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole vodailocz/kilo-kit-mcp collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Database Design

Learn to THINK, not copy SQL patterns.

🎯 Selective Reading Rule

Read ONLY files relevant to the request! Check the content map, find what you need.

File Description When to Read
database-selection.md PostgreSQL vs Neon vs Turso vs SQLite Choosing database
orm-selection.md Drizzle vs Prisma vs Kysely Choosing ORM
schema-design.md Normalization, PKs, relationships Designing schema
indexing.md Index types, composite indexes Performance tuning
optimization.md N+1, EXPLAIN ANALYZE Query optimization
migrations.md Safe migrations, serverless DBs Schema changes

⚠️ Core Principle

  • ASK user for database preferences when unclear
  • Choose database/ORM based on CONTEXT
  • Don't default to PostgreSQL for everything

Decision Checklist

Before designing schema:

  • Asked user about database preference?
  • Chosen database for THIS context?
  • Considered deployment environment?
  • Planned index strategy?
  • Defined relationship types?

Anti-Patterns

❌ Default to PostgreSQL for simple apps (SQLite may suffice) ❌ Skip indexing ❌ Use SELECT * in production ❌ Store JSON when structured data is better ❌ Ignore N+1 queries

Files (kilo-kit-mcp)
  • scripts
    • schema_validator.py 5.2 KB
      Loading…
  • database-selection.md 1.1 KB
    Loading…
  • indexing.md 892 B
    Loading…
  • migrations.md 1.1 KB
    Loading…
  • optimization.md 902 B
    Loading…
  • orm-selection.md 771 B
    Loading…
  • schema-design.md 1.4 KB
    Loading…
  • SKILL.md 1.5 KB
    ---
    name: database-design
    description: Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
    allowed-tools: Read, Write, Edit, Glob, Grep
    ---
    
    # Database Design
    
    > **Learn to THINK, not copy SQL patterns.**
    
    ## 🎯 Selective Reading Rule
    
    **Read ONLY files relevant to the request!** Check the content map, find what you need.
    
    | File | Description | When to Read |
    |------|-------------|--------------|
    | `database-selection.md` | PostgreSQL vs Neon vs Turso vs SQLite | Choosing database |
    | `orm-selection.md` | Drizzle vs Prisma vs Kysely | Choosing ORM |
    | `schema-design.md` | Normalization, PKs, relationships | Designing schema |
    | `indexing.md` | Index types, composite indexes | Performance tuning |
    | `optimization.md` | N+1, EXPLAIN ANALYZE | Query optimization |
    | `migrations.md` | Safe migrations, serverless DBs | Schema changes |
    
    ---
    
    ## ⚠️ Core Principle
    
    - ASK user for database preferences when unclear
    - Choose database/ORM based on CONTEXT
    - Don't default to PostgreSQL for everything
    
    ---
    
    ## Decision Checklist
    
    Before designing schema:
    
    - [ ] Asked user about database preference?
    - [ ] Chosen database for THIS context?
    - [ ] Considered deployment environment?
    - [ ] Planned index strategy?
    - [ ] Defined relationship types?
    
    ---
    
    ## Anti-Patterns
    
    ❌ Default to PostgreSQL for simple apps (SQLite may suffice)
    ❌ Skip indexing
    ❌ Use SELECT * in production
    ❌ Store JSON when structured data is better
    ❌ Ignore N+1 queries
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.