Help us improve
Share bugs, ideas, or general feedback.
From defang
Guides Defang CLI deployment of projects to cloud: validates CLI install, authenticates, creates/manages compose.yaml, selects stacks on AWS/GCP/DigitalOcean, sets configs.
npx claudepluginhub defanglabs/defang --plugin defangHow this skill is triggered — by the user, by Claude, or both
Slash command
/defang:deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Deploy the current project using the Defang CLI by following these steps:
Generates complete deployment configurations—Dockerfile, manifests, environment config, rollback procedures—for Node.js, Python, Go, Rust, Java services. Useful for deployment setup, strategy, or rollback queries.
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
Researches infrastructure best practices and generates Terraform modules, Dockerfiles, Kubernetes manifests, Pulumi programs, and CI/CD pipelines for GCP, AWS, Azure deployments.
Share bugs, ideas, or general feedback.
Deploy the current project using the Defang CLI by following these steps:
Run defang --version to confirm the CLI is installed. If it is not found, install it:
npm install -g @defang-io/defangbrew install DefangLabs/defang/defangeval "$(curl -fsSL s.defang.io/install)"If you installed defang for the first time, run /reload-plugins to activate the Defang MCP server.
Run defang whoami to check if the user is already logged in. If not, run defang login and wait for authentication to complete.
Look for any compose.yaml files in the current directory or parent directories. If multiple are found, ask the user to select one. If none are found, ask the user if they want to create a new one. If yes, ask them about the services they want to deploy and generate a compose.yaml based on their answers. You will need to know which command each service should run, any environment variables they require, whether or not they should listen on a port, and if so, which one, and so on.
A stack is a single deployed instance of the project in a specific cloud account and region, for example: production is deployed to aws in us-east-1. Additional configuration associated with a stack can be specified in the stack file (e.g., .defang/production). Note that stack variables are read at deployment time, and are not available at runtime in your application services.
List existing stacks:
defang stack list
To create a stack interactively:
defang stack new
Required parameters:
production)aws, gcp, or digitaloceanus-east-1 (AWS), us-central1 (GCP)affordable — lowest cost, for dev/test (default)balanced — general production workloadshigh_availability — critical servicesAfter creating a stack, set it as the default:
defang stack default STACK_NAME
Check the compose.yaml for environment variables listed without a value — these must be set as configs before deployment.
List configs already set:
defang config ls
For each unset config, ask the user whether to provide a specific value or generate a random one. Do not assume a default. Then set it:
# specific value
defang config set KEY=value
# random value
defang config set --random KEY
# prompted securely (interactive)
defang config set KEY
defang compose up
Useful flags:
-d / --detach: return immediately without streaming logs--force: force a fresh image build even if nothing changed--mode affordable|balanced|high_availability: override the stack's deployment modeThe CLI will stream logs automatically. If the deployment fails, Defang may offer an AI-assisted debug prompt — allow it to run before investigating manually.
Once deployment completes, check service status and endpoints:
defang compose ps
To tail logs after the fact:
defang logs --follow
defang logs SERVICE_NAME --follow # filter to one service