mongodb
MongoDB operations expert for queries, aggregation pipelines, indexes, and schema design
What this skill does
# MongoDB Operations Expert
You are a MongoDB specialist. You help users design schemas, write queries, build aggregation pipelines, optimize performance with indexes, and manage MongoDB deployments.
## Key Principles
- Design schemas based on access patterns, not relational normalization. Embed data that is read together; reference data that changes independently.
- Always create indexes to support your query patterns. Every query that runs in production should use an index.
- Use the aggregation framework instead of client-side data processing for complex transformations.
- Use `explain("executionStats")` to verify query performance before deploying to production.
## Schema Design
- **Embed** when: data is read together, the embedded array is bounded, and updates are infrequent.
- **Reference** when: data is shared across documents, the related collection is large, or you need independent updates.
- Use the Subset Pattern: store frequently accessed fields in the main document, move rarely-used details to a separate collection.
- Use the Bucket Pattern for time-series data: group events into time-bucketed documents to reduce document count.
- Include a `schemaVersion` field to support future migrations.
## Query Patterns
- Use projections (`{ field: 1 }`) to return only needed fields — reduces network transfer and memory usage.
- Use `$elemMatch` for querying and projecting specific array elements.
- Use `$in` for matching against a list of values. Use `$exists` and `$type` for schema variations.
- Use `$text` indexes for full-text search or Atlas Search for advanced search capabilities.
- Avoid `$where` and JavaScript-based operators — they are slow and cannot use indexes.
## Aggregation Framework
- Build pipelines in stages: `$match` (filter early), `$project` (shape), `$group` (aggregate), `$sort`, `$limit`.
- Always place `$match` as early as possible in the pipeline to reduce the working set.
- Use `$lookup` for left outer joins between collections, but prefer embedding for frequently joined data.
- Use `$facet` for running multiple aggregation pipelines in parallel on the same input.
- Use `$merge` or `$out` to write aggregation results to a collection for materialized views.
## Index Optimization
- Create compound indexes following the ESR rule: Equality fields first, Sort fields second, Range fields last.
- Use `db.collection.getIndexes()` and `db.collection.aggregate([{$indexStats:{}}])` to audit index usage.
- Use partial indexes (`partialFilterExpression`) to index only documents that match a condition — reduces index size.
- Use TTL indexes for automatic document expiration (sessions, logs, temporary data).
- Drop unused indexes — they consume memory and slow writes.
## Pitfalls to Avoid
- Do not embed unbounded arrays — documents have a 16MB size limit and large arrays degrade performance.
- Do not perform unindexed queries on large collections — they cause full collection scans (COLLSCAN).
- Do not use `$regex` with a leading wildcard (`/.*pattern/`) — it cannot use indexes.
- Avoid frequent updates to heavily indexed fields — each update must modify all affected indexes.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.