Realistic seed data generator

Model notes: Any model; for local and demo databases only, never production

Fill in the variables (optional — they're inserted live below):

Generate realistic seed data for local development and demos. Schema / models: {{schema}} Records per table: {{record_count}} Output format: {{format}} Rules: - Respect every constraint: types, required fields, unique values, and foreign keys that point to rows that exist. - Make it look real: varied lengths, some empty optional fields, and edge cases (very long names, non-English characters, dates near month and year boundaries). - Use made-up names and obviously fake contact details (example.com emails, phone numbers from reserved fictional ranges). Don't use well-known people or real companies. - Return a file or script I can run to load the data, then a short note on which rows cover which edge case.

How to use it

  1. Fill the variables above, or replace each {{variable}} after pasting.
  2. Paste into your AI tool (ChatGPT, Claude, Gemini, Cursor, Claude Code, or a local model in Ollama/LM Studio).
  3. Review the output. Models make mistakes, especially with facts, numbers and code.
Pro Prompt Pack · US$12

Get all 209 prompts + agent workflows

Every prompt as Markdown and JSON, 10 multi-step agent workflows, and 12 ready-made slash commands for Cursor and Claude Code. Instant zip download, one-time purchase.

Buy the Pro Pack for US$12 What's inside

More Vibe coding prompts

Vibe coding

Spec-first app kickoff

Any frontier model; works in Cursor, Claude Code, Windsurf

Variables: ideausersstack

You are a senior engineer starting a new project with me. Before writing any code, produce a short build spec.

Project idea: {{idea}}
Target users: {{users}}
Preferred stack (or "you choose"): {{stack}}

Write:
1. One-paragraph product summary.
2. MVP feature list (max 7), each with a one-line acceptance test.
3. Explicit out-of-scope list.
4. Data model (entities + key fields).
5. File/folder structure.
6. Step-by-step build plan in small commits, each independently runnable.
7. Open questions you need me to answer.

Do not write code yet. Wait for my "go".
Open & fill variables: Spec-first app kickoff →
Vibe coding

One small step at a time

Reduces runaway edits in agent mode

Variables: step_numberstep_description

Implement only step {{step_number}} of the plan we agreed: "{{step_description}}".

Rules:
- Touch the fewest files possible. List the files you will change before changing them.
- Don't refactor, rename or reformat anything unrelated.
- After the change, tell me exactly how to run/verify it (command + expected result).
- If something in the plan looks wrong, stop and say so instead of improvising.
Open & fill variables: One small step at a time →
Vibe coding

Turn a screenshot into a component

Needs a vision-capable model

Variables: frameworkstyling

Recreate the UI in the attached screenshot as a {{framework}} component styled with {{styling}}.

- Match layout, spacing, hierarchy and colours as closely as possible; approximate fonts with system fonts.
- Use semantic HTML and accessible labels.
- Make it responsive: describe what changes below 640px.
- Use placeholder data in a typed props object, not hard-coded strings.
- Return a single file, then list anything you couldn't infer from the image.
Open & fill variables: Turn a screenshot into a component →

New prompts every week

One short email a week: new tested prompts and agent workflows. Free. Unsubscribe any time.

Subscribe free →