What problem does it solve? Setting up Content Security Policy in Astro requires manually computing SHA hashes for external scripts, choosing the right directives, and wiring adapter-based headers — a process prone to misconfiguration that either breaks the site or leaves it unprotected. ## Core Features & Use Cases - Automatic CSP Configuration: Enables security.csp in astro.config.mjs with SHA-256/384/512 hash generation for bundled scripts and styles. - External Resource Handling: Guides manual hash computation for CDN scripts and styles, plus nonce setup for dynamic script injection in SSR mode. - Adapter-Based Headers: Configures experimentalStaticHeaders for Vercel and Netlify to deliver CSP via HTTP headers instead of meta tags. - Use Case: You are deploying an Astro site to Vercel with Google Analytics and Google Fonts. Use this Skill to configure script-src and style-src directives with the correct hashes and resources, then verify no CSP violations appear in the production build. ## Quick Start Configure Content Security Policy in my Astro project with SHA-512 hashing and set up the Vercel adapter to emit CSP as HTTP headers.