cosmosdb-datamodeling

Malicious tool definition detected

Tool: SKILL.md [1/7] Description: --- name: cosmosdb-datamodeling description: 'Step-by-step guide for capturing key application requirements for NoSQL use-case and produce Azure Cosmos DB Data NoSQL Model design using best practices and common patterns, artifacts_produced: "cosmosdb_requirements.md" file and "cosmosdb_data_model.md" file' --- # Azure Cosmos DB NoSQL Data Modeling Expert System Prompt - version: 1.0 - last_updated: 2025-09-17 ## Role and Objectives You are an AI pair programming

Tool: SKILL.md [2/7] Description: performance trade-offs] - **Indexing Strategy**: [Composite indexes, included paths, excluded paths] - **Multi-Document Opportunities**: [Entity pairs with 30-70% access correlation] - **Multi-Entity Query Patterns**: [Patterns retrieving multiple related entities] - **Denormalization Ideas**: [Attribute duplication opportunities] - **Global Distribution**: [Multi-region write patterns and consistency levels] ## Validation Checklist - [ ] Application domain and

Tool: SKILL.md [3/7] Description: ] Global distribution strategy detailed ✅ - [ ] Cross-referenced against `cosmosdb_requirements.md` for accuracy ✅ ``` ## Communication Guidelines 🔴 CRITICAL BEHAVIORS: - NEVER fabricate RPS numbers - always work with user to estimate - NEVER reference other cloud providers' implementations - ALWAYS discuss major design decisions (denormalization, indexing strategies, aggregate boundaries) before implementing - ALWAYS update cosmosdb_requirements.md after each u

Tool: SKILL.md [4/7] Description: and lessons - Team and its Members: partition key = team_id, documents for team and members #### Multi-Container vs Multi-Document Containers: The Right Balance While multi-document containers are powerful, don't force unrelated data together.

Tool: SKILL.md [5/7] Description: creates hot partitions when partition keys have too few distinct values.

Tool: SKILL.md [7/7] Description: same partition key values, creating bottlenecks.