sqlite-minimal-persistence
Skill111 starsChanged 5 months agoMITView on GitHub
Extend Ordinus SQLite persistence conservatively. Use when touching better-sqlite3, Drizzle schema, database bootstrap, app_meta, migrations, durable state, persistence boundaries, or proposals to add new product tables.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- lavishSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- documentation-and-adrsSkill
- electron-secure-boundarySkill
- grill-meSkill
- idea-discoverySkill
- ipc-contract-designSkill
- ordinus-ui-systemSkill
- provider-runtime-adapterSkill
- shadcn-project-workflowSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 13 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use SQLite as durable local app state without designing product tables before the workflow model is clear.
- Distinctive: line 15
Add new tables only when the product behavior needs durable state now.
- Distinctive: line 16
Avoid adding agent, task, provider, schedule, inbox, or run schemas speculatively.
- Distinctive: line 17
Keep secrets out of ordinary product tables unless a secure storage decision has been made.
- Distinctive: line 18
Treat SQLite as main-process owned.
- Very specific: line 23
Check whether existing app_meta or settings-level storage is sufficient.
- Distinctive: line 24
If a table is necessary, define the smallest schema that supports the current behavior.
- Distinctive: line 25
Add Drizzle schema and bootstrap/migration logic together.
- Distinctive: line 26
Keep data access behind main-process services.
- Very specific: line 27
Update db.getStatus only if the status surface needs to show new bootstrap information.
- Distinctive: line 28
Run typecheck, lint, build, and a runtime smoke test that opens the app.
- Distinctive: line 32
Prefer durable state for user-visible history, resumable work, and app configuration.
- Distinctive: line 33
Prefer filesystem storage for large artifacts and generated files, with database metadata later when needed.
- Distinctive: line 34
Prefer explicit timestamps and schema versioning for local migrations.
- Distinctive: line 35
Keep schema names product-oriented and stable.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SQLite Minimal Persistence
Objective
Use SQLite as durable local app state without designing product tables before the workflow model is clear.
Current Policy
- The minimum database starts with
app_meta. - Add new tables only when the product behavior needs durable state now.
- Avoid adding agent, task, provider, schedule, inbox, or run schemas speculatively.
- Keep secrets out of ordinary product tables unless a secure storage decision has been made.
- Treat SQLite as main-process owned. Renderer must access state only through typed IPC.
Workflow
- Confirm the requested behavior truly needs persistence.
- Check whether existing
app_metaor settings-level storage is sufficient. - If a table is necessary, define the smallest schema that supports the current behavior.
- Add Drizzle schema and bootstrap/migration logic together.
- Keep data access behind main-process services.
- Update
db.getStatusonly if the status surface needs to show new bootstrap information. - Run typecheck, lint, build, and a runtime smoke test that opens the app.
Design Guidance
- Prefer durable state for user-visible history, resumable work, and app configuration.
- Prefer filesystem storage for large artifacts and generated files, with database metadata later when needed.
- Prefer explicit timestamps and schema versioning for local migrations.
- Keep schema names product-oriented and stable.
Red Flags
- A table is added because a future module might need it.
- Renderer imports database code.
- Database writes are mixed into UI event handlers.
- Migration behavior is not exercised by opening the app.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

