Skip to content
Skills Library
Programming · Planning

database-quick

/database-quick

Use when the product needs to store data — choosing between JSON/SQLite/Supabase/Postgres, schema design, migrations, seeding, and vector search for RAG.

Repository
cenekathon ↗
Licence
MIT
Last repository change
04.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 04.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the product needs to store data — choosing between JSON/SQLite/Supabase/Postgres, schema design, migrations, seeding, and vector search for RAG.

Original author description

Use when the product needs to store data — choosing between JSON/SQLite/Supabase/Postgres, schema design, migrations, seeding, and vector search for RAG.

How it works

  1. Choose (default: the simplest that survives the demo)
  2. Rules
  3. RAG mini-recipe
Original SKILL.md headings · 28 lines, 308 words
SKILL.md preview
---
name: database-quick
description: Use when the product needs to store data — choosing between JSON/SQLite/Supabase/Postgres, schema design, migrations, seeding, and vector search for RAG.
---

# Database, quickly

## Choose (default: the simplest that survives the demo)
| Need | Use |
|------|-----|
| Static or read-only data | JSON/CSV file in the repo, loaded at startup |
| Single-server persistence | SQLite (`better-sqlite3` / Python `sqlite3`) — caution: serverless hosts (Vercel) have no persistent disk |
| Multi-user, hosted, auth, realtime | Supabase (free tier; Postgres + Auth + Storage + pgvector) |
| Postgres only, deploying on Vercel | Neon via Vercel Marketplace (injects `DATABASE_URL`) |
| Local Postgres in dev | `docker-compose-patterns` skill → `postgres:16` |
| Embeddings / semantic search | pgvector (Supabase) or an in-memory index for < 10k items |

**Default pick: Supabase** — Postgres plus auth, storage, realtime and pgvector in one project, so a team needs no extra services. Choose Neon + Vercel only when you need just a database.

## Rules
- Write the schema as a SQL file (`db/schema.sql`) and a seed (`db/seed.sql` or a script) committed to the repo — the DB must be rebuildable in one command.
- Tables: `id` primary key, `created_at`, snake_case names, foreign keys for relations, `text`/`timestamptz`/`jsonb` types. Index columns you filter or join on.
- Parameterized queries only — never string-concatenate user input.
- With Supabase: enable Row Level Security on user-data tables, or keep the service key server-side only. Never ship the service-role key to the browser.
- Keep migrations simple: edit schema, reset and reseed during the hackathon.
- Deeper Postgres guidance: github.com/supabase/agent-skills (`supabase-postgres-best-practices`) — vet before installing.

## RAG mini-recipe
Chunk documents (~500 tokens) → embed → store (pgvector or in-memory) → on query embed the question, take top-k by cosine similarity, put chunks in the prompt, return answer + the source chunks.

**Done when:** a fresh clone + one command creates the schema and seed data, and the app reads and writes it.

Versions

The database has no other skills named database-quick.

Database snapshot: 13.11.2026 · package version ba439cfb0377 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100supabase-schema-from-requirements
    Design Supabase Postgres schema from business requirements with migrations, RLS, and types. Use when translating specifications into database tables, creating migration files, adding Row Level Security policies, or generating TypeScript types from schema. Trigger with phrases…
  • 90database-management
    When you need to modify the database schema, run migrations, or deploy Supabase changes. Use this for all SQL and Supabase-related tasks.
  • 100data
    Design or review Supabase/Postgres schema, migrations, RLS policies, SECURITY DEFINER functions, indexes, and query performance. Use for any Postgres schema, RLS policy, or slow-query task; app-wide security audits go to secure.
  • 90supabase
    Set up, extend, or audit Supabase schema, grants, RLS, migrations, typed clients, storage, and external auth. Use when integrating Supabase or repairing data access and tenant isolation.
  • 100supabase-postgres-best-practices
    Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
  • 100supabase-postgres-best-practices
    Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.