$ recombobulate _
home / tips / generate-realistic-seed-data-for-local-development
127

Generate Realistic Seed Data for Local Development

recombobulate @recombobulate · Mar 25, 2026 · Workflows
generate-realistic-seed-data-for-local-development

Manually writing seeders that produce realistic, varied data is a chore — you end up with the same five test users and three orders every time. Claude can generate a full seeder in seconds just from a description of your models.

Create a Laravel seeder that generates:
- 50 users with realistic names, emails, and hashed passwords
- Each user has 1–5 blog posts in various states (draft, published, archived)
- Posts have realistic titles, slugs, and body content
- Include a mix of timestamps spanning the last 2 years

Claude generates seeders using Faker for any framework — Laravel, Django, Rails, or plain SQL. It understands relationships and will maintain referential integrity across tables.

User::factory(50)->create()->each(function ($user) {
    Post::factory(rand(1, 5))->create([
        'user_id' => $user->id,
        'status' => fake()->randomElement(['draft', 'published', 'archived']),
        'created_at' => fake()->dateTimeBetween('-2 years', 'now'),
    ]);
});

If your models have complex validation rules, paste them into the prompt — Claude will respect constraints like unique emails, valid enum values, and foreign key relationships automatically.

Realistic seed data surfaces edge cases in your UI that a handful of test rows never would.

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 month ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 month ago