frankensqlite-mega-skill
Made by JeffWork on or with FrankenSQLite (fsqlite), the Rust SQLite rewrite with MVCC concurrent writers. Use when fixing engine bugs, adding SQL features, running harnesses, or embedding fsqlite downstream.
From Jeffrey's Skills.md: professionally crafted skills for any AI agent, installed and kept in sync by the jsm CLI. Subscription only, $20/month.
Works With
Quality and Utility come from canonical skill metadata. Community ratings appear separately as stars when subscriber reviews exist.
Subscribe to download
Public previews are available, but downloads, CLI sync, and premium content require an active subscription.
Sign In to Subscribe- Full skill content with deterministic versioning
- CLI sync + local search index
- Access to Jeffrey’s premium library
Save to your account
Saved skills live in your cloud list. Run jsm sync on each machine to pull them locally.
What's New with this Skill
1Updates, enhancements, and release notes for this skill.
New: FrankenSQLite Mega Skill, the operator's map to fsqlite and its concurrent writers
FrankenSQLite (fsqlite) exists to remove one lock: SQLite's global WAL_WRITE_LOCK. This skill is the working map for agents on either side of that engine, whether fixing bugs in a 258k-line connection.rs or embedding fsqlite downstream and handling the Busy/BusySnapshot retry family correctly. Twenty-three references cover the MVCC/SSI core, the storage stack, the conformance harness, and the discipline for classifying which surfaces are live, dormant, or design-only.
- One invariant organizes everything: page-level MVCC plus Serializable Snapshot Isolation replaces the global write lock, so writers touching disjoint pages commit in parallel.
- The downstream contract up front: plain BEGIN auto-promotes to BEGIN CONCURRENT, and contention surfaces as the typed Busy/BusySnapshot retry family, never a hang.
- Connection is !Send by design: one connection per worker, with your asupersync runtime polling fsqlite's futures; the engine never spawns its own.
- Repo lane rules before any engine edit: file-deletion ban, the concurrent-mode invariant, and multi-agent etiquette; connection.rs is ~258k lines and meant to be grepped, not read.
- Status ledger before claims: the codebase is an honest hybrid of live, dormant, and design surfaces, and correct classification is half the job.
- 23 references span the MVCC core, storage stack, SQL frontend and VDBE, extensions and vtabs, pragma surface, file-format quirks, and an incident corpus with operator cards.
- Performance talk is gated by PERF-CLAIMS-DISCIPLINE: harness evidence or no claim.
fsqlite is an independent, clean-room Rust reimplementation of SQLite whose reason for existing is a single invariant: page-level MVCC plus Serializable Snapshot Isolation instead of a global write lock, so writers touching disjoint pages commit in parallel. Downstream code sees a small, sharp contract. Plain BEGIN auto-promotes to BEGIN CONCURRENT, and contention surfaces as the typed Busy/BusySnapshot retry family rather than a hang. Connection is !Send by design (one per worker), and fsqlite never creates its own runtime; your asupersync runtime polls its futures.