Plan a database schema from requirements for Media & Entertainment

Your prompt is ready 4 brackets to fill

You are a senior database architect, working with audiences, advertisers and creators at a media studio publishing video and podcasts.

## Goal
Design a clean, normalised database schema for a new feature or app, ready to turn into migrations.

## What matters in Media & Entertainment
- Rules and standards that usually apply: copyright and licensing for music and footage; the limits of fair use; platform policies (YouTube, Spotify, Instagram); disclosure of sponsored content; defamation and privacy law.
- Common risks to plan for: copyright strikes; algorithm changes; creator burnout; missed release dates; brand-safety problems.
- Tools commonly used: YouTube Studio; Spotify for Podcasters; Premiere Pro or DaVinci Resolve; Canva; social schedulers.
- Words people in this field use: hook; thumbnail; CTR; retention curve; episode; sponsor read; licensing; release schedule.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- What the app does: [DESCRIBE THE APP OR FEATURE]
- Main things it stores: [e.g. customers, orders, products]
- Database: [MySQL / PostgreSQL / MongoDB / other]
- Expected size: [ROWS PER MONTH OR USERS]

## What to do
1. List every entity and what it represents in one line.
2. Define the tables with columns, data types, nullability and defaults.
3. Add primary keys, foreign keys, unique constraints and the indexes each common query needs.
4. Explain each relationship (one-to-many, many-to-many) and how deletes should cascade.
5. Check the design against the five most common queries the app will run.

## What to deliver
- A table-by-table schema in a markdown table
- The SQL CREATE TABLE statements (or the collection design for NoSQL)
- An entity-relationship diagram in Mermaid syntax
- A short list of trade-offs you made and when to revisit them

## Rules
- Keep copyright, licensing and release schedules in mind throughout, and point out anything in my plan that would break them.
- Where it fits, connect your recommendations to audience retention and watch time.
- Use plain language and short sentences. Use headings and tables where they make the answer easier to scan.
- Do not invent figures, laws, sources or quotes. Mark anything you had to assume with "Assumption:".
- If something important is missing, ask me up to 3 short questions before you start.

## Before you answer
Check your draft against this list and fix anything that fails:
- The code works as written: no invented libraries, functions or APIs, and versions are named where they matter.
- It is written for a media studio publishing video and podcasts; nothing in it would read the same for any other business.
- Every item under "What to deliver" is included.

Open in ChatGPT Claude Perplexity

How to use this prompt

Copy the prompt. Press Copy prompt and the full text goes to your clipboard.
Fill the brackets. Use the form above, or replace [DESCRIBE THE APP OR FEATURE], [e.g. customers, orders, products], [MySQL / PostgreSQL / MongoDB / other], [ROWS PER MONTH OR USERS] with your own details.
Paste and send. Paste it into ChatGPT, Claude, Microsoft Copilot and DeepSeek and send. Ask follow-up questions to refine the answer.

Why this prompt works

The “Plan a database schema from requirements” prompt tells the assistant exactly what to hand back: a table-by-table schema in a markdown table; the SQL CREATE TABLE statements (or the collection design for NoSQL); an entity-relationship diagram in Mermaid syntax; and a short list of trade-offs you made and when to revisit them. It makes the assistant work through 5 steps in order, starting with "list every entity and what it represents in one line", instead of jumping straight to an answer. Before replying, the assistant checks its draft against 3 tests and fixes anything that fails.

This version is written for a media studio publishing video and podcasts, so the assistant keeps copyright, licensing and release schedules in mind and judges the result by audience retention and watch time. If an important detail is missing, it asks you up to 3 short questions before it starts.

How to get the best answer

Fill every bracket with real detail: [DESCRIBE THE APP OR FEATURE], [e.g. customers, orders, products], [MySQL / PostgreSQL / MongoDB / other] and the rest should hold real names, numbers and dates, not placeholders.
Paste real material: where the prompt asks for notes, data or text, paste the actual content rather than a summary.
Refine in the same chat: ask "make it shorter", "turn it into a table" or "add more detail on step 2".
Check the result: review it against what you know about audience retention and watch time before you share it.

Other industries

Same prompt for other industries

The same plan a database schema from requirements prompt, rewritten for each industry.

FAQ

Frequently asked questions

Which AI assistant works best with the “Plan a database schema from requirements” prompt?

The “Plan a database schema from requirements” prompt works in any chat assistant and suits ChatGPT, Claude, Microsoft Copilot and DeepSeek best. Paste it in, send it, and ask follow-up questions in the same chat to refine the answer.

What do I fill in before sending the “Plan a database schema from requirements” prompt?

Replace the 4 highlighted brackets – [DESCRIBE THE APP OR FEATURE], [e.g. customers, orders, products], [MySQL / PostgreSQL / MongoDB / other], [ROWS PER MONTH OR USERS] – with your own details. The more specific you are, the better the answer.

Is the “Plan a database schema from requirements” prompt only for Media & Entertainment?

No. This version is written for a media studio publishing video and podcasts, and the same prompt is also written for 15 other industries, listed on this page.

Is the “Plan a database schema from requirements” prompt free to use?

Yes. First AI Prompt prompts are free to copy and use in personal and business work, with no sign-up, no account and no daily limit.

Can I trust the answer the “Plan a database schema from requirements” prompt gives?

Treat it as a strong first draft: the prompt tells the assistant not to invent facts and to mark its assumptions, but check figures yourself, especially anything with legal, financial or safety consequences.

Keep exploring