cloudrun-development

from tencentcloudbase/skills

Production Ready Backend Development (CloudBase)Agent Skills

2 stars0 forksUpdated Jan 23, 2026
npx skills add https://github.com/tencentcloudbase/skills --skill cloudrun-development

SKILL.md

When to use this skill

Use this skill for CloudBase Run backend service development when you need:

  • Long connection capabilities: WebSocket / SSE / server push
  • Long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs
  • Custom runtime environments/system dependencies: custom images, specific system libraries
  • Multi-language/arbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.
  • Stable external services with elastic scaling: pay-as-you-go, can scale down to 0
  • Private/internal network access: VPC/PRIVATE access, mini-program callContainer internal direct connection
  • AI agent development: develop personalized AI applications based on Function mode CloudRun

Do NOT use for:

  • Simple cloud functions (use cloud function development instead)
  • Frontend-only applications
  • Database schema design (use data-model-creation skill)

How to use this skill (for a coding agent)

  1. Choose the right mode

    • Function mode: Fastest to get started, built-in HTTP/WebSocket/SSE, fixed port 3000, local running supported
    • Container mode: Any language and runtime, requires Dockerfile, local running not supported by tools
  2. Follow mandatory requirements

    • Must listen on PORT environment variable (real port in container)
    • Stateless service: write data externally (DB/storage/cache)
    • No background persistent threads/processes outside requests
    • Minimize dependencies, slim images; reduce cold start and deployment time
    • Resource constraints: Mem = 2 × CPU (e.g., 0.25 vCPU → 0.5 GB)
    • Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network
  3. Use tools correctly

    • Read operations: queryCloudRun (list, detail, templates)
    • Write operations: manageCloudRun (init, download, run, deploy, delete, createAgent)
    • Always use absolute paths for targetPath
    • Use force: true for delete operations
  4. Follow the workflow

    • Initialize project → Check/generate Dockerfile (for container mode) → Local run (function mode only) → Configure access → Deploy → Verify

CloudBase Run AI Development Rules

A concise guide for AI assistants and engineering collaboration, providing "when to use, how to use" rules and tool workflows.

1. When to use CloudBase Run (Use Cases)

  • Need long connection capabilities: WebSocket / SSE / server push
  • Need long-running or persistent processes: tasks that are not suitable for cloud functions, background jobs
  • Need custom runtime environments/system dependencies: custom images, specific system libraries
  • Use multi-language/arbitrary frameworks: Java, Go, PHP, .NET, Python, Node.js, etc.
  • Need stable external services with elastic scaling: pay-as-you-go, can scale down to 0
  • Need private/internal network access: VPC/PRIVATE access, mini-program callContainer internal direct connection
  • Need to develop AI agents: develop personalized AI applications based on Function mode CloudRun

2. Mode Selection (Quick Comparison)

  • Function mode: Fastest to get started, built-in HTTP/WebSocket/SSE, fixed port 3000; local running supported by tools
  • Container mode: Any language and runtime, requires Dockerfile; local running not supported by tools

Mode Comparison Checklist

DimensionFunction ModeContainer Mode
Language/FrameworkNode.js (via @cloudbase/functions-framework)Any language/runtime (Java/Go/PHP/.NET/Python/Node.js, etc.)
RuntimeFunction framework loads functions (Runtime)Docker image starts process
PortFixed 3000Application listens on PORT (injected by platform during deployment)
DockerfileNot requiredRequired (and must pass local build)
Local RunningSupported (built-in tools)Not supported (recommend using Docker for debugging)
Typical ScenariosWebSocket/SSE/streaming responses, forms/files, low latency, multiple functions per instance, shared memoryArbitrary system dependencies/languages, migrating existing containerized applications

3. Development Requirements (Must Meet)

  • Must listen on PORT environment variable (real port in container)
  • Stateless service: write data externally (DB/storage/cache)
  • No background persistent threads/processes outside requests
  • Minimize dependencies, slim images; reduce cold start and deployment time
  • Resource constraints: Mem = 2 × CPU (e.g., 0.25 vCPU → 0.5 GB)
  • Access control: Only enable public network for Web scenarios; mini-programs prioritize internal direct connection, recommend closing public network

4. Tools (Plain Language & Read/Write Separation)

  • Read operations (queryCloudRun):
    • list: What services do I have? Can filter by name/type
    • detail: Current configuration, version, access address of a service
    • templates: Ready-to-use starter templates
  • **Write

...

Read full content

Repository Stats

Stars2
Forks0