本文へ移動
cccskills
無料GitHub で公開

relational-database-web-cloudbase

[Deprecated] Use when building frontend Web apps that talk to CloudBase Relational Database via @cloudbase/js-sdk – provides the canonical init pattern so you can then use Supabase-style queries from the browser. New environments should use PostgreSQL with app.rdb() — see postgresql-development skill instead.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md4.7 KB
  • LICENSE.md1.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 Relational Database Web SDK

Activation Contract

Use this first when

  • A browser or Web app must access CloudBase Relational Database through @cloudbase/js-sdk.
  • The task is specifically about frontend initialization and browser-side query usage.

Read before writing code if

  • You need to distinguish browser SDK usage from MCP database management or backend Node access.
  • The request mentions Supabase migration, shared frontend DB client, or browser-side table queries.

Then also read

  • MySQL SQL management and MCP operations -> ../relational-database-mcp-cloudbase/SKILL.md
  • Web auth/login -> ../auth-web-cloudbase/SKILL.md
  • General Web app setup -> ../web-development/SKILL.md

Do NOT use for

  • MCP-based SQL management, schema changes, or permissions management (provisioning is not offered through MCP).
  • Backend/Node service access.
  • Document database operations.

Common mistakes / gotchas

  • Initializing SDKs in an MCP management flow.
  • Treating app itself as the relational database client.
  • Re-initializing CloudBase in every component.
  • Mixing frontend browser access with admin-style schema mutations.

Minimal checklist

  • Confirm the caller is a Web frontend.
  • Keep one shared CloudBase app and one shared relational DB client.
  • Route MySQL management/schema work on an existing instance to relational-database-mcp-cloudbase (it does not provision). If the task says PostgreSQL, CloudBase PG, PG mode, app.rdb(), queryPgDatabase, managePgDatabase, or RLS, route to postgresql-development-cloudbase instead.
  • Handle auth separately before data access.

Overview

This skill standardizes the browser-side initialization pattern for CloudBase Relational Database.

After initialization, use db with Supabase-style query patterns.

Installation

npm install @cloudbase/js-sdk

Canonical initialization

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

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

const auth = app.auth;
// Handle login separately

const db = app.rdb();

Initialization rules

  • Initialize synchronously.
  • Do not lazy-load the SDK with import("@cloudbase/js-sdk") unless the framework absolutely requires it.
  • Create one shared db client and reuse it.
  • Do not invent unsupported cloudbase.init() options.

Quick routing

Use this skill when

  • you are wiring browser components to relational tables
  • you are replacing a Supabase browser client with CloudBase
  • you need a canonical shared frontend db client

Use relational-database-mcp-cloudbase instead when

  • you need to create/destroy MySQL
  • you need MySQL DDL or write-SQL administration
  • you need to inspect or change MySQL table security rules through MCP

Use postgresql-development-cloudbase instead when

  • the task says PostgreSQL, CloudBase PG, PG mode, app.rdb(), queryPgDatabase, managePgDatabase, PostgREST, or RLS
  • browser-side table code must use PG semantics rather than legacy NoSQL / MySQL management tools

Example: shared frontend DB client

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

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

export const db = app.rdb();

Example: Supabase-style query

const { data, error } = await db
  .from("posts")
  .select("*")
  .order("created_at", { ascending: false });

if (error) {
  console.error("Failed to load posts", error.message);
}

Example: insert / update / delete

await db.from("posts").insert({ title: "Hello" });
await db.from("posts").update({ title: "Updated" }).eq("id", 1);
await db.from("posts").delete().eq("id", 1);

Key principle

  • app.rdb() gives you the relational database client.
  • After that point, use Supabase-style query knowledge for table operations.
  • Keep schema management and privileged administration outside browser code.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use this skill for Node.js backend AI via @cloudbase/node-sdk (>=3.16.0) — cloud functions, CloudRun, Express/Koa/NestJS, serverless APIs, scheduled jobs, LLM proxies, agent orchestration. The only SDK supporting image generation (ai.createImageModel + generateImage). Text via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*; model ids (e.g. deepseek-v4-flash, glm-5, kimi-k2.6) go in the `model` field of generateText/streamText. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web) or Mini Program (use ai-model-wechat).

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

Use this skill when a browser/Web app (React, Vue, Next, Nuxt, static sites, SPAs, dashboards, AI chat UI, 页面, 前端, 网页) needs AI models via @cloudbase/js-sdk. Default routing for Web/frontend AI — call directly from the browser, do NOT propose a Node.js proxy. Covers generateText and streamText; models via ai.createModel with groups cloudbase, hunyuan-exp, or custom-*, model id in the `model` field. MUST run two-step preflight before code — see body. NOT for Node.js backend (use ai-model-nodejs), Mini Program (use ai-model-wechat), or image generation (Node SDK only).

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

Use this skill for WeChat Mini Program AI via wx.cloud.extend.AI (小程序, wx.cloud apps). Covers generateText and streamText with callbacks (onText, onEvent, onFinish); streamText needs a data wrapper, generateText returns the raw response. Models via wx.cloud.extend.AI.createModel with groups hunyuan-exp (小程序成长计划), cloudbase (main managed), or custom-*; model id goes in the data wrapper `model` field. MUST run two-step preflight before code — see body. NOT for browser/Web (use ai-model-web), Node.js backend (use ai-model-nodejs), or image generation (use ai-model-nodejs).

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

CloudBase auth provider configuration and login-readiness guide. This skill should be used when users need to inspect, enable, disable, or configure auth providers, publishable-key prerequisites, login methods, SMS/email sender setup, or other provider-side readiness before implementing a client or backend auth flow.

日本語の概要は準備中です。原文の説明を表示しています。

TencentCloudBase/CloudBase-AI-Toolkit1,1362026年10月11日 更新

TencentCloudBase のスキルをすべて見る

このスキルの問題を報告する