eng-add-persisted-model

To add a persisted record type in Flutter, you define the Drift table class, implement the DAO, and write repository transaction bodies. This Skill automates that entire workflow, ensuring schema integrity and transactional consistency for new domain records like Cards or ReviewLogs.

Drift schema management enforces data integrity by applying STRICT tables, CHECK constraints, foreign keys, and indices. This Skill automates these constraints when generating new domain records, ensuring the database schema remains robust and consistent during migrations.

Yes, you need both Dart and Drift to automate database repository transactions. Drift provides the SQLite abstraction and schema management, while Dart handles the repository transaction bodies and DAO methods required for persistent data operations.

The best way to create Drift migrations for new domain records is to automate the generation of table classes, DAOs, and repository transactions together. This ensures schema integrity and transactional consistency, preventing manual migration errors when adding records like Cards.

Yes, this Skill generates DAO methods and repository transaction bodies for existing Flutter data persistence layers. It integrates new domain records into the current Drift database schema while maintaining strict constraints and transactional consistency.

Adding a new Drift table requires updating the repository layer to maintain transactional consistency. Without corresponding DAO methods and transaction bodies, the new persisted record type cannot safely interact with the database schema, risking data integrity.