From aj-geddes-useful-ai-prompts-4
Design NoSQL schemas for MongoDB and DynamoDB. Covers document modeling, indexing, denormalization, and query optimization.
How this skill is triggered — by the user, by Claude, or both
Slash command
/aj-geddes-useful-ai-prompts-4:nosql-database-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- [Overview](#overview)
Design scalable NoSQL schemas for MongoDB (document) and DynamoDB (key-value). Covers data modeling patterns, denormalization strategies, and query optimization for NoSQL systems.
Minimal working example:
// Single document with embedded arrays
db.createCollection("users");
db.users.insertOne({
_id: ObjectId("..."),
email: "[email protected]",
name: "John Doe",
createdAt: new Date(),
// Embedded address
address: {
street: "123 Main St",
city: "New York",
state: "NY",
zipCode: "10001",
},
// Embedded array of items
orders: [
{
orderId: ObjectId("..."),
date: new Date(),
total: 149.99,
},
{
// ... (see reference guides for full implementation)
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Document Structure Design | Document Structure Design |
| Indexing in MongoDB | Indexing in MongoDB |
| Schema Validation | Schema Validation |
| Table Structure | Table Structure |
| Global Secondary Indexes (GSI) | Global Secondary Indexes (GSI) |
| DynamoDB Item Operations | DynamoDB Item Operations |
npx claudepluginhub joshuarweaver/cascade-code-languages-misc-1 --plugin aj-geddes-useful-ai-prompts-4Designs NoSQL data models for MongoDB, DynamoDB, Redis, and Cassandra based on access patterns and query requirements. Guides embedding vs. referencing decisions, single-table DynamoDB design, and denormalization trade-offs. Requires mongosh, aws dynamodb CLI, redis-cli, or cqlsh.
Provides MongoDB schema design patterns and anti-patterns for data modeling, schema reviews, SQL migrations, and performance troubleshooting from schema issues.
Guides MongoDB schema design with patterns and anti-patterns. Use when designing data models, migrating from SQL, or troubleshooting performance issues caused by schema problems.