What problem does it solve? Deploying and operating web services on Render involves many platform-specific behaviors—PORT binding, TLS termination at the edge, health check gating, custom domain DNS, and zero-downtime deploy rules—that cause failed deploys and misconfigurations when misunderstood. ## Core Features & Use Cases - Port and TLS Configuration: Explains binding to 0.0.0.0 on the PORT variable, reserved ports, multi-port private listeners, and edge TLS termination. - Health Checks and Deploy Lifecycle: Covers healthCheckPath requirements, pre-deploy commands for migrations, zero-downtime swaps, drain behavior with maxShutdownDelaySeconds, and rollbacks. - Domains, Disks, and Auto-Deploy: Details CNAME/apex/wildcard DNS setup, persistent disk constraints (single instance, no zero-downtime), autoDeployTrigger modes, and PR previews. - Use Case: A deploy succeeds in the Render Dashboard but never takes traffic—use this Skill to diagnose that the health check path returns 404 or the app binds to 127.0.0.1 instead of 0.0.0.0. ## Quick Start Ask the assistant to configure a Render web service with a health check endpoint and a custom domain, or to troubleshoot why a deploy is not going live.