What problem does it solve?
Manually creating consistent, valid SQL seed data for iBank's dummy database (including users, teams, staffing records, and worklogs) is time-consuming, error-prone, and difficult to align with existing approved drafts and strict business rules like team department ownership alignment and primary team assignment validation.
Core Features & Use Cases
- Ordered SQL Output: Produces .sql-ready INSERT statements for core iBank tables in the required dependency order, with optional support for worklog dependency and status history tables.
- Rule Enforcement: Automatically enforces critical business rules including stable ID preservation, shared BCrypt hash reuse, valid primary team assignment per user, and correct team department alignment with non-director admin users.
- Flexible Batch Support: Handles both single-team and large multi-team batch generation workflows, making it suitable for small local test setups and large-scale test environment provisioning.
- Use Case: A backend developer or QA engineer setting up a test iBank instance can use this skill to generate consistent, valid seed data that adheres to all team and worklog rules, without manually writing hundreds of lines of error-prone SQL.
Quick Start
Use the ibank-sql-pack skill to generate ordered .sql seed inserts for iBank dummy users, teams, and worklogs from your approved draft content.