docs(config): update cloudbase rules and guidelines across IDE configs

- Sync cloudbase-rules in .augment-guidelines, .cursor, .clinerules,
  .comate, .gemini, .github, .lingma, .qoder, .qwen, .roo, .rules,
  .trae, .windsurf
- Update AGENTS.md, CLAUDE.md, CODEBUDDY.md
- Update skills-repo-template cloudbase-guidelines/SKILL.md

Author: binggg

config/.augment-guidelines

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.clinerules/cloudbase-rules.mdc

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.comate/rules/cloudbase-rules.mdr

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.cursor/rules/cloudbase-rules.mdc

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.gemini/GEMINI.md

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.github/copilot-instructions.md

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.lingma/rules/cloudbaase-rules.md

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.qoder/rules/cloudbase-rules.md

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard

config/.qwen/QWEN.md

@@ -427,6 +427,42 @@ If development is found to not comply with standards, can:
 
 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}`
 
+
+## Deployment Workflow
+
+When users request deployment to CloudBase:
+
+0. **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
+
+1. **Backend Deployment (if applicable)**:
+   - Only for nodejs cloud functions: deploy directly using `createFunction` tools
+     - Criteria: function directory contains `index.js` with cloud function format export: `exports.main = async (event, context) => {}`
+   - 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 `manageCloudRun` tool for deployment
+   - Set MinNum instances to at least 1 to reduce cold start latency
+
+2. **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
+
+3. **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
+
+4. **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
+
+
 ### Core Function Entry Points
 
 1. **Overview (概览)**: `#/overview` - Main dashboard