| name | turso |
| description | Turso and libSQL patterns for embedded SQLite-compatible databases, serverless drivers, sync engines, partial sync, WAL/MVCC behavior, compatibility gaps, CLI usage, and Drizzle integration boundaries. Use when mentioning Turso, libSQL, @libsql/client, remote SQLite, embedded replicas, or local database sync. |
| metadata | {"author":"epicenter","version":"1.0"} |
Turso And libSQL
Reference Repositories
- Turso - SQLite-compatible database platform and libSQL ecosystem
- Drizzle ORM - ORM commonly used with libSQL and Turso
Upstream Grounding
When Turso sync behavior, libSQL driver behavior, embedded replicas, partial sync, concurrency, compatibility, or CLI behavior affects correctness, use source-backed grounding before relying on memory. If DeepWiki MCP is available, ask a narrow question against tursodatabase/turso; for Drizzle's libSQL adapter or typed query surface, ask against drizzle-team/drizzle-orm. If DeepWiki is unavailable or the repo is not indexed, use upstream source or official docs directly. Treat DeepWiki as orientation, then verify decisive details against local driver versions, installed types, source, or official docs before changing code.
Use the drizzle-orm skill for schema and query builder decisions.
Driver Boundaries
- Treat Turso/libSQL as SQLite-compatible, not identical to every local SQLite deployment.
- Serverless client usage has network and auth behavior. Keep it behind the runtime boundary that owns secrets.
- Embedded replicas and sync engines have lifecycle and consistency behavior. Document when data is local, when it syncs, and which writes are accepted.
