What problem does it solve? Flutter apps that need SQLite on desktop and mobile via the ffi implementation face manual factory setup, per-isolate database instances, and plugin registration pitfalls. This Skill explains how package:sqflite_ffi auto-registers sqfliteDatabaseFactoryFfi and shares one sqflite isolate across all Flutter isolates. ## Core Features & Use Cases - Automatic plugin registration: SqfliteFfiPlugin.registerWith() runs sqfliteFfiInit() and sets the global databaseFactory on Windows, Linux, macOS, Android, and iOS with no main() code. - Cross-isolate sharing: One sqflite isolate is shared between the main isolate, compute, and Isolate.run via IsolateNameServer, preserving singleInstance semantics and transaction ordering. - Package selection guidance: Clear criteria for choosing between sqflite, sqflite_common_ffi, sqflite_ffi, and sqflite_common_ffi_web, plus coexistence rules when both native and ffi plugins are present. - Use Case: A Flutter desktop app runs heavy inserts in a compute isolate while the main isolate holds an open transaction; with rollbackActiveTransactionOnOpen: false and the shared factory, both isolates write to the same database in order. ## Quick Start Add sqflite_ffi to my Flutter app's pubspec.yaml and show me how to open a database from both the main isolate and a compute isolate sharing one instance.