cloudbase-guidelines
npx skills add https://github.com/tencentcloudbase/skills --skill cloudbase-guidelines
Agent 安装分布
Skill 文档
CloudBase Development Guidelines
ð¡ Recommended: MCP Installation
For enhanced CloudBase development experience, we recommend installing CloudBase MCP (Model Context Protocol).
CloudBase MCP provides essential tools for CloudBase development, including environment management, function deployment, database operations, and more. While not required, installing MCP will significantly improve your development workflow.
MCP Configuration Instructions
Most Coding Agents support project-level MCP configuration. The standard JSON configuration structure is:
{
"mcpServers": {
"cloudbase": {
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"]
}
}
}
Project-level configuration file locations:
- Cursor:
.cursor/mcp.json - Claude Code:
.mcp.json - Windsurf:
~/.codeium/windsurf/mcp_config.json(user-level, no project-level JSON config) - Cline: Check Cline settings for project-level MCP configuration file location
- GitHub Copilot Chat (VS Code): Check VS Code settings for MCP configuration file location
Format differences:
- Continue: Uses YAML format in
.continue/mcpServers/folder:
name: CloudBase MCP
version: 1.0.0
schema: v1
mcpServers:
- uses: stdio
command: npx
args: ["@cloudbase/cloudbase-mcp@latest"]
Using mcporter (CLI) When MCP Is Not Available
In environments that do not support MCP (e.g. moltbot) or when users are unsure how to configure MCP, use mcporter as a CLI to call MCP tools. Confirm with the user that Secret ID, Secret Key, and Env ID are set in the mcporter config.
Config: Default ./config/mcporter.json (override with --config). Prefer --output json for machine-readable results.
{
"mcpServers": {
"cloudbase-mcp": {
"description": "CloudBase MCP",
"command": "npx",
"args": ["@cloudbase/cloudbase-mcp@latest"],
"env": {
"TENCENTCLOUD_SECRETID": "<your_secret_id>",
"TENCENTCLOUD_SECRETKEY": "<your_secret_key>",
"CLOUDBASE_ENV_ID": "<your_env_id>"
}
}
}
}
Quick start:
mcporter listâ list servers/toolsmcporter list <server> --schemaâ show tool schemamcporter call <server.tool> key=valueâ call a tool
Call examples:
- Selector:
mcporter call linear.list_issues team=ENG limit:5 - Function syntax:
mcporter call "linear.create_issue(title: \"Bug\")" - JSON payload:
mcporter call <server.tool> --args '{"limit":5}'
Quick Reference
When Developing a Web Project:
- Platform: Read the
web-developmentskill for SDK integration, static hosting, and build configuration - Authentication: Read the
auth-webandauth-toolskills – Use Web SDK built-in authentication - Database:
- NoSQL:
no-sql-web-sdkskill - MySQL:
relational-database-webandrelational-database-toolskills
- NoSQL:
- UI Design (Recommended): Read the
ui-designskill for better UI/UX design guidelines
When Developing a Mini Program Project:
- Platform: Read the
miniprogram-developmentskill for project structure, WeChat Developer Tools, and wx.cloud usage - Authentication: Read the
auth-wechatskill – Naturally login-free, get OPENID in cloud functions - Database:
- NoSQL:
no-sql-wx-mp-sdkskill - MySQL:
relational-database-toolskill (via tools)
- NoSQL:
- UI Design (Recommended): Read the
ui-designskill for better UI/UX design guidelines
When Developing a Native App Project (iOS/Android/Flutter/React Native/etc.):
- â ï¸ Platform Limitation: Native apps do NOT support CloudBase SDK – Must use HTTP API
- Required Skills:
http-api– HTTP API usage for all CloudBase operationsrelational-database-tool– MySQL database operations (via tools)auth-tool– Authentication configuration
- â ï¸ Database Limitation: Only MySQL database is supported. If users need MySQL, prompt them to enable it in console: CloudBase Console – MySQL Database
Core Capabilities
1. Authentication
Authentication Methods by Platform:
- Web Projects: Use CloudBase Web SDK built-in authentication, refer to the
auth-webskill - Mini Program Projects: Naturally login-free, get
wxContext.OPENIDin cloud functions, refer to theauth-wechatskill - Node.js Backend: Refer to the
auth-nodejsskill
Configuration:
- When user mentions authentication requirements, read the
auth-toolskill to configure authentication providers - Check and enable required authentication methods before implementing frontend code
2. Database Operations
Web Projects:
- NoSQL Database: Refer to the
no-sql-web-sdkskill - MySQL Relational Database: Refer to the
relational-database-webskill (Web) andrelational-database-toolskill (Management)
Mini Program Projects:
- NoSQL Database: Refer to the
no-sql-wx-mp-sdkskill - MySQL Relational Database: Refer to the
relational-database-toolskill (via tools)
3. Deployment
Static Hosting (Web):
- Use CloudBase static hosting after build completion
- Refer to the
web-developmentskill for deployment process - Remind users that CDN has a few minutes of cache after deployment
Backend Deployment:
- Cloud Functions: Refer to the
cloud-functionsskill – Runtime cannot be changed after creation, must select correct runtime initially - CloudRun: Refer to the
cloudrun-developmentskill – Ensure backend code supports CORS, prepare Dockerfile for container type
4. UI Design (Recommended)
For better UI/UX design, consider reading the ui-design skill which provides:
- Design thinking framework
- Frontend aesthetics guidelines
- Best practices for creating distinctive and high-quality interfaces
Platform-Specific Skills
Web Projects
web-development– SDK integration, static hosting, build configurationauth-web– Web SDK built-in authenticationno-sql-web-sdk– NoSQL database operationsrelational-database-web– MySQL database operations (Web)relational-database-tool– MySQL database managementcloud-storage-web– Cloud storage operationsai-model-web– AI model calling for Web apps
Mini Program Projects
miniprogram-development– Project structure, WeChat Developer Tools, wx.cloudauth-wechat– Authentication (naturally login-free)no-sql-wx-mp-sdk– NoSQL database operationsrelational-database-tool– MySQL database operationsai-model-wechat– AI model calling for Mini Program
Native App Projects
http-api– HTTP API usage (MANDATORY – SDK not supported)relational-database-tool– MySQL database operations (MANDATORY)auth-tool– Authentication configuration
Universal Skills
cloudbase-platform– Universal CloudBase platform knowledgeui-design– UI design guidelines (recommended)spec-workflow– Standard software engineering process
Professional Skill Reference
Platform Development Skills
- Web:
web-development– SDK integration, static hosting, build configuration - Mini Program:
miniprogram-development– Project structure, WeChat Developer Tools, wx.cloud - Cloud Functions:
cloud-functions– Cloud function development, deployment, logging, HTTP access - CloudRun:
cloudrun-development– Backend deployment (functions/containers) - Platform (Universal):
cloudbase-platform– Environment, authentication, services
Authentication Skills
- Web:
auth-web– Use Web SDK built-in authentication - Mini Program:
auth-wechat– Naturally login-free, get OPENID in cloud functions - Node.js:
auth-nodejs - Auth Tool:
auth-tool– Configure and manage authentication providers
Database Skills
- NoSQL (Web):
no-sql-web-sdk - NoSQL (Mini Program):
no-sql-wx-mp-sdk - MySQL (Web):
relational-database-web - MySQL (Tool):
relational-database-tool
Storage Skills
- Cloud Storage (Web):
cloud-storage-web– Upload, download, temporary URLs, file management
AI Skills
- AI Model (Web):
ai-model-web– Text generation and streaming via @cloudbase/js-sdk - AI Model (Node.js):
ai-model-nodejs– Text generation, streaming, and image generation via @cloudbase/node-sdk â¥3.16.0 - AI Model (WeChat):
ai-model-wechat– Text generation and streaming with callbacks via wx.cloud.extend.AI
UI Design Skill
ui-design– Design thinking framework, frontend aesthetics guidelines (recommended for UI work)
Workflow Skills
- Spec Workflow:
spec-workflow– Standard software engineering process (requirements, design, tasks)
Core Behavior Rules
- Project Understanding: Read current project’s README.md, follow project instructions
- Development Order: Prioritize frontend first, then backend
- Backend Strategy: Prefer using SDK to directly call CloudBase database, rather than through cloud functions, unless specifically needed
- Deployment Order: When there are backend dependencies, prioritize deploying backend before previewing frontend
- Authentication Rules: Use built-in authentication functions, distinguish authentication methods by platform
- Web Projects: Use CloudBase Web SDK built-in authentication (refer to
auth-web) - Mini Program Projects: Naturally login-free, get OPENID in cloud functions (refer to
auth-wechat) - Native Apps: Use HTTP API for authentication (refer to
http-api)
- Web Projects: Use CloudBase Web SDK built-in authentication (refer to
- Native App Development: CloudBase SDK is NOT available for native apps, MUST use HTTP API. Only MySQL database is supported.
Deployment Workflow
When users request deployment to CloudBase:
-
Check Existing Deployment:
- Read README.md to check for existing deployment information
- Identify previously deployed services and their URLs
- Determine if this is a new deployment or update to existing services
-
Backend Deployment (if applicable):
- Only for nodejs cloud functions: deploy directly using
createFunctiontools- Criteria: function directory contains
index.jswith cloud function format export:exports.main = async (event, context) => {}
- Criteria: function directory contains
- For other languages backend server (Java, Go, PHP, Python, Node.js): deploy to Cloud Run
- Ensure backend code supports CORS by default
- Prepare Dockerfile for containerized deployment
- Use
manageCloudRuntool for deployment - Set MinNum instances to at least 1 to reduce cold start latency
- Only for nodejs cloud functions: deploy directly using
-
Frontend Deployment (if applicable):
- After backend deployment completes, update frontend API endpoints using the returned API addresses
- Build the frontend application
- Deploy to CloudBase static hosting using hosting tools
-
Display Deployment URLs:
- Show backend deployment URL (if applicable)
- Show frontend deployment URL with trailing slash (/) in path
- Add random query string to frontend URL to ensure CDN cache refresh
-
Update Documentation:
- Write deployment information and service details to README.md
- Include backend API endpoints and frontend access URLs
- Document CloudBase resources used (functions, cloud run, hosting, database, etc.)
- This helps with future updates and maintenance
CloudBase Console Entry Points
After creating/deploying resources, provide corresponding console management page links. All console URLs follow the pattern: https://tcb.cloud.tencent.com/dev?envId=${envId}#/{path}
Core Function Entry Points
- Overview (æ¦è§):
#/overview– Main dashboard - Template Center (模æ¿ä¸å¿):
#/cloud-template/market– Project templates - Document Database (ææ¡£åæ°æ®åº):
#/db/doc– NoSQL collections:#/db/doc/collection/${collectionName}, Models:#/db/doc/model/${modelName} - MySQL Database (MySQL æ°æ®åº):
#/db/mysql– Tables:#/db/mysql/table/default/ - Cloud Functions (äºå½æ°):
#/scf– Function detail:#/scf/detail?id=${functionName}&NameSpace=${envId} - CloudRun (äºæç®¡):
#/platform-run– Container services - Cloud Storage (äºåå¨):
#/storage– File storage - AI+:
#/ai– AI capabilities - Static Website Hosting (éæç½ç«æç®¡):
#/static-hosting - Identity Authentication (身份认è¯):
#/identity– Login:#/identity/login-manage, Tokens:#/identity/token-management - Weida Low-Code (å¾®æä½ä»£ç ):
#/lowcode/apps - Logs & Monitoring (æ¥å¿çæ§):
#/devops/log - Extensions (æ©å±åè½):
#/apis - Environment Settings (ç¯å¢é
ç½®):
#/env