SQLite-compatible database written in Rust.
Bans a specific list of metaphorical words and asks for plain language.
This file points the agent at 10 other documents in the repository. Open any of them to read it here, as it was at this commit.
├── docs │ └── agent-guides │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ ├── │ └── ├── serverless │ └── conformance │ └── differential │ └── └──
File measured on main at commit 85e2346. Analysis written 2026-09-14. Star count is a snapshot from September 2026.
A command reference, a map of where to find each subsystem, and a set of core principles. Three of its sections are about how code and comments are written rather than what they do.
Quoted lines are verbatim from the file. Open one to see it where it sits.
House vocabulary
A section headed in block capitals asks for plain language over jargon, shows two renamed examples, and then lists thirteen individual metaphorical words that may not appear: load-bearing, pin, bite, sharp, arm, guard, bless, wedge, retire, retarget, answer, settle, carry, land. Inventing terms where a common domain equivalent exists is ruled out in the same paragraph.
Behavioral framing
Tests failing after a change are defined as that change's regressions, to be debugged directly. Stashing or reverting to check whether they also fail on main is described as a waste of time and prohibited by name.
A file should read from the top without jumping ahead: callers come first, callees follow, and a new helper goes below the functions that call it rather than at the end of the file. A three-line example shows the ordering.
Hard prohibitions
A two-line section states that comments are not to be added, and directs the effort into making the code expressive instead. It is the most absolute position on comments in the directory, where other files ask for comments that explain why.
Nine test directories are listed with what each is for, under a default: add coverage to the narrowest existing harness that can express the bug, and extend an existing file rather than create one. Imported upstream golden tests are marked as not to be modified for local behavior changes.
A closing section tells the agent it may be running in a GitHub Action with a turn limit, that pushing work in progress and continuing in another run is acceptable, and to avoid rabbit holes.
Turso's file tells an agent how the codebase works. It cannot tell it which bug three customers hit this week. Modem keeps that context current and attaches it to the work.