🚀 Core Philosophy: Software is not real until it is running in production for real users.
When to use
Use this skill when writing Dockerfiles, configuring GitHub Actions or GitLab CI configs, managing static assets, caching configurations on CDN Edge (Stale-While-Revalidate), designing zero-downtime deployments (Blue-Green, Canary), and executing zero-downtime database migrations.
When not to use
Do not use this skill for frontend UI state logic, visual theme layout, or unit test mock designs.
Trigger cues
- Key terms: deployment, Dockerfile, docker-compose, CI/CD, GitHub Actions, Vercel, Netlify, CDN, canary, blue-green, database migration, zero-downtime, pipeline, multi-stage build, container, edge routing.
- Writing CI pipelines, Docker config, CDN caching config, or coordinating schema migrations with code updates.
Routing boundary
- Primary for deployment automation, containerization, release patterns, environment variables (12-factor), and edge assets optimization.
- Secondary to
developer-web-performance for in-app bundle optimization.
Inputs required
- Target deployment infrastructure (e.g., AWS, Railway, Vercel, Kubernetes)
- DB migration requirements and rollback targets
- Source of truth:
references/source.md
Instructions
- Detect Stack: Inspect the workspace files to identify the project's existing build, host, and deployment configurations (e.g., GitHub Actions, Vercel, AWS, Docker, Kubernetes, Terraform, Prisma migrations).
- Do Not Migrate: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.
- Read references/source.md to understand continuous delivery and distributed container deployment.
- Design pipeline operations and deployment targets matching the existing hosting tooling.
- Establish environment configurations according to 12-factor app guidelines.
- Implement zero-downtime deployment strategies (Blue-Green or Canary) appropriate to the infrastructure.
- Orchestrate zero-downtime database migrations using the Expand-and-Contract (Parallel Run) pattern.
Output format
- Primary decision/output: CI/CD configuration files, Dockerfiles, and migration scripts.
- Summary: One-paragraph overview of the release and pipeline plan.
- Actions: Verification checklist for build speed, container security, and migration safety.
1---2name: web-deployment-rules3description: Trigger: deployment pipeline, CI CD, Docker builds, DB migrations, expand contract database, Netlify. Scope: Application deployment, multi-stage builds, zero-downtime releases. Boundary: Excludes local editor settings.4---56# 🚀 Core Philosophy: Software is not real until it is running in production for real users.78## When to use910Use this skill when writing Dockerfiles, configuring GitHub Actions or GitLab CI configs, managing static assets, caching configurations on CDN Edge (Stale-While-Revalidate), designing zero-downtime deployments (Blue-Green, Canary), and executing zero-downtime database migrations.1112## When not to use1314Do not use this skill for frontend UI state logic, visual theme layout, or unit test mock designs.1516## Trigger cues1718- Key terms: deployment, Dockerfile, docker-compose, CI/CD, GitHub Actions, Vercel, Netlify, CDN, canary, blue-green, database migration, zero-downtime, pipeline, multi-stage build, container, edge routing.19- Writing CI pipelines, Docker config, CDN caching config, or coordinating schema migrations with code updates.2021## Routing boundary2223- Primary for deployment automation, containerization, release patterns, environment variables (12-factor), and edge assets optimization.24- Secondary to `developer-web-performance` for in-app bundle optimization.2526## Inputs required2728- Target deployment infrastructure (e.g., AWS, Railway, Vercel, Kubernetes)29- DB migration requirements and rollback targets30- Source of truth: `references/source.md`3132## Instructions33341. **Detect Stack**: Inspect the workspace files to identify the project's existing build, host, and deployment configurations (e.g., GitHub Actions, Vercel, AWS, Docker, Kubernetes, Terraform, Prisma migrations).352. **Do Not Migrate**: Never propose or force a technology stack change. Apply the principles in this skill using the project's current tooling.363. Read [references/source.md](references/source.md) to understand continuous delivery and distributed container deployment.374. Design pipeline operations and deployment targets matching the existing hosting tooling.385. Establish environment configurations according to 12-factor app guidelines.396. Implement zero-downtime deployment strategies (Blue-Green or Canary) appropriate to the infrastructure.407. Orchestrate zero-downtime database migrations using the Expand-and-Contract (Parallel Run) pattern.4142## Output format4344- Primary decision/output: CI/CD configuration files, Dockerfiles, and migration scripts.45- Summary: One-paragraph overview of the release and pipeline plan.46- Actions: Verification checklist for build speed, container security, and migration safety.
coreyone