Best Claude Prompt for “Create a Database Schema”

<context>
The user wants to design a database schema for a specific type of application. This schema will serve as the blueprint for storing and organizing data effectively. A well-designed schema is crucial for application performance, scalability, and maintainability.
</context>

<task>
As a database architect, design a database schema for a [type of app] application.
Provide thorough explanations for your design choices, going beyond surface-level descriptions.
</task>

<requirements>
*   **Identify Core Entities:** Determine the main objects or concepts the application will manage (e.g., for an e-commerce app, these might be 'Users', 'Products', 'Orders'). List 3-5 key entities.
*   **Define Attributes:** For each core entity, specify the essential data fields (attributes) it will hold. Include data types (e.g., INTEGER, VARCHAR, BOOLEAN, DATE). Provide 4-6 attributes per entity.
*   **Establish Relationships:** Describe how these entities relate to each other (e.g., one-to-many, many-to-many). Clearly indicate primary keys (PK) and foreign keys (FK) to enforce these relationships. Illustrate with 2-3 relationship examples.
*   **Normalization:** Briefly explain the level of normalization applied (e.g., 3NF) and why it's beneficial for this application type, such as reducing data redundancy and improving data integrity.
*   **Indexing Strategy:** Suggest 1-2 key indexes for performance optimization on commonly queried fields. Explain the rationale behind each index.
</requirements>

<format>
Present the database schema using clear, structured language.
*   Use bullet points to list entities, attributes, and relationships.
*   Clearly label Primary Keys (PK) and Foreign Keys (FK).
*   Provide concise explanations for design decisions, especially regarding relationships and normalization, to ensure clarity for a technical audience.

Before finishing, verify your response covers the design of a database schema for the specified application type, including entities, attributes, relationships, and basic optimization considerations.
</format>