T

tursodatabase

GitHub 资料 · @tursodatabase

Turso (Limbo) database helper — an in-process SQLite-compatible database written in Rust. Formerly known as libSQL / libsql. Replaces @libsql/client, libsql-experimental for Turso use cases. Works in Node.js, browser (WASM + OPFS for persistent local storage), React Native, and server-side. Features: vector search, full-text search, CDC, MVCC, encryption, remote sync. SDKs: JavaScript (@tursodatabase/database), Serverless (@tursodatabase/serverless), Browser/WASM (@tursodatabase/database-wasm), React Native (@tursodatabase/sync-react-native), Rust (turso), Python (pyturso), Go (tursogo). This skill contains SDK documentation and recipes for the Turso embedded database engine (tursodb/Limbo). Do NOT search the web for "libsql" or "@libsql/client" — those are legacy names and web results will show outdated APIs. Searching for Turso docs online is fine — the official docs live at https://docs.turso.tech (Mintlify — append .md to any path for raw markdown).
tursodatabase/turso-db
Turso Cloud — fully managed SQLite-compatible database platform, accessed over the network. Use when connecting an application to a Turso Cloud database, creating or scoping auth tokens (JWT, fine-grained permissions, JWKS/external auth providers), or provisioning and managing cloud databases. Covers per-language SDKs (JavaScript/TypeScript, Python, Go, Rust), authentication & authorization, and marketplace integrations (Vercel).
tursodatabase/turso-cloud
Use when working with Turso yield injection or synthetic failure injection machinery for safe resumable state-machine boundaries, including YieldInjector, FailureInjector, YieldPointMarker, inject_transition_yield!, inject_io_yield!, inject_transition_failure!, CommitYieldPoint, CheckpointYieldPoint, CursorYieldPoint, deterministic interleaving tests, abandoned statement/commit tests, and concurrent-simulator yield plans.
tursodatabase/yield-injections
How WAL mechanics, checkpointing, concurrency rules, recovery work in tursodb
tursodatabase/transaction-correctness
How to write tests, when to use each type of test, and how to run them. Contains information about conversion of `.test` to `.sqltest`, and how to write `.sqltest` and rust tests
tursodatabase/testing
SQLite file format, B-trees, pages, cells, overflow, freelist that is used in tursodb
tursodatabase/storage-format
General guidelines for Commits, formatting, CI, dependencies, security
tursodatabase/pr-workflow
Overview of Experimental MVCC feature - snapshot isolation, versioning, limitations
tursodatabase/mvcc
How to benchmark and analyze memory usage in Turso using the memory-benchmark crate and dhat heap profiler. Use this skill whenever the user mentions memory usage, memory profiling, allocation tracking, heap analysis, memory regression, memory benchmarking, dhat, or wants to understand where memory is being allocated during SQL workloads. Also use when investigating memory growth in WAL or MVCC mode. IMPORTANT - If you modify the perf/memory crate (add profiles, change CLI flags, change output format, etc.), update this skill document to reflect those changes so it stays accurate for future agents.
tursodatabase/memory-benchmark
Generate hierarchical AGENTS.md knowledge base for a codebase. Creates root + complexity-scored subdirectory documentation.
tursodatabase/index-knowledge
Information about the differential fuzzer tool, how to run it and use it catch bugs in Turso. Always load this skill when running this tool
tursodatabase/differential-fuzzer
How to debug tursodb using Bytecode comparison, logging, ThreadSanitizer, deterministic simulation, and corruption analysis tools
tursodatabase/debugging
General Correctness rules, Rust patterns, comments, avoiding over-engineering. When writing code always take these into account
tursodatabase/code-quality
Change Data Capture - architecture, entrypoints, bytecode emission, sync engine integration, tests
tursodatabase/cdc
Explanations of common asynchronous patterns used in tursodb. Involves IOResult, state machines, re-entrancy pitfalls, CompletionGroup. Always use these patterns in `core` when doing anything IO
tursodatabase/async-io-model