Safer database changes for non-Flutter Dart apps.
Guides changes to non-Flutter Dart persistence code with backend-specific patterns and mandatory database validation.
When to use it
Use when adding, fixing, auditing, or migrating Drift persistence in Dart CLI, server-side, or non-Flutter desktop applications.
It changes how the agent implements Dart database work by inspecting the project, choosing backend-specific references, making small changes, and validating them.
What you provide
Requires the Dart toolchain to resolve dependencies, generate database code, analyze changes, and run relevant tests.
No additional actions listed.