Database Schema Design
Stating query patterns upfront produces correctly indexed schemas. The 'one thing to change at scale' question surfaces design decisions you'll need to revisit later.
Design a database schema for {{feature_description}}. Requirements: {{list your requirements}} Constraints: - Database: {{PostgreSQL/MySQL/MongoDB}} - Expected data volume: {{e.g., "10K users, 1M records"}} - Key query patterns: {{e.g., "filter by date range", "full-text search on title"}} Provide: 1. Table definitions with column types, constraints, and indexes 2. Relationships (foreign keys, junction tables for many-to-many) 3. Indexes optimized for the stated query patterns 4. Migration SQL that can run directly 5. One thing I might need to change as the app scales
Variables to customize
Why this prompt works
Stating query patterns upfront produces correctly indexed schemas. The 'one thing to change at scale' question surfaces design decisions you'll need to revisit later.
What you get when you save this prompt
Your workspace unlocks powerful tools to iterate and improve.
AI Optimization
One-click improvement with structure analysis and pattern suggestions.
Version History
Track every edit. Compare versions side-by-side with word-level diffs.
Folders & Tags
Organize your library with nested folders, tags, and drag-and-drop.
$ npm i -g @promptingbox/mcpUse Everywhere
Access prompts from Claude, Cursor, ChatGPT & more via MCP integration.
Your prompts, organized
Save, version, and access your best prompts across ChatGPT, Claude, Cursor, and more.