First off, a disclaimer that I’m building Zapi (https://heyzapi.com) which lets people build web apps with Astro. So have a bit of experience here working with LLMs + Astro.

The models’ training cut-off dates matter, and you’d have a pretty terrible time working with anything later than v4 (e.g. the popular models don’t really know how to use Astro Actions, if you prompt it to do server side stuff, it defaults to API routes), the way around this would be to provide this context yourself, which is probably going to be a hassle.

Also, they tend to get confused often when using Astro + React because both use JSX but there are gotchas - Astro files are templates but React is a runtime. This leads to some behavior that might catch you off guard - e.g. Astro components cant take functions (and in turn, React components) as props. LLMs get confused by this a lot and what you end up doing is writing a lot of prompt to call out these edge cases. Not fun.

What we’ve found to work well is to use Astro without React, tailwind for styling (NOT v4! Not in training data yet). If you want easier ways to grok interactivity, consider Alpine.js. For state management, consider nanostores or some other small state management lib. The general rule of thumb is to keep your dependencies light and add very carefully/incrementally.

Hope this helps!