Generate realistic seed data that covers edge cases
Test databases filled with 'John Doe' and '[email protected]' miss the edge cases that break production. This prompt generates a seed data script targeting the boundaries that matter for a given schema.
You are a QA-minded backend engineer. Generate a realistic seed data script for testing a database table or set of tables.
Database engine: {{DB_ENGINE}}
Schema (DDL or description):
```
{{SCHEMA}}
```
Application context (what does this data represent and what does the app do with it):
{{APP_CONTEXT}}
Number of seed rows per main table: {{ROW_COUNT}}
Complete the following:
1. Identify the columns most likely to cause bugs: nullable fields, enums, date ranges, foreign keys with optional references, numeric fields near zero or at type limits, and free-text fields.
2. Ensure the seed data deliberately includes at least one row for each of these edge cases: null optional fields, maximum-length strings, dates at boundaries (epoch, far future, Feb 29), zero and negative numbers where the type allows, and duplicate values where uniqueness is not enforced.
3. Include a realistic distribution of 'normal' rows alongside the edge-case rows so the dataset feels plausible.
4. Output the seed data as executable SQL INSERT statements (or a {{DB_ENGINE}}-compatible seed file format).
5. Add a comment above each edge-case row explaining what it is testing.
6. List any constraints you could not satisfy due to schema rules, and explain why. {{DB_ENGINE}}{{SCHEMA}}{{APP_CONTEXT}}{{ROW_COUNT}}
How to use this prompt
- Copy the prompt above (Copy button on the top-right).
- Replace each
{{VAR}}with your own value. Variables:{{DB_ENGINE}}{{SCHEMA}}{{APP_CONTEXT}}{{ROW_COUNT}}. - Paste it into one of the recommended tools below.
- Iterate: tighten constraints in the prompt if the output is generic.
Why this prompt is structured this way
The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.
Pair this prompt with a tool
Cursor
$20/moAI-first code editor forked from VS Code.
Cursor is VS Code with first-class LLM integration. Multi-file edits, codebase Q&A, autocomplete that's actually useful. The default IDE for many shipping engineers in 2026.
Claude (Anthropic)
$0/mo (Pro at $20)Frontier model with long context and strong reasoning.
Claude (Opus / Sonnet / Haiku tiers) is the assistant favored by writers and engineers who care about reasoning quality and tone. 1M token context on Opus.
ChatGPT (OpenAI)
$0/mo (Plus at $20)The category-defining general-purpose AI assistant.
ChatGPT has the broadest feature surface: image gen, voice, custom GPTs, web browsing, code execution. Often the right default; sometimes beaten on specific tasks by Claude or Perplexity.
The PlaybookPrompts weekly
One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.
Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.