StructuredFor DevelopersDatabases & Data Engineering

Database Schema Designer.

When starting a new application and designing the data model — good schema design is 10x harder to fix retroactively.

ChatGPT · Claude · Gemini·Beginner·~200 tokens
Curated by the AIPP team
Last updated 14 May 2026 · v3
database-schema-designer.md · 200 words
You are a senior {{role}} brought in to help {{target_user}} complete a Database Schema Designer.

# Context
Original working context:
- Act as a data architect. Design a relational database schema for {{describe_the_domain}}. Include: (1) all tables with column names, types, constraints (PK, FK, NOT NULL, UNIQUE), (2) normalisation decisions — explain any deliberate denormalisation, (3) indexing strategy for common query patterns, (4) audit trail design (created_at, updated_at, soft delete pattern),
- 5. SQL DDL statements to create the full schema.

# Goal
Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use.

# Constraints
- Use the user's variables exactly where relevant.
- Avoid generic filler and vague advice.
- Be specific to the stated audience, platform, market, role, industry, or situation.
- Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue.

# Output
Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.

The variables to fill in

PlaceholderWhat to put thereExample
{{describe_the_domain}}Describe the domaininsert your specific value
{{role}}Rolefreelance client onboarding strategist
{{target_user}}Target usera freelance consultant

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone — formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When starting a new application and designing the data model — good schema design is 10x harder to fix retroactively.

PRO TIP

Add created_at and updated_at to every table from day one — you will always eventually need them and they are expensive to add retroactively.

Related prompts

Structured

Blog Post Drafting Engine

Write a complete, SEO-optimised blog post on the given topic. Include a compelling headline, an engaging introduction, 4-5 subheadings with detailed body paragraphs, and a strong conclusion with a cal

Structured

Email Newsletter Writer

Write a complete email newsletter including subject line, preview text, opening hook, main body content (3 short sections), and a clear call to action.

Structured

YouTube Video Script Writer

Write a complete YouTube video script including a strong hook (first 30 seconds), structured main content with transitions, and a closing that encourages likes, comments, and subscriptions.

Structured

LinkedIn Article Builder

Write a complete LinkedIn article that establishes professional authority, shares a genuine insight, and encourages professional discussion.

★ THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth — built by developers for developers.

Browse more prompts →