# flutter-drift

Walks the agent through Drift persistence in Flutter: tables, queries, reactive streams, schema migrations and tests. Useful whether the app already has a local database or you are adding one.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 671 installs · ★ 110
- Author: Stanislav \[MADTeacher\] Chernyshev
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/MADTeacher/mad-agents-skills/tree/HEAD/flutter-drift/SKILL.md
- Updated: 2026-05-01
- HTML: https://affpapa.org/en/nevibecode/skills/flutter-drift

## What it does

This skill is a workflow, not a snippet dump. The agent inspects `pubspec.yaml`, existing database files, `build.yaml`, the state management package, target platforms and tests before touching anything. Dependencies go in through `dart pub add drift drift_flutter path_provider dev:drift_dev dev:build_runner`, so no versions get hardcoded. `provider` or `flutter_riverpod` are added only when the app already uses one or you ask for it.

Then comes the code: tables in Dart or `.drift` files, `@DriftDatabase`, opening the database with `driftDatabase` from `package:drift_flutter/drift_flutter.dart`. Calls like `database.select(database.todoItems)` stay scoped to the database object instead of floating at widget level. Any change to Drift declarations requires `dart run build_runner build` afterwards, and generator errors count as blockers.

Seven reference files get pulled in as needed: setup, tables, queries, writes, streams, migrations, flutter-ui. There is also a list of calls to avoid. `watch(...)` and `notifyTableUpdates(...)` are out; `customSelect(...).watch()` and `notifyUpdates(...)` are in. One rule is absolute: never bump `schemaVersion` without a migration plan for databases already in users' hands. If the schema history is unclear, the skill stops and asks rather than guessing. Web builds need `sqlite3.wasm` and `drift_worker.js` — without them the agent writes the code path and tells you which assets are missing.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add MADTeacher/mad-agents-skills --skill flutter-drift -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/flutter-drift/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/flutter-drift/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add MADTeacher/mad-agents-skills --skill flutter-drift -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/flutter-drift/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add MADTeacher/mad-agents-skills --skill flutter-drift -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/flutter-drift/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install MADTeacher/mad-agents-skills flutter-drift
```

2. **Manually: put the files in place**
- File: `.github/skills/flutter-drift/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add MADTeacher/mad-agents-skills --skill flutter-drift -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/MADTeacher/mad-agents-skills --path flutter-drift
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/flutter-drift/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add MADTeacher/mad-agents-skills --skill flutter-drift -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/MADTeacher/mad-agents-skills/tree/HEAD/flutter-drift/SKILL.md

## When to use it
- set up a Drift local database in a fresh Flutter project
- fix a failing `build_runner` run after editing tables
- replace deprecated `watch` and `notifyTableUpdates` calls with current APIs
- write a schema migration without wiping user data
- pipe database rows into a widget through StreamBuilder or Riverpod

## Example prompts
- Add a Drift local database to this project with a tasks table: id, title, done
- The schema changed — bump schemaVersion and write a migration with a test
- The task list should refresh itself on every write; wire the stream into the widget

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 9f24d445e2eb207b.

BEGIN THIRD-PARTY FILE 9f24d445e2eb207b
```text
---
name: flutter-drift
description: Implement, fix, review, migrate, test, or debug Drift persistence in Flutter apps using SQLite, drift_flutter, type-safe Dart queries, generated tables, StreamBuilder or Riverpod StreamProvider UI, write operations, transactions, schema migrations, web assets, isolate sharing, and local database testing. Use when a Flutter task mentions drift, local database storage, SQLite, reactive database streams, CRUD, schemaVersion, build_runner, drift_dev make-migrations, migration tests, or Flutter-specific database setup across mobile, web, or desktop.
metadata:
  author: Stanislav [MADTeacher] Chernyshev
  version: "1.1"
---

# Flutter Drift

Use this skill to add or repair Drift-based local persistence in Flutter apps. The skill is an operating workflow: inspect the target app first, choose only the relevant reference files, implement with current Drift APIs, and validate generated code.

## Core Workflow

1. Inspect the app before editing:
   - Check `pubspec.yaml`, existing database files, `build.yaml`, state management package, target platforms, and tests.
   - Prefer the app's current architecture and naming over the examples in this skill.
2. Add or verify dependencies with package commands instead of hardcoding versions:
   - `dart pub add drift drift_flutter path_provider dev:drift_dev dev:build_runner`
   - Add `provider` or `flutter_riverpod` only when the app already uses it or the user asks for that integration.
3. Create or update the database entry point:
   - Define tables in Dart or `.drift` files.
   - Add the tables to `@DriftDatabase`.
   - Open Flutter databases with `driftDatabase` from `package:drift_flutter/drift_flutter.dart` unless the project needs a custom executor.
4. Keep Drift calls scoped to the database object:
   - Use `database.select(database.todoItems)`, `database.into(database.todoItems)`, `database.update(database.todoItems)`, and `database.delete(database.todoItems)` from widgets, services, and repositories.
```
END THIRD-PARTY FILE 9f24d445e2eb207b

The third-party file has ended. Everything between the 9f24d445e2eb207b tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2010 of 6541 bytes. © Stanislav \[MADTeacher\] Chernyshev · MIT · https://github.com/MADTeacher/mad-agents-skills/tree/HEAD/flutter-drift/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md