My pre-publish Audit prompt before i ship anything. (Please give me feedback on how to improve. I'm a total newbie). 🙏 Perform a complete PRE-PUBLISH AUDIT of the provided project (source code + build artifacts) and the site at the production URL (if available). The goal: confirm the app/website is ready for public deployment and produce an actionable, prioritized remediation plan and (where possible) PR-ready fixes. INPUT: - If available, use: production URL, staging URL, Git repo URL, build command, environment variables (redacted), and any test accounts. If any of these are not provided, test the production URL and the latest build artifacts you generated. SCOPE (run automated checks + manual checks where needed): 1. Functionality - Validate all pages, navigation, and flows (signup, login, password reset, SSO, onboarding, payment flows, contact/support). - Verify forms: client & server validation, error states, spam protection (CAPTCHA/recaptcha), and successful submission. - Check all external integrations: payment providers, email delivery, analytics, and third-party APIs (authentic test calls if secrets/test keys are provided). 2. Broken links & routing - Crawl the whole site (all internal links, anchor links, images, scripts) and report 4xx/5xx and redirect loops. - Confirm friendly 404 and proper redirects (301 vs 302). - Ensure canonicalization (single canonical URL per page). 3. Performance & Core Web Vitals - Run Lighthouse (headless) and report: Performance, Accessibility, Best Practices, SEO, PWA scores. - Measure Core Web Vitals: LCP, CLS, INP/FID, TTFB. - Detect large assets (>200KB) — images, fonts, JS bundles. Check code-splitting and unused JS/CSS. - Verify image optimization: responsive images (srcset), modern formats (WebP/AVIF), width/height attributes, lazy-loading. - Recommend CDN usage, compression (Brotli/gzip), caching headers, preconnect/preload for critical resources. 4. Accessibility (A11Y) - Run automated accessibility audits (axe/pa11y) and manual checks for: