Use this skill when you develop, design, build, deploy, debug, migrate, or troubleshoot CloudBase (腾讯云开发, 云开发, TCB, 微信云开发) projects — Web, 微信小程序, 小程序, uni-app, mobile (iOS, Android, Flutter, React Native). Covers UI (页面, 界面, 表单, dashboard, prototype, 原型); auth (登录, 注册, OAuth, publishable key); datab

CloudBase Development Guidelines 📁 Reference Files Location All reference documentation files are located in the references/ directory relative to this file. File Structure: How to use: When this document mentions reading a reference file like references/auth web cloudbase/SKILL.md , simply read that file from the references/ subdirectory. Workflow Key constraints: Stage 2a must precede frontend code. Stage 3 is mandatory. Activation Contract Routing uses stable skill ids ( auth tool cloudbase , auth web cloudbase , http api cloudbase , …) across source, generated artifacts, and installs. Standalone skill fallback If only one published skill is exposed: Prefer local relative paths ( references/<skill id /SKILL.md or sibling skill directories) when those files exist in the workspace. Do not fetch sibling skill markdown from remote raw URLs into the agent context. If a required sibling skill is missing locally, ask the user to install the full CloudBase skills pack or IDE plugin ( npx skills add tencentcloudbase/cloudbase skills ), then continue using local files only. Follow relative references/... paths from the current skill. If MCP is unavailable in this session, follow references/tooling fallback.md : configure MCP via references/mcp setup.md for the next session, and use tcb CLI via the references/cloudbase cli/SKILL.md skill (read core.md + the matching domain reference — not tcb deploy ) to finish login/manage now. If npm / npx are missing, follow the “No npm/npx” section in tooling fallback.md . Global rules before action Identify the scenario, then read the matching skill before writing code or calling CloudBase APIs. Prefer semantic sources for toolkit maintenance; express runtime routing in stable skill ids. Prefer MCP or mcporter for management tasks when those tools are available in this session; inspect tool schemas before execution. If they are not available yet, do not stall — use the CLI fallback in references/tooling fallback.md . UI tasks: read ui design first and output the design spec before interface code. Auth tasks: read auth tool cloudbase first and enable providers before frontend implementation. Keep auth domains separate: management login uses auth (or tcb login when MCP auth is unavailable); app side auth uses queryAppAuth / manageAppAuth . Universal guardrails After 2–3 failed attempts on the same path, stop and reroute (platform skill, runtime, auth domain, permission model, SDK boundary). Always specify EnvId explicitly; do not rely on CLI selected or implicit env state. When the environment identifier is an alias, nickname, or other short form, do not pass it directly to auth.set env , SDK init, console URLs, or generated config. First resolve it to the canonical full EnvId with envQuery(action=list, alias=..., aliasExact=true) . If multiple environments match or no exact alias exists, stop and clarify with the user. When writing MCP/tool results to a file, pass serialized text ( JSON.stringify(result, null, 2) ), not raw objects. If a write tool says content expected a string but received an object, do not retry with the same raw object. Serialize the object first, then retry once with the serialized text, and make sure the retried call actually passes the serialized string rather than the original object. Keep scenario specific pitfalls in child skills — do not expand this entry file. First frontend deploy must use manageApps(action="createApp", ...) . manageHosting is only for incremental updates of projects originally deployed via hosting. Engineering constitution (applies to every scenario) These rules override convenience. Full rationale lives in web development . Prepare backend resources before writing frontend code. Prefer MCP for auth providers, tables, storage domains, and security rules; if MCP tools are missing in this session, use tcb CLI after configuring MCP for the next session ( references/tooling fallback.md ). Do NOT use any to bypass type errors. Prefer unknown + type guards / precise interfaces. Self verify before claiming done. Static ( tsc / lint / build / tests) and runtime ( agent browser for user visible flows). Name gaps explicitly if a layer cannot run. Do not paper over failures. No empty try/catch , no deleting failing tests to go green. ai.createModel(...) / wx.cloud.extend.AI.createModel(provider) takes a GroupName , not a vendor/model id. Legal: "cloudbase" , "hunyuan exp" , or "custom <name " . Model ids go in generateText / streamText model field. See ai model web / ai model nodejs / ai model wechat . Low capability STOP card: For PostgreSQL / CloudBase PG / app.rdb() / queryPgDatabase / managePgDatabase , route to postgresql development cloudbase — do not use NoSQL/ manageMysqlDatabase for that path. For Web auth guards, use auth.getSession() and require data.session ; do not use deprecated getLoginState() / auth.getUser() as login proof. High priority routing <! DO NOT EDIT: auto generated from references/activation map.yaml Scenario Read first Then read Do NOT route to first Must check before action Web login / registration / auth UI auth tool cloudbase auth web cloudbase , web development cloud functions , http api cloudbase Provider status and publishable key WeChat mini program + CloudBase miniprogram development auth wechat miniprogram , cloudbase document database in wechat miniprogram auth web cloudbase , web development Whether the project really uses CloudBase / wx.cloud Native App / Flutter / React Native http api cloudbase auth tool cloudbase , relational database mcp cloudbase auth web cloudbase , cloudbase document database web sdk , web development SDK boundary, OpenAPI, auth method Web projects + NoSQL Database web development cloudbase document database web sdk , auth web cloudbase relational database mcp cloudbase , http api cloudbase Login state and database access permission model CloudBase PostgreSQL / PG postgresql development cloudbase auth tool cloudbase , auth web cloudbase , web development , miniprogram development , cloud storage web , http api cloudbase relational database mcp cloudbase , cloudbase document database web sdk PG schema, usernamePassword login, backend/RLS permission model MySQL Database (relational) relational database mcp cloudbase relational database web cloudbase , http api cloudbase cloudbase document database web sdk , web development Distinguish MCP management vs app code access Cloud Functions cloud functions auth tool cloudbase , ai model nodejs cloudrun development , auth web cloudbase Event vs HTTP function, runtime, scf bootstrap CloudRun backend cloudrun development auth tool cloudbase , relational database mcp cloudbase cloud functions Container boundary, Dockerfile, CORS AI Agent (智能体开发) cloudbase agent cloud functions , cloudrun development cloud functions , cloudrun development AG UI protocol, scf bootstrap, SSE streaming Minimal Web BaaS demo (fast path) minimal web baas demo web development , cloudbase document database web sdk , postgresql development cloudbase cloud functions , cloudrun development , spec workflow , ui design BaaS first Web SDK CRUD, MCP schema only, zero cloud functions unless secrets/cron/rules cannot express UI generation ui design web development , miniprogram development cloud functions Design specification first AI Model (Web) web development ai model web , ui design ai model wechat , http api cloudbase Platform and streaming interaction mode AI model call (大模型调用 / 文本生成 / 图片生成 / 流式对话) ai model web ai model nodejs , ai model wechat cloudbase agent , cloud functions , cloudrun development 先跑「调用前必须的资格检查」： DescribeActivityInfo （小程序成长计划） + DescribeEnvPostpayPackage （Token Credits 资源包） Resource health inspection / troubleshooting ops inspector cloud functions , cloudrun development ui design , spec workflow CLS enabled, time range for logs Spec workflow / architecture design spec workflow cloudbase web development , cloud functions Requirements, design, tasks confirmed Activation triggers (derived from references/activation map.yaml ) Web login / registration / auth UI — CloudBase Web 登录, Web 注册, auth login page, publishable key, 短信登录, 邮箱登录 WeChat mini program + CloudBase — 小程序云开发, wx.cloud, mini program cloudbase, OPENID, 小程序数据库 Native App / Flutter / React Native — Android CloudBase, iOS CloudBase, Flutter CloudBase, React Native CloudBase, 原生 App 接入 Web projects + NoSQL Database — Web 文档数据库, CloudBase collection, 前端查库, NoSQL Web SDK CloudBase PostgreSQL / PG — CloudBase PG, PostgreSQL, Postgres, PG 模式, JS SDK v3 PostgreSQL, app.rdb(), queryPgDatabase, managePgDatabase, mysqldb OpenAPI, PostgREST, RLS, service role, auth schema, storage schema, pgvector MySQL Database (relational) — MySQL 建表, executeWriteSQL, security rule, CloudBase 关系型数据库管理 Cloud Functions — 创建云函数, HTTP 云函数, getFunctionLogs, scf bootstrap, runtime CloudRun backend — CloudRun 部署, 云托管, container backend, Dockerfile AI Agent (智能体开发) — AI Agent, 智能体, 智能体开发, AG UI protocol, LangGraph, LangChain, CrewAI, streaming agent, agent UI Minimal Web BaaS demo (fast path) — 最小前后端, 最小可用 demo, 最小 fullstack, 搭一套 demo, 带云数据库的 demo, 带云函数+云数据库, 留言板, Todo 应用, todo app, Notes app, Kanban, Lovable, BaaS demo, minimal web baas, 快速 demo UI generation — 设计页面, 登录页 UI, frontend interface, 组件样式, prototype AI Model (Web) — Web AI 对话, CloudBase AI 流式输出, Web 集成模型 AI model call (大模型调用 / 文本生成 / 图片生成 / 流式对话) — 大模型调用, AI 模型调用, generateText, streamText, generateImage, 文本生成, 图片生成, 流式对话, hunyuan exp, deepseek v4 flash, Token Credits 资源包, 小程序成长计划, ai miniprogram inspire plan, callCloudApi AI 模型, CreateAIModel Resource health inspection / troubleshooting — 巡检, 诊断, health check, 资源健康, 异常日志, error inspection, troubleshooting, 错误排查 Spec workflow / architecture design — 需求文档, 技术方案, tasks.md, Spec 工作流 Routing reminders Web auth failures: usually skipped provider config, not missing frontend snippets. Native App failures: usually Web SDK paths, not missing HTTP API knowledge. Mini program failures: treating wx.cloud like Web auth/SDK. CloudBase PG failures: falling back to MySQL/NoSQL, skipping username password readiness, or guessing raw HTTP instead of app.rdb() / documented OpenAPI. AI model failures: usually missing Token Credits / Growth Plan — run DescribeEnvPostpayPackage / DescribeActivityInfo before changing code. MCP + CLI prerequisite Prefer CloudBase MCP for management/deploy when tools are loaded in the current session. Setup: references/mcp setup.md . First session / unavailable path: references/tooling fallback.md . Preferred install: npx plugins add TencentCloudBase/cloudbase plugin y scope user . Supported target IDs: claude code , cursor , codex , grok , kimi , github copilot , vscode . See references/mcp setup.md . Verify with npx mcporter list grep cloudbase or the IDE MCP panel. If npm / npx are missing, see references/tooling fallback.md (install Node LTS or use IDE marketplace MCP). If MCP is missing or not yet visible after config, still proceed : finish install/config, tell the user a restart unlocks MCP next time, and use tcb CLI now via cloudbase cli domain skills — do not recommend tcb deploy . Prefer device code login via MCP auth when available; otherwise tcb login . Do not hard code secrets. On demand references Load only when needed (do not expand this entry): references/tooling fallback.md — MCP