What problem does it solve? The default sqflite web factory loads sqflite_sw.js and sqlite3.wasm relative to the page and stores everything in one IndexedDB database, which breaks when apps are served from nested routes, need versioned worker files, or require isolated database stores. This Skill guides customization and debugging of sqflite_common_ffi_web beyond those defaults. ## Core Features & Use Cases - Custom Factories: Build factories with createDatabaseFactoryFfiWeb using SqfliteFfiWebOptions for custom sqlite3WasmUri, sharedWorkerUri, and indexedDbName values. - Isolated Stores: Run separate IndexedDB stores (for example production data versus a scratch store) by pairing distinct worker script URLs with distinct store names. - Debugging: Enable sqliteFfiWebDebugWebWorker message logging and inspect the shared worker in Chrome via chrome://inspect/#workers. - Use Case: An app deployed under /app/ with a versioned worker file uses createDatabaseFactoryFfiWeb with sharedWorkerUri '/app/sqflite_sw_v2.js' and sqlite3WasmUri '/app/sqlite3.wasm' so the worker and wasm load correctly after every package upgrade. ## Quick Start Ask the AI to create a custom sqflite web database factory that loads sqflite_sw.js and sqlite3.wasm from a specific path and uses a custom IndexedDB store name.