Set up deploy notifications so I always know when code ships and whether it worked. 1. Platform hooks: check my hosting platform's built-in notifications (Vercel, Netlify, Fly.io, Render, Railway all have Slack/email/webhook integrations) and configure deploy success and failure notifications to a Slack channel or email I actively monitor. 2. CI hooks: if my deploys run through CI (GitHub Actions or similar), add notification steps to the workflow: on deploy start, on success (with the deployed commit SHA and a link), and on failure (with the failing step and a link to logs). 3. Custom webhook: if my platform has no native integration, add a deploy webhook: a curl at the end of my deploy script hitting a Slack incoming webhook or email service, with success/failure branches. 4. Signal quality: include the useful facts per notification: environment (staging vs production), commit SHA and message, who/what triggered it, and duration. Keep it one message, not a thread of spam. 5. Failure amplification: for production deploy failures specifically, make the notification loud (mention me or use a distinct channel) since a failed deploy often means the site is in a partial or rolled-back state that needs eyes. 6. Pair with smoke tests: if I have post-deploy smoke tests, their failure should notify through the same channel so a 'successful' deploy that broke the site still pages me. Do not notify on every preview/branch deploy; production and staging only, or it becomes noise I learn to ignore. Do not put secrets in the notification payloads. Give me: the configured integrations or workflow changes, a sample notification per event type, and confirmation by triggering a test deploy.