deploy-gen
Generate deployment configurations (Docker, Kubernetes) for the current project
What this skill does
<!-- AIWG-SKILL-CALLOUT -->
> **Skill access pattern (post-kernel-pivot, 2026.5+)**
>
> Skill names referenced in this document are AIWG skills, **not slash commands**. Most are not kernel-listed and cannot be invoked as `/skill-name` by the platform. Reach them via:
>
> ```bash
> aiwg discover "<capability>"
> aiwg show skill <name>
> ```
>
> Only kernel-listed skills (`aiwg-doctor`, `aiwg-refresh`, `aiwg-status`, `aiwg-help`, `use`, `steward`) are directly invokable as slash commands. See [skill-discovery rule](../../../addons/aiwg-utils/rules/skill-discovery.md).
# Deploy Generator
Generate production-ready deployment configurations based on project analysis.
## Research Foundation
**REF-001**: BP-8 - Containerized Deployment
> "Production-grade agentic workflows require containerized deployment with proper isolation, resource management, and orchestration."
## Usage
```bash
/deploy-gen docker [options]
/deploy-gen k8s [options]
/deploy-gen compose [options]
```
## Arguments
| Argument | Required | Description |
|----------|----------|-------------|
| type | Yes | Deployment type: docker, k8s, compose |
## Options
| Option | Default | Description |
|--------|---------|-------------|
| --output | ./deploy/ | Output directory for generated files |
| --app-name | (from package.json) | Application name |
| --port | 3000 | Application port |
| --multi-stage | true | Use multi-stage Dockerfile |
| --health-check | true | Include health check endpoints |
## Process
### 1. Project Analysis
Detect project characteristics:
```
Analyzing project...
- Runtime: [node/python/go/java]
- Package manager: [npm/yarn/pip/go mod]
- Entry point: [detected or ask]
- Dependencies: [count]
- Build required: [yes/no]
```
### 2. Template Selection
Choose appropriate templates based on analysis:
| Runtime | Template |
|---------|----------|
| Node.js | `templates/deploy/docker/node.Dockerfile` |
| Python | `templates/deploy/docker/python.Dockerfile` |
| Go | `templates/deploy/docker/go.Dockerfile` |
### 3. Configuration Generation
Generate deployment files with project-specific values.
## Output: Docker
```
deploy/
├── Dockerfile # Multi-stage build
├── .dockerignore # Exclude dev files
└── docker-build.sh # Build helper script
```
### Dockerfile Features
- Multi-stage build (build → production)
- Non-root user
- Health check
- Proper signal handling
- Layer caching optimization
## Output: Kubernetes
```
deploy/k8s/
├── deployment.yaml # Pod specification
├── service.yaml # Service exposure
├── configmap.yaml # Environment configuration
├── hpa.yaml # Horizontal Pod Autoscaler
└── kustomization.yaml # Kustomize base
```
### Kubernetes Features
- Resource limits and requests
- Liveness and readiness probes
- ConfigMap for environment
- HPA for auto-scaling
- Kustomize for environment overlays
## Output: Docker Compose
```
deploy/
├── docker-compose.yml # Service definition
├── docker-compose.dev.yml # Development overrides
└── .env.example # Environment template
```
## Examples
```bash
# Generate Dockerfile for Node.js project
/deploy-gen docker
# Generate full Kubernetes manifests
/deploy-gen k8s --app-name my-api --port 8080
# Generate Docker Compose for local development
/deploy-gen compose --output ./
# Generate all deployment types
/deploy-gen docker && /deploy-gen k8s && /deploy-gen compose
```
## Template Variables
Templates use these variables:
| Variable | Source |
|----------|--------|
| `{{APP_NAME}}` | --app-name or package.json |
| `{{PORT}}` | --port option |
| `{{NODE_VERSION}}` | .nvmrc or latest LTS |
| `{{PYTHON_VERSION}}` | .python-version or 3.11 |
| `{{ENTRY_POINT}}` | Detected from project |
## CLI Equivalent
```bash
aiwg deploy-gen <type> [options]
```
## Related Commands
- `project-health-check` - Analyze project before deployment
- `security-audit` - Security review before production
- `flow-deploy-to-production` - Full deployment workflow
## Success Metrics
From Unified Plan:
| Metric | Target |
|--------|--------|
| Zero to containerized | <2 minutes |
| Generated configs | Production-ready |
| Security baseline | Non-root, minimal image |
Generate deployment for: $ARGUMENTS
## References
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/README.md — aiwg-utils addon overview
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework context for deployment workflows
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference including deploy-related commands
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Analyze project before generating configs
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.