couchbase-data-modelinglisted

Design document models, choose document boundaries, and pick access patterns for Couchbase. Use whenever the user asks about document model, schema design, key design, document shape, embed vs reference, denormalization, scope vs collection vs bucket, modeling for query / index / FTS / vector search, time-series in Couchbase, TTL strategies, anti-patterns, migrating from SQL / MongoDB / DynamoDB / DocumentDB, or general 'how should I structure this data.' Triggers on design-phase conversations before any tools are called — distinct from the couchbase-mcp skill, which is for operating an existing cluster. Use proactively for: greenfield Couchbase projects, schema migrations, re-architecting an existing model, deciding between scopes/collections/buckets, modeling time-series or vector embeddings, planning denormalization tradeoffs, naming keys, choosing between embedded sub-documents and references.
celticht32/Couchbase-Skills-for-Claude.ai · ★ 1 · AI & Automation · score 77

Install: claude install-skill celticht32/Couchbase-Skills-for-Claude.ai

# Couchbase data modeling A skill for *designing* what to put in Couchbase, not operating an existing cluster. The companion `couchbase-mcp` skill is for executing operations; this one is for the architectural decisions that come before any tool is called. ## When this skill applies Use this skill whenever the conversation is about *what shape the data should take*, not *what tool to call*. Concrete signals: - "How should I model X in Couchbase?" - "Should I embed this or use references?" - "What's the right key format?" - "Bucket vs scope vs collection?" - "I'm coming from [MongoDB / Postgres / DynamoDB] — how do I think about this?" - "How do I model time-series / events / logs?" - "Where do I put the embedding vector?" - "Schema migration in Couchbase?" If the conversation has already moved to "now run this tool," switch to `couchbase-mcp`. These skills are designed to compose — modeling first, then operation. ## Pick the right reference | Question | Read | |---|---| | "What should my keys look like?" | `references/keys.md` | | "Should I embed or reference?" / "How big should one document be?" | `references/document-shape.md` | | "Bucket vs scope vs collection?" | `references/boundaries.md` | | "How do I model for fast queries / FTS / vector search?" | `references/access-patterns.md` | | "Time-series, event logs, anything with timestamps and TTL" | `references/time-series-and-ttl.md` | | "I think I'm doing something wrong" | `references/anti-patterns.md` | | "I'm co