Data Partitioning
Design partitioning and sharding strategies for data at scale. Use when single database hits throughput or storage limits.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill data-partitioninggit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/architect/system-design/skills/data-partitioning ~/.claude/skills/data-partitioningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Partitioning Design partitioning strategies (sharding, bucketing) to distribute data across multiple databases or nodes, enabling horizontal scaling. ## Context You are designing data partitioning for large-scale systems. The user faces single database bottlenecks (throughput or storage). Read their data volume, access patterns, and consistency requirements. ## Domain Context Based on designing data-intensive applications and partition strategies from Dynamo/Cassandra: - **Range Partitioning**: Partition by key range (UserID 1-1000 on DB1, 1001-2000 on DB2). Simple but uneven load. - **Hash Partitioning**: Partition by hash(key). Even distribution, but range queries require scatter-gather. - **Directory-Based**: Maintain mapping of key → partition. Flexible, adds lookup cost. - **Rebalancing**: When adding nodes, some partitions migrate. Strategy affects availability. - **Hot Partitions**: Some keys receive disproportionate traffic. Mitigate by splitting hot partition or using caching. ## Instructions 1. **Choose Partition Key**: What key distributes evenly? UserID is obvious for user-centric apps. For IoT, might be (SensorType, RegionID). Avoid keys that hotspot (Country or Status). 2. **Select Partitioning Scheme**: - **Range**: If range queries common (time-series data). Risk: uneven distribution. - **Hash**: If uniform access. Range queries require scatter-gather. - **Directory**: If rebalancing needed frequently. Cost: lookup on every request.
Details
- Skill name
data-partitioning- Repository
- sethdford/claude-skills
- Path
architect/system-design/skills/data-partitioning/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Data Partitioning skill do?
Design partitioning and sharding strategies for data at scale. Use when single database hits throughput or storage limits.
How do I install the Data Partitioning 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 Data Partitioning popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/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.
Schema Design
48sethdford/claude-skills
Database schema design with normalization, relationships, constraints, and data integrity.
Caching Strategy
48sethdford/claude-skills
Design multi-layer caching strategies (client, edge, service, database) for performance. Use when optimizing latency or reducing database load.
Schema Evolution
48sethdford/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.
Browse the most popular Claude skills, all databases skills, or write your own with the skills generator.