mongodb-guideline

Stars11

Forks4

UpdatedJune 28, 2026 at 15:29

MongoDB 7.0+ schema design, collection/index creation, query optimization, sharding, and async connection management. Triggers: createCollection, createIndex, aggregation, $lookup, $match, $group, TTL index, async client, embedded document, content schema, metadata, document design, chat/log storage, user settings, content/metadata operations.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

TeiNam

TeiNam/kiro-with-harness

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

5 files

SKILL.md

readonly

name	mongodb-guideline
description	MongoDB 7.0+ schema design, collection/index creation, query optimization, sharding, and async connection management. Triggers: createCollection, createIndex, aggregation, $lookup, $match, $group, TTL index, async client, embedded document, content schema, metadata, document design, chat/log storage, user settings, content/metadata operations.
origin	custom
workloads	["mongodb"]

MongoDB Database Guideline

When to Activate

Designing MongoDB collection schemas (chat, log, user settings, content, metadata)
Writing queries or aggregation pipelines
Creating indexes (single, compound, TTL, text)
Troubleshooting slow queries
Setting up async driver connection (PyMongo Async / Node.js native driver)
Implementing TTL-based data expiry

MongoDB Version and Defaults

MongoDB 7.0+
Driver: raw async driver without ODM
- Python: PyMongo Async AsyncMongoClient (async) / pymongo 4.x (sync). motor is deprecated as of 2026-05.
- Node.js: mongodb 6.x (native driver)
Default write concern: w: "majority"
Default read preference: primaryPreferred
Schema validation performed in application layer, not driver (Pydantic, Zod, etc.)

Naming Rules

Collections: snake_case, plural (e.g. chat_histories, user_settings, contents, content_metadata)
Fields: snake_case (e.g. user_id, created_at, updated_at)
Indexes: idx_{collection}_{field} / uidx_{collection}_{field}
Database: snake_case (e.g. myapp, myapp_log)

Field Type Guide

Use Case	Recommended Type	Notes
Document ID	`ObjectId`	Default `_id`, auto-generated
External ID	`string` (UUID)	For API-facing IDs
Integer	`int32` / `int64`	Use int64 for large counts
Boolean	`bool`	Never use 0/1 strings
String	`string`	Always validate max length in app
Timestamp	`date` (ISODate)	Always store in UTC
Decimal	`Decimal128`	Never use double for money
Embedded doc	`object`	For tightly coupled data
Reference	`ObjectId` / `int`	For loosely coupled relations
Tags/list	`array`	Prefer flat arrays
Free-form data	`object`	Use only when schema is truly dynamic

Prohibited Items

$where operator: prohibited (JS injection risk)
Unbounded arrays: prohibited (document size limit 16MB)
Deep nesting (4+ levels): discouraged
Storing binary files in documents: use GridFS or S3
Schema-less by habit: always define expected fields

Reference Files

document-design.md — Embed vs Reference strategy, content-centric design, global query avoidance
index-strategy.md — MongoDB index strategies that differ from RDBMS, multikey/partial/TTL
shard-key.md — Shard key selection principles, pattern-specific guides
connection-and-features.md — Async connection (PyMongo Async AsyncMongoClient; motor deprecated as of 2026-05), transactions, change streams

mongodb-patterns — Runtime query/aggregation/index/transaction/connection pool/diagnostic patterns (this guideline covers design conventions; patterns covers execution patterns).

More from this repository

same repository

archify

TeiNam/kiro-with-harness

Create professional architecture, workflow, sequence, data-flow, and lifecycle/state diagrams as standalone HTML files with SVG graphics, a built-in dark/light theme toggle, and one-click export to PNG / JPEG / WebP / SVG. Accepts plain-language descriptions or pasted Mermaid code (flowchart, sequenceDiagram, stateDiagram) and lays the diagram out from scratch in archify style. Use when the user asks for system architecture diagrams, infrastructure diagrams, cloud architecture visualizations, security diagrams, network topology, technical workflows, approval flows, runbooks, CI/CD flows, process diagrams, API call sequences, request lifecycles, data pipelines, ETL/ELT maps, PII boundaries, data lineage, state machines, lifecycle diagrams, status transitions, or asks to convert/beautify a Mermaid diagram.

2026-07-1511

analysis-methodology

TeiNam/kiro-with-harness

Data analysis methodology — how to frame a question, pick the right technique, avoid statistical traps, and connect results to decisions. NOT a tool tutorial (pandas/polars/duckdb live in python-data-analysis) — this is the judgment layer: problem framing, analysis-type decision tree, experiment/causal design, and domain playbooks (churn, cohort, funnel, anomaly). Trigger: "왜 늘었/줄었지", 이탈 분석, 코호트, 퍼널, A/B 테스트, 인과추론, 상관 vs 인과, 유의성, 세그먼트, 이상 탐지, "이 데이터로 뭘 봐야", 지표 설계, exploratory analysis.

2026-07-1311

aws-finops

TeiNam/kiro-with-harness

AWS cost management and FinOps practice — Cost Explorer, Budgets, Cost Anomaly Detection, CUR/data exports, cost allocation tags, Cost Categories, Savings Plans vs Reserved Instances, Compute Optimizer / Cost Optimization Hub, rightsizing, unit economics, showback/chargeback. Grounded in the FinOps Foundation Framework (Inform / Optimize / Operate). Trigger: cost anomaly, Savings Plan, Reserved Instance, rightsizing, cost allocation tag, chargeback, showback, unit cost, budget alert, CUR, Cost Explorer, unblended/amortized cost, RI coverage, commitment, "왜 청구서가 늘었지".

2026-07-1311

cost-tracking

TeiNam/kiro-with-harness

Track and report AI model token usage, spending, and budgets from a local cost-tracking database.

2026-07-1311

deep-research

TeiNam/kiro-with-harness

Multi-source deep research using firecrawl and exa MCPs. Searches the web, synthesizes findings, and delivers cited reports with source attribution. Use when the user wants thorough research on any topic with evidence and citations.

2026-07-1311

market-research

TeiNam/kiro-with-harness

Conduct market research, competitive analysis, investor due diligence, and industry intelligence with source attribution and decision-oriented summaries. Use when the user wants market sizing, competitor comparisons, fund research, technology scans, or research that informs business decisions.

2026-07-1311

name	mongodb-guideline
description	MongoDB 7.0+ schema design, collection/index creation, query optimization, sharding, and async connection management. Triggers: createCollection, createIndex, aggregation, $lookup, $match, $group, TTL index, async client, embedded document, content schema, metadata, document design, chat/log storage, user settings, content/metadata operations.
origin	custom
workloads	["mongodb"]

MongoDB Database Guideline

When to Activate

Designing MongoDB collection schemas (chat, log, user settings, content, metadata)
Writing queries or aggregation pipelines
Creating indexes (single, compound, TTL, text)
Troubleshooting slow queries
Setting up async driver connection (PyMongo Async / Node.js native driver)
Implementing TTL-based data expiry

MongoDB Version and Defaults

MongoDB 7.0+
Driver: raw async driver without ODM
- Python: PyMongo Async AsyncMongoClient (async) / pymongo 4.x (sync). motor is deprecated as of 2026-05.
- Node.js: mongodb 6.x (native driver)
Default write concern: w: "majority"
Default read preference: primaryPreferred
Schema validation performed in application layer, not driver (Pydantic, Zod, etc.)

Naming Rules

Collections: snake_case, plural (e.g. chat_histories, user_settings, contents, content_metadata)
Fields: snake_case (e.g. user_id, created_at, updated_at)
Indexes: idx_{collection}_{field} / uidx_{collection}_{field}
Database: snake_case (e.g. myapp, myapp_log)

Field Type Guide

Use Case	Recommended Type	Notes
Document ID	`ObjectId`	Default `_id`, auto-generated
External ID	`string` (UUID)	For API-facing IDs
Integer	`int32` / `int64`	Use int64 for large counts
Boolean	`bool`	Never use 0/1 strings
String	`string`	Always validate max length in app
Timestamp	`date` (ISODate)	Always store in UTC
Decimal	`Decimal128`	Never use double for money
Embedded doc	`object`	For tightly coupled data
Reference	`ObjectId` / `int`	For loosely coupled relations
Tags/list	`array`	Prefer flat arrays
Free-form data	`object`	Use only when schema is truly dynamic

Prohibited Items

$where operator: prohibited (JS injection risk)
Unbounded arrays: prohibited (document size limit 16MB)
Deep nesting (4+ levels): discouraged
Storing binary files in documents: use GridFS or S3
Schema-less by habit: always define expected fields

Reference Files

document-design.md — Embed vs Reference strategy, content-centric design, global query avoidance
index-strategy.md — MongoDB index strategies that differ from RDBMS, multikey/partial/TTL
shard-key.md — Shard key selection principles, pattern-specific guides
connection-and-features.md — Async connection (PyMongo Async AsyncMongoClient; motor deprecated as of 2026-05), transactions, change streams

mongodb-patterns — Runtime query/aggregation/index/transaction/connection pool/diagnostic patterns (this guideline covers design conventions; patterns covers execution patterns).