← ClaudeAtlas

db-defaultslisted

Use when adding local data persistence to a Python project — caching, relational storage (simple, complex/OLTP, or analytical/OLAP), document storage, full-text search, vector/embedding search, background job queues, cron/scheduled tasks, pub/sub/event streaming, graph data, blob storage, or time-series data — and no explicit "evaluate the best DB for this" request was made. Gives the default technology per category, chosen for permissive licensing, pytest-local testability with no docker/cloud, and low-boilerplate LLM-agent-friendly APIs, so picks stay consistent across projects instead of drifting session to session.
TheodoreAD/agent-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill TheodoreAD/agent-skills
# Default storage tech per use case Personal, Python-first, local-first projects. Applies when starting a storage/caching need without an explicit request to analyze alternatives — pick from this table, don't re-litigate from scratch each session. Deviating is fine when a category genuinely doesn't fit or scale requirements outgrow the default (see each category's "Escalate to" line) — the point is to stop a fresh session/model from silently picking something different for no reason, not to forbid judgment calls. **Selection criteria for every entry below**: MIT/Apache-2.0/BSD-style permissive license only; popular and actively maintained (verified via real GitHub/PyPI activity, not vibes); testable fully inside a plain `pytest` run — in-memory or `tmp_path`-scoped, no Docker/cloud account/CI services; low-boilerplate API a coding agent can use correctly without much ceremony or indirection. Picks favor the best-fit tool per concern over minimizing the number of technologies in a project — don't force a consolidation the categories below don't call for. **Cash in the testability criterion: don't mock these.** The whole point of picking a store the suite can start and stop is that tests run the real one, so a double here throws away what the choice bought. `python-conventions`, "Don't double anything the suite can run for real", states the rule and the boundary. **Security is deliberately not a selection factor.** Every default here is chosen for local, personal-scale use