Prompt to Build an Astro Static SEO Site

Copy-paste prompt for scaffolding a fully optimized Astro static site with content collections, sitemap, og-images, and TypeScript.

Give this to your agent to scaffold a production-ready Astro static site with content collections, Tailwind v4, SEO meta, sitemap, and per-page OG images — without it inventing incompatible integrations or skipping canonical tags.

Main Prompt

You are scaffolding a new Astro static site. Use Astro 5, TypeScript strict mode,
and Tailwind CSS v4 (via @tailwindcss/vite — NOT the legacy @astrojs/tailwind integration).

Requirements:
- Initialize with `bun create astro@latest` defaults, then layer in:
  - A `src/content/blog/` collection with a Zod schema (title, description, pubDate, tags).
  - A shared `<BaseLayout>` with `<head>` containing: canonical URL, og:title, og:description,
    og:image (per-page), twitter:card, and the Astro `<ViewTransitions />` component.
  - `@astrojs/sitemap` integration configured with `customPages` for any dynamic routes.
  - A `public/robots.txt` that disallows `/api/` and allows everything else.
  - A `/blog/[slug].astro` dynamic route that renders MDX blog posts.
  - A `/tags/[tag].astro` route that filters posts by tag.
  - Tailwind applied globally via `src/styles/global.css` imported in BaseLayout.
- All components must be `.astro` — no React unless explicitly asked.
- Export a typed `getStaticPaths` for every dynamic route.
- Do NOT install `@astrojs/react`, `next`, or any SSR adapter — this is a static build.

Stop after listing all files you plan to create or modify. Wait for my approval before writing any code.

Implementation Notes

Astro 5 content collections use defineCollection in src/content.config.ts, not the old src/content/config.ts path — confirm the agent uses the correct location.
Tailwind v4 ships as a Vite plugin; the old astro.config.ts integrations: [tailwind()] pattern is obsolete and will cause a runtime error.
getStaticPaths must return { params, props } objects; the agent sometimes returns bare strings.

Expected File Changes

astro.config.ts                          (new)
src/content.config.ts                    (new)
src/layouts/BaseLayout.astro             (new)
src/pages/index.astro                    (new)
src/pages/blog/[slug].astro              (new)
src/pages/tags/[tag].astro              (new)
src/styles/global.css                    (new)
public/robots.txt                        (new)
package.json                             (edited)
tsconfig.json                            (edited)

Acceptance Criteria

bun run build exits 0 with no type errors.
Each blog post page includes a unique canonical URL and og:image in the rendered HTML.
/sitemap-index.xml is generated and contains all blog post URLs.
/robots.txt exists and disallows /api/.

Test Commands

bun run build
bun run preview
curl -s http://localhost:4321/sitemap-index.xml | grep '<loc>'
curl -s http://localhost:4321/robots.txt
bun run typecheck

Common AI Mistakes

Installing the deprecated @astrojs/tailwind instead of @tailwindcss/vite.
Placing content.config.ts at src/content/config.ts (old Astro 4 path).
Forgetting to call getCollection('blog') inside getStaticPaths — returning an empty array.
Adding output: 'server' to astro.config.ts, which breaks static export.

Fix Prompt

The build failed. Check for these issues in order:
1. Tailwind: remove `@astrojs/tailwind` from integrations and add `@tailwindcss/vite` to the
   `vite.plugins` array in astro.config.ts.
2. Content config: the file must be at `src/content.config.ts` (not `src/content/config.ts`).
3. `getStaticPaths`: each entry must be `{ params: { slug }, props: { post } }`.
Fix only the broken items. Show me the corrected diff.