What problem does it solve? Custom domains on Azure Static Web Apps fail in non-obvious ways: the binding shows Ready but DNS still points to the old host, apex domains reject CNAME records, SVCB records silently do nothing, and a green CI deploy can hide a missing deployment token. This Skill captures the diagnostic steps and fixes for these failures. ## Core Features & Use Cases - DNS diagnosis: Distinguish validation records (TXT _dnsauth) from routing records (A/ALIAS/CNAME), verify with dig and DoH queries, and detect apex constraints like MX records blocking root CNAMEs. - Terraform management: Import portal-created azurerm_static_web_app_custom_domain bindings safely, handle the provider read gap with lifecycle { ignore_changes = [validation_type] }, and fix mocked-plan test failures. - Deployment troubleshooting: Identify when the SWA placeholder page means no deployment ever happened (builds API WaitingForDeployment, skipped deploy steps exiting 0 via SKIP_DEPLOY_ON_MISSING_SECRETS). - Use Case: A custom domain shows the SWA placeholder despite a Ready binding — trace the evidence chain from DNS to the builds API to the GitHub Actions deploy log to find the missing token. ## Quick Start Diagnose why my Azure Static Web Apps custom domain shows the placeholder page even though the binding status is Ready.