/cloudbase-document-database-web-sdk

name: cloudbase-document-database-web-sdk
description: Use CloudBase document database Web SDK only for confirmed NoSQL collection work. Query, create, update, and delete document data; if the task mentions PostgreSQL / CloudBase PG / app.rdb(), route to postgresql-development instead.
version: 2.34.3
alwaysApply: false

Sibling skills (local only)

Sibling CloudBase skills ship beside this skill. Use local relative paths such as `../auth-tool-cloudbase/SKILL.md`.

If a referenced sibling skill file is missing from this environment, ask the user to install the full CloudBase plugin (or the missing skill). Do **not** HTTP-fetch remote skill or protocol markdown into the agent context.

CloudBase Document Database Web SDK

Activation Contract

Use this first when

• A browser or Web app must read or write CloudBase document database data through `@cloudbase/js-sdk`.
• The request mentions `app.database()`, `db.collection()`, `.where()`, `.watch()`, pagination, aggregation, or geolocation queries in a Web frontend.

Read before writing code if

• The task is clearly browser-side, but you still need to decide between Web SDK, Mini Program SDK, or backend access.
• The request touches login state, collection permissions, or realtime updates.

Then also read

• Web login and caller identity -> `../auth-web-cloudbase/SKILL.md`
• General Web app structure -> `../web-development/SKILL.md`
• Mini Program database code -> `../cloudbase-document-database-in-wechat-miniprogram/SKILL.md`

Do NOT use for

• Mini Program code using `wx.cloud.database()`.
• Server-side or cloud-function database access.
• SQL / MySQL database operations.
• Pure resource-permission administration with no browser SDK code.
• **NEW business tables that the task explicitly asks to put in CloudBase PostgreSQL (CloudBase PG).** Before applying this skill, call `envQuery(action="info", envId=...)` and read `EnvInfo.RuntimeBackends`. If `postgresql === true` AND the task asks for a new business table to live in PG, switch to the `postgresql-development-cloudbase` skill for that table: it goes through `app.rdb()`, uses PG row-level security (`CREATE POLICY`), and uploads via `app.storage.from('<bucket>').upload('<key>', file)` against an explicitly-created pgstore bucket.
• Existing NoSQL collections in the same env keep using THIS skill — PG and NoSQL coexist in CloudBase PG environments. The rule is "follow the task / existing surface", not "PG env forbids NoSQL".

SDK Code vs MCP Tools

**When to write SDK code (use this skill):**

• The task explicitly asks to "modify code" or "use SDK"
• The task asks to implement app/frontend logic
• The task mentions specific SDK methods like `db.collection().add()`, `.get()`, `.update()`
• The context shows an existing Web project with SDK initialization (e.g., `index.js` already has `cloudbase.init()`)

**When to use MCP tools instead:**

• The task asks to manage CloudBase resources (create collection, set permissions, etc.)
• The task involves admin/management operations without writing app code
• The task mentions tools like `writeNoSqlDatabaseContent`, `managePermissions`, etc.

**Key distinction:** If the user says "使用 JS SDK 执行 XX 操作" (use JS SDK to perform XX operation) or "修改代码" (modify code), write SDK code in the project files. Do not use MCP database write tools for app-level data operations.

Common mistakes / gotchas

• Querying before the user is signed in when the collection rules require identity.
• Using `wx.cloud.database()` or Node SDK patterns in browser code.
• Initializing CloudBase lazily with dynamic imports instead of a shared synchronous app instance.
• Treating security rules as result filters rather than request validators.
• **Expecting a `CUSTOM` security rule to take effect immediately after you call `managePermissions(updateResourcePermission)`.** The backend caches rule evaluators for **2–5 minutes**; first writes after a rule change may silently fail or be rejected with `DATABASE_PERMISSION_DENIED` even when the expression is correct. Either (a) wait a few minutes and retry the same write before assuming the rule is wrong, or (b) verify the rule is live by reading `result.code` / `result.message` on every write and by doing a `get()` round-trip on the just-written `_id`; do not treat a resolved promise as success. See `security-rules.md` → "Propagation And Verification" for the full pattern.
• Misreading the return shape of `db.collection(...).add(...)`. In the CloudBase Web SDK, the created document ID is exposed at top-level `result._id`, not `result.id`, `result.data.id`, or `result.insertedId`.
• For CMS-style collections that need **app-level admin users** to edit/delete all records while editors can only edit/delete their own records, do not oversimplify the rule to `READONLY`. A validated pattern is a `CUSTOM` rule that reads role from `user_roles` by `auth.uid` and combines it with `doc.authorId == auth.uid`, while frontend writes can stay on `.doc(id).update()` / `.doc(id).remove()`.
• Forgetting pagination or indexes for larger collections.

Minimal checklist

• Confirm this is browser-side document database work.
• Initialize CloudBase once and reuse the same `app` / `db` instance.
• Verify auth expectations before CRUD.
• Read the right companion reference file for the specific operation.

Overview

This skill covers **browser-side document database usage** via `@cloudbase/js-sdk`.

Use it for:

• CRUD in a Web app
• complex queries and pagination
• aggregation
• realtime listeners with `watch()`
• geolocation queries

Canonical initialization

import cloudbase from "@cloudbase/js-sdk";

const app = cloudbase.init({
  env: "your-env-id"
});

const db = app.database();
const _ = db.command;

Important rules:

• Sign in before querying if the collection rules require identity.
• Keep a single shared app/database instance.
• Do not hide initialization inside ad-hoc async loaders