astro-security
Use when configuring Content Security Policy (CSP) in Astro 6, setting security headers, managing script/style hashes, using nonces, or implementing experimentalStaticHeaders for adapter deployments.
What this skill does
# Astro Security ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze existing security config, adapters, headers 2. **fuse-ai-pilot:research-expert** - Verify latest Astro 6 CSP docs via Context7/Exa 3. **mcp__context7__query-docs** - Check CSP compatibility with deployment adapter After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Enabling CSP in an Astro 6 project (stable in v6.0.0) - Configuring `security.csp` in `astro.config.mjs` - Adding SHA-256/384/512 hashes for external scripts or styles - Using nonces for dynamic script injection - Setting up `experimentalStaticHeaders` for adapter-based CSP headers ### CSP in Astro 6 Astro 6 ships Content Security Policy as a **stable** feature (previously experimental). When enabled: - Astro automatically generates SHA hashes for all bundled scripts and styles - Injects a `<meta http-equiv="content-security-policy">` in each page's `<head>` - Supports `script-src` and `style-src` directives by default **Limitations:** - Not supported in `dev` mode — test with `build` + `preview` - External scripts and styles require manual hash configuration - Incompatible with `<ClientRouter />` view transitions (use native View Transition API) - Shiki syntax highlighter (inline styles) not currently supported --- ## Reference Guide ### Concepts | Topic | Reference | When to Consult | |-------|-----------|-----------------| | CSP overview | [csp-overview.md](references/csp-overview.md) | Understanding CSP in Astro 6 | | Configuration | [csp-config.md](references/csp-config.md) | All config options | | Script directive | [script-directive.md](references/script-directive.md) | script-src configuration | | Style directive | [style-directive.md](references/style-directive.md) | style-src configuration | | Nonces | [nonces.md](references/nonces.md) | Dynamic script injection | | Static headers | [static-headers.md](references/static-headers.md) | Adapter-based CSP headers | ### Templates | Template | When to Use | |----------|-------------| | [csp-basic.md](references/templates/csp-basic.md) | Basic CSP enable with algorithm | | [csp-advanced.md](references/templates/csp-advanced.md) | Full config with directives + static headers | --- ## Best Practices 1. **Always test with build + preview** — CSP is inactive in dev mode 2. **Start with SHA-512** — strongest hash algorithm 3. **Use `'self'` explicitly** — not included by default in resources 4. **Hash external scripts manually** — compute SHA hashes for CDN resources 5. **Combine with adapter headers** — use `experimentalStaticHeaders` for Vercel/Netlify --- ## Forbidden - Testing CSP in `dev` mode (doesn't work — always use `build + preview`) - Using `<ClientRouter />` with CSP enabled - Forgetting to add `'self'` when using `resources` array - Adding `unsafe-inline` (defeats purpose of CSP)
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.