with one click
database-design
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Menu
Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases.
Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.
Token-efficient code review using Tree-sitter AST graphs and MCP. Reduces AI assistant token usage by 6.8ā49x by computing blast radius of changes instead of reading entire codebases. Uses SQLite graph database for structural analysis.
Persistent cross-session memory management. Enables agents to remember user preferences, project conventions, and past decisions across different sessions using a structured MEMORY.md index and topic files.
Multi-agent orchestration patterns. Use when multiple independent tasks can run with different domain expertise or when comprehensive analysis requires multiple perspectives.
Reduce complexity of over-engineered code. Identify unnecessary abstractions, remove dead code, flatten deep nesting, and simplify logic while preserving behavior.
API design principles and decision-making. REST vs GraphQL vs tRPC selection, response formats, versioning, pagination.
| name | database-design |
| description | Database design principles and decision-making. Schema design, indexing strategy, ORM selection, serverless databases. |
| when_to_use | When designing database schemas, choosing ORMs, planning migrations, or optimizing queries. When working with Prisma, Drizzle, or SQL files. |
| allowed-tools | Read, Write, Edit, Glob, Grep |
Learn to THINK, not copy SQL patterns.
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 |
Before designing schema:
ā 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