vybekiit 0.4.0 → 0.6.0

package/dist/global-skills/mongodb-query-optimizer/references/aggregation-optimization.md

@@ -0,0 +1,210 @@
+# Principles
+
+Aggregation pipelines process documents through sequential stages. Focus on:
+
+- Reducing documents early in the pipeline
+- Minimizing data moved between stages
+- Leveraging indexes where possible
+- Managing memory usage
+
+## Memory limits and disk spilling
+
+Blocking stages (such as in-memory `$sort` and `$group`) have a 100MB memory limit per stage. Default behavior when this limit is exceeded is to spill to disk automatically (`allowDiskUse` defaults to `true`).
+
+**Better solutions:**
+
+- Filter more aggressively early in pipeline
+- Add indexes to enable `$sort` to use index order
+- Use `$limit` with `$sort` to reduce the amount of data the sort must process in memory for unindexed sorts
+- Consider materialized views for repeated aggregations
+
+# Optimization Examples
+
+These examples are not exhaustive but representative of some common optimization patterns.
+
+## Unindexed $lookup vs. Indexed $lookup
+
+**Bad** — No index on the foreign collection's join field:
+
+```javascript
+db.orders.aggregate([
+  { $lookup: {
+      from: "products",
+      localField: "productId",
+      foreignField: "sku",   // no index on products.sku!
+      as: "product"
+  }}
+])
+```
+
+**Good** — Index on `foreignField` in the foreign collection:
+
+```javascript
+db.products.createIndex({ sku: 1 })
+
+db.orders.aggregate([
+  { $lookup: {
+      from: "products",
+      localField: "productId",
+      foreignField: "sku",
+      as: "product"
+  }}
+])
+```
+
+**Why:** Each `$lookup` executes a find on the `from` collection. Without an index on `foreignField`, every join does a full collection scan. This is the single most critical $lookup optimization.
+
+## Early $project Defeating Optimization vs. Late $project
+
+**Bad** — Early `$project` prevents the optimizer from pruning unused fields, forgets to exclude `_id` which is unneeded, and includes `name` which is not used:
+
+```javascript
+db.collection.aggregate([
+  { $project: { name: 1, status: 1, amount: 1 } },
+  { $match: { status: "active" } },
+  { $group: { _id: "$status", total: { $sum: "$amount" } } }
+])
+```
+
+**Good** — Let the optimizer handle field pruning; use `$project` only at the end for reshaping:
+
+```javascript
+db.collection.aggregate([
+  { $match: { status: "active" } },
+  { $group: { _id: "$status", total: { $sum: "$amount" } } },
+  { $project: { _id: 0, status: "$_id", total: 1 } }  // reshape at the end
+])
+```
+
+**Why:** MongoDB's pipeline optimizer automatically analyzes which fields are used and avoids fetching unused ones. An early `$project` defeats this optimization, and can inadvertently request the wrong fields.
+
+## $facet for Divergent Processing vs. $unionWith
+
+**Bad** — `$facet` sends all documents to every branch, even if branches need very different subsets:
+
+```javascript
+db.collection.aggregate([
+  { $facet: {
+      "top10": [{ $sort: { score: -1 } }, { $limit: 10 }],
+      "totalCount": [{ $count: "n" }]  // gets ALL docs even though it's just counting
+  }}
+])
+```
+
+**Good** — Separate pipelines via `$unionWith` let each branch optimize independently:
+
+```javascript
+db.collection.aggregate([
+  { $sort: { score: -1 } }, { $limit: 10 },
+  { $unionWith: {
+      coll: "collection",
+      pipeline: [{ $count: "n" }]
+  }}
+])
+```
+
+**Why:** `$facet` funnels every document into every branch. `$unionWith` runs independent pipelines that each benefit from their own index usage and optimization.
+
+## $sort \+ $limit as Separate Concerns vs. Top-N Sort
+
+**Bad** — Large sort, then limit (MongoDB may sort entire dataset):
+
+```javascript
+db.collection.aggregate([
+  { $group: { _id: "$category", total: { $sum: "$amount" } } },
+  { $sort: { total: -1 } },
+  // ... many stages later ...
+  { $limit: 10 }
+])
+```
+
+**Good** — Place `$limit` immediately after `$sort`:
+
+```javascript
+db.collection.aggregate([
+  { $group: { _id: "$category", total: { $sum: "$amount" } } },
+  { $sort: { total: -1 } },
+  { $limit: 10 }
+])
+```
+
+**Why:** When `$sort` is immediately followed by `$limit`, MongoDB performs a *top-N sort* — it only tracks the top N values instead of sorting the full dataset. Far less memory.
+
+## $unwind Best Practices
+
+**When $unwind is needed**, filter before unwinding so that the $match stage allows index usage:
+
+```javascript
+[
+  { $match: { "items.category": "electronics" } },  // Reduce documents first
+  { $unwind: "$items" },  // Then unwind
+  { $match: { "items.category": "electronics" } }  // Filter unwound elements
+]
+```
+
+**Never $unwind to re-group by `_id`:** If you are using `$unwind` followed by `$group` with `_id:` you can replace it with an array operator like `$filter`, `$map` or `$reduce` to match or transform array elements without unwinding.
+
+## Optimize $lookup operations
+
+`$lookup` performs collection joins and can be expensive. Strategies to improve performance:
+
+1. **Filter before lookup** to reduce left-side documents
+2. **Use indexed fields** in the lookup `localField`/`foreignField`
+3. **Add $match in the lookup pipeline** to reduce right-side documents early
+4. **Add $project last in the lookup pipeline** to keep only the fields you need
+5. **$unwind immediately after lookup** when you need `as` result flattened
+
+```javascript
+[
+  { $match: { active: true } },  // Reduce left side
+  { $lookup: {
+      from: "inventory",
+      localField: "product_id",
+      foreignField: "_id",  // _id is always indexed
+      pipeline: [
+        { $match: { inStock: true } },  // Reduce right side
+        { $project: { _id: 0, name: 1, price: 1 } }
+      ],
+      as: "product"
+  }},
+  { $unwind: "$product" }
+]
+```
+
+**Schema consideration:** Excessive `$lookup` usage may indicate over-normalization. Consider embedding frequently-joined data.
+
+## $group efficiency
+
+Group operations require accumulating result documents in memory. Keys to efficiency:
+
+1. **Include only needed fields within the $group stage** \- reference only the fields you need in accumulators
+2. **Be mindful of unbounded accumulators** \- `$push` and `$addToSet` grow as group size increases and can cause memory issues
+
+**Bad** \- do not add $project before $group to "reduce fields":
+
+```javascript
+[
+  { $match: { date: { $gte: ISODate("2024-01-01") } } },
+  { $project: { category: 1, amount: 1 } },
+  { $group: {
+      _id: "$category",
+      total: { $sum: "$amount" },
+      count: { $sum: 1 }
+  }}
+]
+```
+
+**Good** \- reference only needed fields directly in $group:
+
+```javascript
+[
+  { $match: { date: { $gte: ISODate("2024-01-01") } } },
+  { $group: {
+      _id: "$category",
+      total: { $sum: "$amount" },
+      count: { $sum: 1 }
+  }}
+]
+```
+
+**Why:** The $group stage only processes the fields referenced in its expressions. Adding a $project before it does not save memory.

package/dist/global-skills/mongodb-query-optimizer/references/antipattern-examples.md

@@ -0,0 +1,74 @@
+## $exists on Regular Index vs. Sparse Index
+
+**Bad** — `$exists: true` on a regular index still requires a document fetch:
+
+```javascript
+db.collection.createIndex({ a: 1 })
+db.collection.find({ a: { $exists: true } })
+// Cannot efficiently answer — null semantics require checking each document
+```
+
+**Good** — Use a sparse index, which only contains entries where the field exists:
+
+```javascript
+db.collection.createIndex({ a: 1 }, { sparse: true })
+db.collection.find({ a: { $exists: true } })
+// Answered directly from the index — no document fetch needed
+```
+
+**Why:** Regular indexes store `null` for both missing and existing fields that are set to `null`, so `$exists` can't be answered from the index alone. Sparse indexes only store entries for documents where the field exists.
+
+## Unanchored $regex vs. Anchored $regex
+
+**Bad** — Unanchored case insensitive regex cannot use the index efficiently:
+
+```javascript
+db.collection.find({ name: { $regex: /smith/i } })
+// Full index or collection scan — case-insensitive, not anchored
+```
+
+**Good** — Anchored, case-sensitive regex uses the index as a range query:
+
+```javascript
+db.collection.find({ name: { $regex: /^Smith/ } })
+// Efficient index range scan on the "Smith" prefix
+```
+
+**Why:** Indexes store values in sorted order. Only a left-anchored, case-sensitive `$regex` can be converted into an efficient index range scan. For case-insensitive matching, use a case-insensitive collation index instead.
+
+## $where / JavaScript vs. Native MQL Operators
+
+**Bad** — Server-side JavaScript execution:
+
+```javascript
+db.collection.find({
+  $where: "this.price * this.quantity > 1000"
+})
+```
+
+**Good** — Native aggregation expression:
+
+```javascript
+db.collection.find({
+  $expr: { $gt: [{ $multiply: ["$price", "$quantity"] }, 1000] }
+})
+```
+
+**Why:** JavaScript executed on the server is always slower than native MQL, cannot use indexes. It's also a security risk and is deprecated. Use `$expr` with aggregation operators instead.
+
+## In-Memory Sort vs. Index-Supported Sort
+
+**Bad** — Sort on an unindexed field triggers in-memory sort:
+
+```javascript
+db.orders.find({ status: "processing" }).sort({ createdAt: -1 })
+// Index: { status: 1 } — sort is done in memory
+```
+
+**Good** — Compound index supports both filter and sort:
+
+```javascript
+db.orders.createIndex({ status: 1, createdAt: -1 })
+db.orders.find({ status: "processing" }).sort({ createdAt: -1 })
+// No SORT stage in the plan — results come pre-sorted from the index
+```

package/dist/global-skills/mongodb-query-optimizer/references/core-indexing-principles.md

@@ -0,0 +1,134 @@
+# Core Index Principles
+
+### Compound Index Guidelines
+
+The first field of the index should be in the query's filter or sort condition.
+
+**Equality → Sort → Range** order is most often preferred:
+
+- **Equality** fields first (e.g. `{field: value}`, `{$in: [...]}` with \<= 200 elements, `{field: {$eq: value}}`)
+- **Sort** fields next  
+- **Range** fields last (e.g. `$gt`, `$lt`, `$gte`, `$lte`, `{$in: [...]}` with \> 200 elements in the array, `$ne`, anchored case-sensitive `$regex`)
+
+If equality is not very selective and range is, then ERS may perform better than ESR.
+
+### Sort direction
+
+Index `{a:1, b:1}` supports `sort({a:1, b:1})` and reverse `sort({a:-1, b:-1})`, but NOT mixed directions like `sort({a:1, b:-1})`. For mixed sorts, create index matching exact pattern.
+
+### Collation Match
+
+**Before** — Query collation differs from index collation, so the index cannot be used:
+
+```javascript
+db.users.createIndex({ name: 1 })
+db.users.find({ name: "José" }).collation({ locale: "es", strength: 2 })
+// Index cannot be used for query
+```
+
+**After** — Create the index with the same collation the query uses:
+
+```javascript
+db.users.createIndex({ name: 1 }, { collation: { locale: "es", strength: 2 } })
+db.users.find({ name: "José" }).collation({ locale: "es", strength: 2 })
+// Index can be used for query
+```
+
+**Why:** Collation must match between index and query.
+
+# Covered Queries
+
+A covered query retrieves data directly from the index, never accessing the actual documents. This is extremely fast and preferable when possible.
+
+## Requirements
+
+1. **All query fields** are in the index  
+2. **All returned fields** are in the index (includes sort fields)  
+3. **Inclusion projection required** \- you must use an inclusion projection (e.g., `{ field: 1 }`) that requests only indexed fields, plus `_id: 0` if `_id` is not in the index. Exclusion projections cannot produce covered queries.  
+4. **No `$exists` or null equality checks** \- queries using `$exists` or querying for null/missing values cannot usually be covered by an index
+5. **Multikey index constraints** \- multikey indexes can cover queries under certain conditions, such as when the array field itself is not included in the projection and operators like `$elemMatch` are not used. If the array field must be projected, covering is not possible.
+
+## Building a covered query
+
+**Step 1:** Identify your query pattern
+
+```javascript
+db.products.find(
+  { category: "electronics", inStock: true },
+  { category: 1, inStock: 1, price: 1, _id: 0 }
+).sort({ price: 1 })
+```
+
+**Step 2:** Create index with all accessed fields
+
+Following ESR (Equality-Sort-Range):
+
+```javascript
+db.products.createIndex({
+  category: 1,    // Equality
+  inStock: 1,     // Equality
+  price: 1        // Sort
+})
+```
+
+**Step 3:** Project only indexed fields
+
+- Include indexed fields in projection  
+- **Exclude \_id** unless \_id is in the index (use `_id: 0`)  
+- Don't request fields not in the index
+
+## Common mistakes
+
+### Forgetting to explicitly exclude  \_id
+
+```javascript
+// NOT COVERED - _id not in index but included in result
+db.products.find(
+  { category: "electronics" },
+  { category: 1, price: 1 }  // _id included by default!
+)
+```
+
+**Fix:** Explicitly exclude \_id
+
+```javascript
+db.products.find(
+  { category: "electronics" },
+  { category: 1, price: 1, _id: 0 }  // Now covered
+)
+```
+
+### Requesting non-indexed fields
+
+```javascript
+// NOT COVERED - description not in index
+db.products.find(
+  { category: "electronics" },
+  { category: 1, price: 1, description: 1, _id: 0 }
+)
+```
+
+**Fix:** Only project indexed fields, or add description to index
+
+### Array fields (multikey indexes)
+
+```javascript
+// NOT COVERED - tags is an array field and is included in projection
+db.products.createIndex({ tags: 1, price: 1 })
+db.products.find(
+  { tags: "sale" },
+  { tags: 1, price: 1, _id: 0 }
+)
+```
+
+**Fix:** If the array field is not needed in the result, remove it from the projection:
+
+```javascript
+// COVERED - array field (tags) used in query but not projected
+db.products.find(
+  { tags: "sale" },
+  { price: 1, _id: 0 }
+)
+```
+
+Multikey indexes can cover queries when the array field itself is not projected and operators like `$elemMatch` are not used. If you must return the array field, the query cannot be covered.

package/dist/global-skills/mongodb-query-optimizer/references/update-query-examples.md

@@ -0,0 +1,39 @@
+# Update Query Examples
+
+## replaceOne vs. updateOne with $replaceWith
+
+**Bad** — Full document replacement generates a large oplog entry:
+
+```javascript
+db.coll.replaceOne({ _id: X }, entireNewDocument)
+```
+
+**Good** — Use aggregation-based update to generate smaller oplog deltas:
+
+```javascript
+db.coll.updateOne({ _id: X }, [{ $replaceWith: { $literal: entireNewDocument } }])
+```
+
+**Why:** `replaceOne` writes the full document to the oplog. The aggregation update syntax lets MongoDB compute deltas, resulting in smaller oplog entries when only a few fields are changed.
+
+## findOneAndUpdate Misuse vs. updateOne
+
+**Bad** — Using `findOneAndUpdate` when you don't need the document returned:
+
+```javascript
+db.coll.findOneAndUpdate(
+  { _id: X },
+  { $set: { status: "processed" } }
+)
+```
+
+**Good** — Use `updateOne` when you don't need the result document:
+
+```javascript
+db.coll.updateOne(
+  { _id: X },
+  { $set: { status: "processed" } }
+)
+```
+
+**Why:** `findOneAndUpdate` writes a copy of the pre-change document to a side collection for retryable writes. This overhead is unnecessary if you don't need the returned document.

package/dist/global-skills/mongodb-schema-design/SKILL.md

@@ -0,0 +1,181 @@
+---
+name: mongodb-schema-design
+description: MongoDB schema design patterns and anti-patterns. Use when designing data models, reviewing schemas, migrating from SQL, or troubleshooting performance issues caused by schema problems. Triggers on "design schema", "embed vs reference", "MongoDB data model", "schema review", "unbounded arrays", "one-to-many", "tree structure", "16MB limit", "schema validation", "JSON Schema", "time series", "schema migration", "polymorphic", "TTL", "data lifecycle", "archive", "index explosion", "unnecessary indexes", "approximation pattern", "document versioning".
+license: Apache-2.0
+metadata:
+  version: "1.0.0"
+---
+
+# MongoDB Schema Design
+
+Data modeling patterns and anti-patterns for MongoDB, maintained by MongoDB. Bad schema is the root cause of most MongoDB performance and cost issues—queries and indexes cannot fix a fundamentally wrong model.
+
+## When to Apply
+
+Reference these guidelines when:
+- Designing a new MongoDB schema from scratch
+- Migrating from SQL/relational databases to MongoDB
+- Reviewing existing data models for performance issues
+- Troubleshooting slow queries or growing document sizes
+- Deciding between embedding and referencing
+- Modeling relationships (one-to-one, one-to-many, many-to-many)
+- Implementing tree/hierarchical structures
+- Seeing Atlas Schema Suggestions or Performance Advisor warnings
+- Hitting the 16MB document limit
+- Adding schema validation to existing collections
+
+## Quick Reference
+
+### 1. Schema Anti-Patterns - 3 rules
+
+- [antipattern-unnecessary-collections](references/antipattern-unnecessary-collections.md) - Splitting homogeneous data into multiple collections is often an anti-pattern; consult this reference to validate whether this is the case.
+- [antipattern-excessive-lookups](references/antipattern-excessive-lookups.md) - When encountering overly normalized collections that reference each other or frequent and possibly slow $lookup operations, consult this reference to validate whether this is problematic and how to fix it.
+- [antipattern-unnecessary-indexes](references/antipattern-unnecessary-indexes.md) - Consult this reference when indexes overlap or are not used by queries, to identify and remove unnecessary indexes that add overhead without benefit.
+
+### 2. Schema Fundamentals - 4 rules
+
+- [fundamental-embed-vs-reference](references/fundamental-embed-vs-reference.md) - Consult this reference for approaches to modeling different types of relationships (1:1, 1:few, 1:many, many:many, tree/hierarchical data) and how to decide between embedding and referencing based on access patterns.
+- [fundamental-document-model](references/fundamental-document-model.md) - Fundamentals of the document model. Consult this reference when migrating from SQL or other normalized data to a document database like MongoDB.
+- [fundamental-schema-validation](references/fundamental-schema-validation.md) - Consult this reference when creating new collections, or adding validation to existing collections, for example in response to finding inconsistent document structures or data quality issues.
+- [fundamental-document-size](references/fundamental-document-size.md) - Consult this reference when documents hit the hard 16MB limit, or when accesses are slower than expected as a result of large documents.
+
+### 3. Design Patterns - 11 rules
+
+- [pattern-approximation](references/pattern-approximation.md) - Use approximate values for high-frequency counters
+- [pattern-archive](references/pattern-archive.md) - Move historical data to separate/cold storage for performance
+- [pattern-attribute](references/pattern-attribute.md) - Collapse many optional fields into key-value attributes
+- [pattern-bucket](references/pattern-bucket.md) - Group time-series or IoT data into buckets
+- [pattern-computed](references/pattern-computed.md) - Pre-calculate expensive aggregations
+- [pattern-document-versioning](references/pattern-document-versioning.md) - Track document changes to enable historical queries and audit trails
+- [pattern-extended-reference](references/pattern-extended-reference.md) - Cache frequently-accessed data from related entities
+- [pattern-outlier](references/pattern-outlier.md) - Handle collections in which a small subset of documents are much larger than the rest, to prevent outliers from dominating memory and index costs
+- [pattern-polymorphic](references/pattern-polymorphic.md) - Store different types of entities in the same collection, often when they are different types of the same base entity (e.g. different types of users or different types of products)
+- [pattern-schema-versioning](references/pattern-schema-versioning.md) - Schema evolution, preventing drift, and safe online migrations. Consult when encountering inconsistent document structures, or when planning a schema change that cannot be applied atomically.
+- [pattern-time-series-collections](references/pattern-time-series-collections.md) - Use native time series collections for high-frequency time series data
+
+### Access Pattern Analysis
+
+Do not immediately recommend a pattern or schema change without understanding the broader context. Together with the user, analyze access patterns to identify pain points and opportunities for optimization.
+
+#### Workflow
+
+**Step 1: Assess the environment**
+Ask the user:
+  - Is this a new design or is there a production database with existing access patterns to analyze?
+  - If there is production data, is it on Atlas? If yes, what tier? (M0/M2/M5 vs M10+)
+
+**Step 2: Determine workload type**
+Is the workload read-heavy, write-heavy, or balanced? This will influence which diagnostic sources are most relevant.
+Ask the user:
+- What's the primary workload for these collections — read-heavy (analytics, reports, searches), write-heavy (logging, IoT ingestion, frequent updates), or balanced?
+
+Verify with `db.serverStatus().opcounters`.
+
+**Step 3: Work with the user to choose the best source(s)**
+  Recommend the best source(s) for their situation, explaining the tradeoffs. For schema design decisions, we often need to combine multiple sources for a complete picture.
+
+**Step 4: Proceed with analysis**
+  Only after source selection, fetch data or guide the user through analysis.
+
+#### Sources
+
+- [Query statistics](references/source-query-stats.md) - Returns runtime statistics for recorded queries showing query shapes and frequency. **Limitation**: Currently only captures read operations (pair with other sources for write patterns). Requires Atlas M10+ tier.
+- [Atlas Slow Query Logs](references/source-slow-query-logs.md) - Review slow queries (actual queries, not shapes) to identify performance bottlenecks. Captures all reads and writes. Requires Atlas M10+ tier.
+- Codebase - Examine actual queries in application code to understand access patterns, especially for new applications or with changing workloads. Can be used in conjunction with query stats for a more complete picture.
+- Natural language input - Ask the user to describe their typical queries and access patterns in natural language. Can be used as the only source or to supplement and validate other sources - the user might have contextual knowledge that is not reflected in the data or codebase.
+
+**Combining Query Stats and Slow Query Logs:**
+
+Use both together for comprehensive analysis:
+1. Query Stats → identify frequent access patterns (which queries run most often)
+2. Slow Query Logs → identify performance bottlenecks (which queries are slow)
+3. Focus schema optimization on queries that are both frequent AND slow (highest impact)
+
+## Key Principle
+
+> **"Data that is accessed together should be stored together."**
+
+This is MongoDB's core philosophy. Embedding related data eliminates joins, reduces round trips, and enables atomic updates. Reference only when you must.
+
+A core way to implement this philosophy is the fact that MongoDB exposes **flexible schemas**. This means you can have different fields in different documents, and even different structures. This allows you to model data in the way that best fits your access patterns, without being constrained by a rigid schema. For example, if different documents have different sets of fields, that is perfectly fine as long as it serves your application's needs. You can also use schema validation to enforce certain rules while still allowing for flexibility.
+
+Another implication of the key principle is that information about the expected read and write workload becomes very relevant to schema design. If pieces of information from different entities are often queried or updated together, that means that prioritizing co-location of that data in the same document can lead to significant performance benefits. On the other hand, if certain pieces of information are rarely accessed together, it may make sense to store them separately to avoid loading more data than necessary.
+
+#### Schema Fundamentals Summary
+
+- **Embed vs Reference**: Choose embedding or referencing based on access patterns: embed when data is always accessed together (1:1, 1:few, bounded arrays, atomic updates needed); reference when data is accessed independently, relationships are many-to-many, or arrays can grow without bound.
+- **Data accessed together stored together**: MongoDB's core principle: design schemas around queries, not entities. Embed related data to eliminate cross-collection joins and reduce round trips. Identify your API endpoints/pages, list the data each returns, then shape documents to match those queries.
+- **Embrace the document model**: Don't recreate SQL tables 1:1 as MongoDB collections. Instead, denormalize joined tables into rich documents for single-query reads and atomic updates. When migrating from SQL, identify tables that are always joined together and merge them into single documents.
+- **Schema validation**: Use MongoDB's built-in `$jsonSchema` validator to catch invalid data at the database level (type checks, required fields, enum constraints, array size limits). Start with `validationLevel: "moderate"` and `validationAction: "warn"` on existing collections, then tighten to `strict`/`error`.
+- **16MB document limit**: MongoDB documents cannot exceed 16MB—this is a hard limit, not a guideline. Common causes: unbounded arrays, large embedded binaries, deeply nested objects. Mitigate by moving unbounded data to separate collections and monitoring document sizes with `$bsonSize`.
+
+## Embed/Reference Decision Framework
+
+| Relationship | Cardinality | Access Pattern | Recommendation |
+|-------------|-------------|----------------|----------------|
+| One-to-One | 1:1 | Always together | Embed |
+| One-to-Few | 1:N (N < 100) | Usually together | Embed array |
+| One-to-Many | 1:N (N > 100) | Often separate | Reference |
+| Many-to-Many | M:N | Varies | Two-way reference |
+
+This is a **rough** guideline, and whether to embed or reference depends on your specific access patterns, data size, and read/write frequencies. Always verify with your actual workload.
+
+## How to Use
+
+Each reference file listed above contains detailed explanations and code examples. Use the descriptions in the Quick Reference to identify which files are relevant to your current task.
+
+Each reference file contains:
+- Brief explanation of why it matters
+- Incorrect code example with explanation
+- Correct code example with explanation
+- "When NOT to use" exceptions
+- Performance impact and metrics
+- Verification diagnostics
+
+---
+
+## How These Rules Work
+
+### MongoDB MCP Integration
+
+For automatic verification, connect the [MongoDB MCP Server](https://github.com/mongodb-js/mongodb-mcp-server).
+
+If the MCP server is running and connected, I can automatically run verification commands to check your actual schema, document sizes, array lengths, index usage, slow query logs, and more. This allows me to provide tailored recommendations based on your real data, not just code patterns.
+
+**⚠️ Security**: Use `--readOnly` for safety. Remove only if you need write operations.
+
+When connected, I can automatically:
+- Infer schema via `mcp__mongodb__collection-schema`
+- Measure document/array sizes via `mcp__mongodb__aggregate`
+- Check collection statistics via `mcp__mongodb__db-stats`
+
+### ⚠️ Action Policy
+
+**I will NEVER execute write operations without your explicit approval.**
+
+Before any write or destructive operation via MCP, I will: (1) summarize the exact operation (collection, index/validator, estimated number of docs affected), and (2) ask for explicit confirmation (yes/no). I will not proceed on partial or ambiguous approvals.
+
+| Operation Type | MCP Tools | Action |
+|---------------|-----------|--------|
+| **Read (Safe)** | `find`, `aggregate`, `collection-schema`, `db-stats`, `count` | I may run automatically to verify |
+| **Write (Requires Approval)** | `update-many`, `insert-many`, `create-collection` | I will show the command and wait for your "yes" |
+| **Destructive (Requires Approval)** | `delete-many`, `drop-collection`, `drop-database` | I will warn you and require explicit confirmation |
+
+When I recommend schema changes or data modifications:
+1. I'll explain **what** I want to do and **why**
+2. I'll show you the **exact command**
+3. I'll **wait for your approval** before executing
+4. If you say "go ahead" or "yes", only then will I run it
+
+**Your database, your decision.** I'm here to advise, not to act unilaterally.
+
+### Working Together
+
+If you're not sure about a recommendation:
+1. Run the verification commands I provide
+2. Share the output with me
+3. I'll adjust my recommendation based on your actual data
+
+We're a team—let's get this right together.
+
+