DevOps Guidelines

Deployment strategy

Rolling (default): gradual, zero-downtime replacement.
Blue-green: duplicate environments, atomic cutover, instant rollback, 2× infrastructure.
Canary: route a small percentage first; requires traffic splitting.

Docker

Pin specific base-image tags (for example node:22-alpine); NEVER use :latest.
Use multi-stage builds and a non-root user. Copy dependencies first for caching.
.dockerignore: node_modules, .git, tests. Define HEALTHCHECK and resource limits.

Kubernetes

Configure startup, readiness, and liveness probes with workload-appropriate initial delays and thresholds.

CI/CD

PR: lint → typecheck → unit → integration → preview.
Main: build → staging → smoke → production.

Health and shutdown

Simple: GET /health → { "status": "ok" }.
Detailed: dependencies, uptime, version.
Services MUST expose meaningful health and gracefully handle SIGTERM when the workload requires it.

Configuration

Use environment variables (Twelve-Factor), separated by environment. Validate at startup and fail fast. NEVER commit secrets or hard-code NODE_ENV=production.

Rollback

Kubernetes: kubectl rollout undo. Vercel: vercel rollback. Docker: redeploy the previous pinned image.

Feature Flags

Lifecycle: create → enable → 5% → 25% → 50% → 100% → remove flag and dead code.
Every flag MUST have an owner, expiration, and rollback trigger. Remove within two weeks.

Checklists

Pre-deploy, when applicable: passing tests, code review, environment variables, migrations, rollback plan.
Post-deploy services: healthy, monitored, old pods terminated, outcome documented.
Production services: passing tests; no hardcoded secrets; JSON logs; meaningful health; pinned versions; validated environment variables; resource limits; TLS; CVE scan; CORS; rate limiting; CSP/HSTS/X-Frame-Options; tested rollback; runbook; on-call.
Apply security/CVE checks to executable or security-sensitive workloads.

Mobile Deployment

EAS: eas build:configure; eas build -p ios|android --profile preview; eas update --branch production; --auto-submit.
Fastlane: iOS match/cert/sigh/pilot; Android Gradle/supply.
Keep credentials in environment/secret storage, never Git. Automate iOS development/distribution signing with fastlane match; use keytool and Google Play App Signing for Android.
TestFlight: internal instant; external 90 days/100 testers. Google Play: internal/beta/production. Expect 1–7 days for review.
Rollback: EAS eas update:rollback; native release → revert build; store release → reduce phased rollout.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

92

Quality

80

Clarity

85

Completeness

75

Summary

A comprehensive reference guide for DevOps best practices covering deployment strategies (rolling, blue-green, canary), containerization (Docker/Kubernetes), CI/CD pipelines, health checks, configuration management, and mobile release workflows. The skill provides checklists and patterns for production readiness, rollback procedures, and feature flag lifecycle management.

Detected Capabilities

guidance-onlyno-file-writesno-shell-executionno-credentials-accessreference-documentation

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

design deployment strategysetup docker kubernetesconfigure ci/cd pipelinemobile app releaseproduction readiness checklistimplement feature flagsplan rollback strategyhealth check setupinfrastructure review

Use Cases

Design a rolling deployment strategy for zero-downtime releases
Set up Docker multi-stage builds with health checks and resource limits
Configure Kubernetes startup, readiness, and liveness probes
Structure CI/CD pipelines (PR → main branch flows)
Implement feature flags with lifecycle management and rollback triggers
Build production readiness checklists (secrets, monitoring, TLS, CVE scans)
Automate mobile releases via EAS Build or Fastlane
Plan and execute safe rollbacks across infrastructure platforms
Document pre-deploy and post-deploy verification steps

Quality Notes

Well-structured reference with clear section hierarchy (strategy, Docker, Kubernetes, CI/CD, health, configuration, rollback, feature flags, checklists)
Explicitly discourages dangerous practices: NEVER use :latest Docker tags, NEVER hardcode NODE_ENV or secrets, NEVER commit secrets to Git
Comprehensive production readiness checklists include security concerns (TLS, CVE scans, CORS, CSP, HSTS, X-Frame-Options)
Feature flag guidance includes lifecycle, ownership, and expiration — prevents flag sprawl
Provides specific platform commands (kubectl, Vercel, EAS, Fastlane) for common operations
Mobile deployment section covers both iOS (TestFlight, match, pilot) and Android (Google Play, keytool) with credential management guardrails
Clear guidance on health check patterns (simple vs. detailed) and graceful shutdown (SIGTERM handling)
Concise format works as reference material — bullet points make it scannable without excessive verbosity

Model: claude-haiku-4-5-20251001Analyzed: Aug 18, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

gem-devops-guidelines