AGENT SKILL

managing-database-sharding

This skill assists with managing database sharding strategies. It is activated when the user needs to implement horizontal database sharding to scale beyond single-server limitations. The skill supports designing sharding strategies, distributing data across multiple database instances, and implementing consistent hashing, automatic rebalancing, and cross-shard query coordination. Use this skill when the user mentions "database sharding", "sharding implementation", "scale database", or "horizontal partitioning". The plugin helps design and implement sharding for high-scale applications.

License 许可
MIT
最近更新
2026-11-13
Stars
★ 2
Forks
0

01 前言 Front Matter

name
managing-database-sharding
description
This skill assists with managing database sharding strategies. It is activated when the user needs to implement horizontal database sharding to scale beyond single-server limitations. The skill supports designing sharding strategies, distributing data across multiple database instances, and implementing consistent hashing, automatic rebalancing, and cross-shard query coordination. Use this skill when the user mentions "database sharding", "sharding implementation", "scale database", or "horizontal partitioning". The plugin helps design and implement sharding for high-scale applications.

02 资源文件 3

03 SKILL.md 正文

Overview

This skill empowers Claude to design and implement horizontal database sharding strategies. It guides the user through the process of distributing data across multiple database instances, ensuring scalability and performance for applications handling large datasets and high query loads.

How It Works

  1. Strategy Design: Analyzes the application's data model and access patterns to determine the optimal sharding key and sharding strategy (e.g., range-based, hash-based).
  2. Implementation Planning: Generates a detailed plan for implementing the chosen sharding strategy, including database schema modifications, data migration procedures, and application code changes.
  3. Cross-Shard Query Coordination: Provides guidance on implementing cross-shard query coordination mechanisms to ensure data consistency and accuracy across multiple shards.

When to Use This Skill

This skill activates when you need to:

  • Scale a database beyond the capacity of a single server.
  • Distribute write load across multiple database servers.
  • Improve database performance by reducing contention.

Examples

Example 1: Scaling an E-commerce Product Catalog

User request: "Implement database sharding for my e-commerce product catalog to handle increased traffic and product listings."

The skill will:

  1. Analyze the product catalog's data model and access patterns.
  2. Recommend a hash-based sharding strategy based on product ID.
  3. Generate a plan for migrating the product catalog data to the sharded database.

Example 2: Sharding a Social Media Activity Feed

User request: "Design a sharding strategy for a social media activity feed to handle millions of users and billions of activities."

The skill will:

  1. Evaluate the activity feed's data model and query patterns.
  2. Suggest a time-based sharding strategy combined with user ID sharding.
  3. Outline the steps for implementing cross-shard queries to retrieve activities across multiple shards.

Best Practices

  • Data Modeling: Carefully consider the sharding key and its impact on query performance.
  • Data Migration: Plan the data migration process thoroughly to minimize downtime and ensure data integrity.
  • Monitoring: Implement robust monitoring to track shard performance and identify potential issues.

Integration

This skill can be integrated with other database management tools and plugins to automate tasks such as schema creation, data migration, and monitoring. It complements plugins focused on database deployment and performance tuning.

04 同仓库更多 Skills

sandraschi
sandraschi/documentation-mcp

Docs Research

Use MCP Central Docs server to search, ask, and retrieve documentation (FastMCP, standards, packaging).

资料检索与研究Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

wrappee-drift

Read-only, single-repo audit of a repo's tool coverage against the software it wraps (its current real API/docs, not training-data memory) and against comparable/competing wrappers. Trigger when the user says "wrappee drift" followed by a repo name, "capability audit" followed by a repo name, or asks whether a repo is missing features the wrapped software or a competitor now has. Always scoped to one named repo per invocation -- never trigger this fleet-wide or unprompted; that is explicitly against the SOP. Do NOT trigger for internal fleet-standard compliance (that is drift-scan) or strategic worth/archive decisions (that is quality-check) -- this is specifically about the gap between the repo's tool list and the wrapped software's/competitors' actual current capabilities.

★ 2
sandraschi
sandraschi/documentation-mcp

modules

暂无简介

运维与部署Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

mcp-standards

Use when developing MCP servers to access comprehensive standards for scaffolding, packaging, sampling, documentation, testing, error handling, monitoring, and CI/CD workflows.

测试与质量Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

webapp-cua-test

Run the pre-Tauri CUA click-through test (real browser, dev stack, OCR "Connected" wait, sidebar nav walk) for a fleet MCP server repo under D:\Dev\repos. Trigger when the user says "cua webapp test" or "webapp clickthrough" followed by a repo name, asks for an e2e click-through of a webapp, or asks whether a webapp boots and connects in a real browser. Not for the installed NSIS app (that is the nsis-build skill / cua-nsis-test) and not for DOM assertions (Playwright), and not for hunting fake data or dead buttons (fakefind).

测试与质量Skill与智能体开发
★ 2
sandraschi
sandraschi/documentation-mcp

ship

Final release gate for a fleet MCP server repo under D:\Dev\repos -- run all quality gates, build the release artifact, verify it, commit, push, and cut a GitHub release. Trigger this whenever the user says "ship it", "ship" followed by a repo name, "release" followed by a repo name, or asks to finalize and publish work that's already been done in a repo. This is the terminal step after assfix/nsis-build, not a substitute for them -- if the repo hasn't been assessed recently, say so before shipping rather than shipping blind.

Skill与智能体开发
★ 2