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.