db-selector

Recommends databases by matching project scale and requirements against a cataloged service list.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill db-selector-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-selector
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/db-selector
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill db-selector-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing a database is a high-stakes early decision, and comparing dozens of managed services, free tiers, and scaling models manually is slow and error-prone. This Skill narrows the choice to a concrete recommendation with cost projections. ## Core Features & Use Cases - Pre-cataloged service comparison: Covers relational (Supabase, PlanetScale, Neon, RDS), NoSQL (Firestore, MongoDB Atlas, DynamoDB), and special-purpose stores (Redis, Qdrant, ClickHouse, D1, Turso) with free tiers and fit notes. - Decision tree matching: Routes data characteristics (relational, flexible schema, cache, vector, analytics, edge) to the right database family. - Scale-based recommendations with cost: Maps MVP through 100K+ user tiers to specific services and monthly cost estimates. - Use Case: A founder asks "Supabase vs Firebase for my mobile app?" and receives a recommendation based on realtime/offline needs, expected scale, and budget, plus a migration path note. ## Quick Start Ask which database to use for your project, describing your data model, expected user scale, and whether you need auth, realtime sync, or edge deployment.

Frequently Asked Questions about db-selector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose a database for a new project?

Start by classifying your data: relational records like users and orders fit SQL databases, while flexible schemas fit document stores. Then match your expected scale to a tier, since Supabase Free suits MVPs while AWS RDS fits large-scale production.

Supabase vs Firebase, which should I use?

Supabase is PostgreSQL-based with integrated Auth, Storage, and Realtime, suiting relational data and SQL familiarity. Firebase Firestore is a document store with strong realtime and offline sync, making it better for mobile apps with flexible schemas.

What database should I use for an MVP with no budget?

Supabase Free offers 500MB with integrated auth and storage at zero cost, making it the default MVP pick. Neon and MongoDB Atlas also provide free tiers around 512MB for serverless Postgres or document models respectively.

Which database works for AI embeddings and RAG?

Vector databases like Qdrant or Pinecone are designed for embedding storage and similarity search in RAG pipelines. They are special-purpose stores, so pair them with a primary relational or document database for application data.

When should I not use a single database for everything?

Beyond roughly 100K users, a multi-database architecture separating concerns by workload becomes appropriate. Use Redis for caching and rate limiting, ClickHouse for analytics, and a primary SQL store for transactional data rather than forcing one engine to handle all patterns.