astro-knowledge-patch

Update Astro code for versions 5.16 through 6.0 compatibility.

22|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill astro-knowledge-patch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro-knowledge-patch
Source: https://github.com/Nevaberry/nevaberry-plugins/tree/main/plugins/astro-knowledge-patch/skills/astro-knowledge-patch
Command: npx skills add https://github.com/Nevaberry/nevaberry-plugins --skill astro-knowledge-patch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This knowledge patch fills gaps between model training cutoffs and real-world Astro changes so developers and AI assistants avoid generating deprecated patterns, broken APIs, or incompatible configurations when working with Astro projects.

Core Features & Use Cases

  • Breaking changes & migration guidance: Notes on Node 22 minimum, removed APIs, Zod 4 migration, and upgraded dependencies (Vite 7, Shiki 4).
  • Content and caching updates: Live collections, retainBody behavior, and experimental route caching guidance for SSR and API routes.
  • Fonts, assets, and security: Built-in Fonts API, experimental SVGO, image background handling, and Content Security Policy configuration with auto-generated hashes.
  • Use Case: Audit or update an existing Astro codebase or generated code to ensure compatibility with Astro 5.16–6.0, including dependency bumps and configuration changes.

Quick Start

Load the astro-knowledge-patch and update or validate Astro code for compatibility with versions 5.16 through 6.0, focusing on Node 22, the Fonts API, live collections, CSP, route caching, and dependency upgrades.

Frequently Asked Questions about astro-knowledge-patch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate my Astro project to Node 22 and Zod 4 compatibility?

Astro migration to Node 22 and Zod 4 requires updating deprecated APIs and bumping dependencies. This patch provides specific breaking change notes and migration guidance to ensure your Astro 5.16–6.0 codebase remains compatible without generating deprecated patterns.

How does the Astro Fonts API work for local and remote font integration?

The Astro Fonts API provides built-in font management for local and remote sources. This knowledge patch supplies updated integration details to help you configure fonts correctly in Astro 5.16–6.0 and avoid generating broken API configurations.

Does Astro 6.0 support live collections and experimental route caching for SSR?

Astro 6.0 supports live collections and experimental route caching for SSR and API routes. This patch covers retainBody behavior and caching guidance, ensuring your content layer and SSR routes function correctly with the latest framework updates.

What is the best way to configure Content Security Policy with auto-generated hashes in Astro?

Configuring CSP in Astro 6.0 involves auto-generated hashes for script and style tags. This patch delivers the updated CSP configuration details needed to secure your Astro project and prevent AI assistants from generating incompatible security policies.

Why does my Astro project break after upgrading Vite 7 and Shiki 4 dependencies?

Upgrading Vite 7 and Shiki 4 in Astro projects can introduce breaking changes and incompatible configurations. This knowledge patch provides dependency upgrade notes and migration steps to validate your code against Astro 5.16–6.0 expectations.

Astro dependency upgrade not working with deprecated APIs, what are the limitations?

Astro dependency upgrades fail when deprecated APIs and incompatible configurations persist in your codebase. This patch identifies removed APIs and provides validation steps to ensure full compatibility with Astro 5.16–6.0, including Node 22 runtime requirements.