Storage Selection

Choose the right database technology for specific workloads. Evaluate relational, NoSQL, data warehouses, and search engines. Use when selecting storage systems for new features or optimizing existing ones.

48 stars 10 forksDatabases Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill storage-selection
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/data-architecture/skills/storage-selection ~/.claude/skills/storage-selection

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Storage Selection

Choose optimal database technology by analyzing workload characteristics, consistency requirements, and operational complexity.

## Context

You are helping select storage systems for specific data requirements. Analyze access patterns, consistency needs, data volume, and operational constraints. Read any existing schemas or architectural context provided.

## Domain Context

Based on Martin Kleppmann's _Designing Data-Intensive Applications_:

- **Relational Databases**: ACID transactions, schema enforcement, complex queries; limited horizontal scaling
- **Document Databases**: Flexible schema, natural object mapping, good for hierarchical data; transactions often single-document only
- **Key-Value Stores**: Fast reads/writes, simple data model; limited query flexibility
- **Column Family Stores**: Optimized for analytics and time-series; sparse data; distributed
- **Search Engines**: Full-text search, fuzzy matching, aggregations; not transaction-oriented
- **Data Warehouses**: Analytical queries, columnar storage, massive scale; designed for batch not realtime

## Instructions

1. **Catalog Data Requirements**: List primary access patterns (read-heavy? write-heavy? both?), data volume growth rate, consistency needs (strong/eventual?), query types (transactional vs analytical), and operational SLAs.
Read the full skill on GitHub

Details

Skill name
storage-selection
Path
architect/data-architecture/skills/storage-selection/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Storage Selection skill do?

Choose the right database technology for specific workloads. Evaluate relational, NoSQL, data warehouses, and search engines. Use when selecting storage systems for new features or optimizing existing ones.

How do I install the Storage Selection skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Storage Selection popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

A B Test Design

48

sethdford/claude-skills

Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.

Testing & QA10

A B Test Design Pm

48

sethdford/claude-skills

Analytics and experimentation skill for product managers.

Testing & QA10

Abuse Case Design

48

sethdford/claude-skills

Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.

Security10

Architecture Database Scaling

45

j4flmao/agent-skills

Use when the user asks how to scale the database, read replicas, table partitioning, sharding, choosing a shard key, Citus, Vitess, resharding or hot partitions. Produces a scaling ladder plan, shard key and routing design. Not for PostgreSQL engine internals (use architecture-postgresql-internals) or NoSQL selection (use data-nosql-database).

Databases

Schema Evolution

48

sethdford/claude-skills

Manage database schema changes while maintaining backwards compatibility. Handle migrations, versioning, and zero-downtime deployments. Use when evolving data models in production systems.

Databases10

Backend Database Patterns

45

j4flmao/agent-skills

Use when the user asks about database schema design, slow queries, indexes, EXPLAIN ANALYZE, N+1 problems, transactions, keyset pagination, connection pooling or repository pattern. Produces schema, index and query fixes. Not for engine internals (use architecture-postgresql-internals) or migrations tooling (use database-migration).

Databases

Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.