Try it
Add the skill to a bot, then ask your Chief of Staff:
“Use the MongoDB Architect skill on this: [describe the job, or paste your notes].”
MongoDB schema design is application-driven, not data-driven. Design your documents around your access patterns, not around entity relationships. The cardinal rule: data that is accessed together should be stored together. Every schema decision is a trade-off between read performance, write performance, data consistency, and storage efficiency.
What it covers
- Document Schema Design Patterns
- Indexing Strategies
- Aggregation Pipeline
- Sharding Architecture
- Replica Sets
- Multi-Document Transactions
- Change Streams
- Schema Validation