Ask Claude to Scaffold an Astro Site from Your Content Structure
Astro ships zero JavaScript by default — perfect for content-heavy sites. But wiring up content collections, layouts, and dynamic routes still takes time. Let Claude do the scaffolding.
Scaffold an Astro 4 blog site. I want a content collection for blog posts with frontmatter: title, date, tags, and description. Generate an index page that lists posts sorted by date, a [slug].astro dynamic route for individual posts, and a tag filtering page.
Claude generates a complete project structure with typed content collections, a Zod config schema, and the correct getStaticPaths calls for fully static output:
// src/content/config.ts
const blog = defineCollection({
type: 'content',
schema: z.object({
title: z.string(),
date: z.coerce.date(),
tags: z.array(z.string()),
description: z.string(),
}),
});
export const collections = { blog };
From there, extend the site without fighting Astro's internals:
Add an RSS feed at /rss.xml, an auto-generated sitemap, and syntax highlighting for code blocks using Shiki with the github-dark theme.
You can also ask Claude to add an @astrojs/image integration for optimised images, a view transitions API for animated page changes, or React/Svelte islands for any interactive components.
Get a fast, typed content site running before you write a single word of copy.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.