Azure Cosmos DB Application Developer
Purpose
Guide Azure Cosmos DB application-development decisions without pretending relational habits, scan-heavy queries, or cross-partition assumptions will scale safely.
When to use
Use this skill when the user asks for:
- Azure Cosmos DB data-model or document-shape design,
- partition-key choice from an application access-pattern perspective,
- point reads, query design, indexing, or SDK usage guidance,
- transactional batch, change feed, or consistency-aware client behavior questions,
- code-facing Cosmos DB design review for APIs or services.
Do not use this skill as a substitute for:
- pure control-plane platform review when the question is mainly throughput, failover, or account governance,
- generic application debugging unrelated to Cosmos DB,
- RBAC-only analysis when the main question is access governance rather than application data design,
- Mongo vCore vector-search-specific implementation unless the user explicitly asks for that API surface.
Lean operating rules
- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.
- Separate confirmed facts from inference. If state was not queried or shown, say so.
- Challenge broad scope, vague partition keys, and RU-blind advice.
- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.
References
Load these only when needed:
- MCP and evidence path - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.
- Workflow and output contract - use when executing the full review, applying stress checks, or formatting the final answer.
- Official sources - use when you need the detailed Microsoft documentation list or source notes.
Response minimum
Return, at minimum:
- the scoped target and evidence level,
- the main design or operational risks,
- the safest next actions,
- the assumptions or blockers that prevent stronger conclusions.
1---2name: techtide-azure-cosmosdb-application-developer3description: Use this skill for Azure Cosmos DB application development work, especially NoSQL data modeling, document structure, partition-aware access patterns, point reads, query design, SDK usage, transactional batch scope, consistency-aware reads, change feed integration, and Cosmos DB development guidance.4---56# Azure Cosmos DB Application Developer78## Purpose910Guide Azure Cosmos DB application-development decisions without pretending relational habits, scan-heavy queries, or cross-partition assumptions will scale safely.1112## When to use1314Use this skill when the user asks for:1516- Azure Cosmos DB data-model or document-shape design,17- partition-key choice from an application access-pattern perspective,18- point reads, query design, indexing, or SDK usage guidance,19- transactional batch, change feed, or consistency-aware client behavior questions,20- code-facing Cosmos DB design review for APIs or services.2122Do not use this skill as a substitute for:2324- pure control-plane platform review when the question is mainly throughput, failover, or account governance,25- generic application debugging unrelated to Cosmos DB,26- RBAC-only analysis when the main question is access governance rather than application data design,27- Mongo vCore vector-search-specific implementation unless the user explicitly asks for that API surface.2829## Lean operating rules3031- Prefer live Azure or Microsoft evidence first when the active client exposes it; otherwise fall back to official documentation and sanitized user evidence.32- Separate confirmed facts from inference. If state was not queried or shown, say so.33- Challenge broad scope, vague partition keys, and RU-blind advice.34- Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.3536## References3738Load these only when needed:3940- [MCP and evidence path](references/mcp-and-evidence.md) - use when choosing live Azure evidence, confirming Microsoft MCP capability, or switching to documentation mode.41- [Workflow and output contract](references/workflow-and-output.md) - use when executing the full review, applying stress checks, or formatting the final answer.42- [Official sources](references/official-sources.md) - use when you need the detailed Microsoft documentation list or source notes.4344## Response minimum4546Return, at minimum:4748- the scoped target and evidence level,49- the main design or operational risks,50- the safest next actions,51- the assumptions or blockers that prevent stronger conclusions.
TechTideOhio