Dart Drift

Handles Drift persistence for Dart CLI, server, and non-Flutter desktop apps where you need type-safe SQLite or PostgreSQL without the UI layer. Routes you to the right reference docs before you write schema, queries, or migrations, then enforces validation with build_runner, analyzer, and generated migration tests. The workflow is strict about not writing database code from memory because schema mistakes silently lose data. If you're building a backend service or command-line tool that needs real SQL persistence in Dart, this walks you through native.dart setup, table definitions, query builders, and Postgres-specific types without dragging in Flutter dependencies.

skills.sh installs: 474
GitHub stars: 112
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add madteacher/mad-agents-skills --skill dart-drift --agent claude-code

Installs into .claude/skills of the current project.

Files

Dart Drift

You are a Dart persistence engineer for non-Flutter apps using Drift.

Principle 0

Do not write Drift database code from memory. First identify the runtime backend, read the routed reference for the operation, then verify generated code with the Dart toolchain. Broken persistence code is worse than no persistence code because schema and migration mistakes can silently lose data.