What problem does it solve? Resetting or initializing a Toollab database requires knowing which of the six seeders to run, in what order, and how to create the first super-admin on an empty base where no in-app signup exists. Running the wrong seeder in production injects demo data, and skipping RoleSeeder breaks school creation with a 500 error. ## Core Features & Use Cases - Seeder selection guide: Documents the role of each seeder (RoleSeeder, ToollabSeeder, DemoSeeder, AlQalamSeeder, ProductionSeeder, DatabaseSeeder) and which are safe for production versus dev-only. - Super-admin bootstrap: Explains the idempotent toollab:create-super-admin Artisan command that creates or resets super-admin accounts derived from the SUPER_ADMIN_EMAILS env variable. - Ready-to-run sequences: Provides copy-paste command sequences for dev reset with demo data, clean dev base, and production initialization of a new instance. - Use Case: A developer needs a realistic multi-school, multi-year dataset with closed school years to test archive and read-only features; the Skill directs them to DemoSeeder and explains its invariants and purge safeguards. ## Quick Start Ask the assistant to reset the dev database with demo data or to initialize a fresh production instance, and it will provide the exact Artisan commands to run.