agentsclimarketplace

Riligar dev database

Skill riligar/agents-kit/.agent/skills/riligar-dev-database

RiLiGar Agents Kit - Curated collection of AI Agent templates, skills, and rules designed to standardize and supercharge your AI-driven development workflows.

Install
npx -y skills add riligar/agents-kit --skill riligar-dev-database

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

database patterns for RiLiGar using Drizzle ORM + bun:sqlite. Use when setting up database connections, defining schemas, creating migrations, or writing queries. Covers SQLite on Fly.io volumes with the drizzle-kit workflow.

SKILL.md

2.0 KB, as published. Nobody here has run it

database — Drizzle + bun:sqlite

SQLite nativo no Bun. Zero drivers externos. Base de dados no volume do Fly.io (/app/data).

Referências

ArquivoQuando usar
connection.mdSetup inicial: instalação, db.js, drizzle.config
schema.mdDefinir tabelas, tipos de colunas, relações
migrations.mdCriar e executar migrations com drizzle-kit
queries.mdSelect, insert, update, delete, queries com relações

Quick Start

// database/db.js
import { drizzle } from 'drizzle-orm/bun-sqlite'
import database from 'bun:sqlite'

const sqlite = new database(process.env.DB_PATH ?? './database/database.db')
const db = drizzle({ client: sqlite })

export { db }

Regras

  • Caminho do banco: /app/data/database.db em produção (volume Fly.io). ./database/database.db em desenvolvimento.
  • Migrations sempre: Use drizzle-kit generate + drizzle-kit migrate. Nunca edite migrations à mão.
  • Schema único: Todas as tabelas em database/schema.js.
  • Migrations no startup: Use migrate() no index.js antes de .listen().

Related Skills

NeedSkill
Backend (Elysia)@[.agent/skills/riligar-dev-manager]
Payments (Stripe)@[.agent/skills/riligar-infra-stripe]
Infrastructure@[.agent/skills/riligar-infra-fly]

Gives 0 of the 12 instructions most databases sql skills give

Counted across 589 of the 662 authors here whose files we hold, read 2026-08-06

  • use parameterized queriesin 36 of 589, across 32 files
  • use timestamptz for timestampsin 30 of 589, across 12 files
  • create indexes concurrentlyin 29 of 589, across 23 files
  • index foreign keysin 28 of 589, across 17 files
  • use numeric type for moneyin 25 of 589, across 8 files
  • select only required columnsin 24 of 589, across 19 files
  • use cursor pagination instead of OFFSETin 23 of 589, across 15 files
  • add indexes manually on foreign key columnsin 22 of 589, across 11 files
  • read individual rule files for detailed explanationsin 18 of 589, across 4 files
  • configure connection poolingin 18 of 589, across 16 files
  • put equality columns before range columns in indexesin 17 of 589, across 9 files
  • normalize to third normal formin 17 of 589, across 8 files

Said here and by no other author read

  • Use bun sqlite without external drivers
  • Place all tables in a single schema file
  • Use the production database path on volumes
  • Use the development database path locally

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.