astro-website-builder

Builds Astro content-first websites with shared layouts, content collections, and publication checks.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill astro-website-builder-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: astro-website-builder
Source: https://github.com/oxie/prime-agent-skills/tree/main/astro-website-builder
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill astro-website-builder-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an agreed site plan into working Astro pages often leads to scaffolded boilerplate, invented content, broken publication rules, and unverified output. This Skill guides the implementation of explicitly selected Astro content sites so routes, layouts, collections, and metadata stay consistent and verifiable. ## Core Features & Use Cases - Shared layout and route implementation: Build one complete route with a typed layout/head contract, navigation, and real content before repeating the shell across requested pages. - Content collections and publication rules: Configure Astro 5/6 Content Layer schemas, glob loaders, draft/date predicates, and keep lists, feeds, and sitemaps consuming one shared published selection. - Page delivery and verification: Handle metadata, image ownership, islands hydration, native form behavior, and run the project's own authorized checks before reporting results. - Use Case: A user asks for an Astro blog with draft filtering and an RSS feed; the Skill guides building the collection schema, a single publication predicate, static routes, and output inspection proving drafts never reach emitted HTML or feeds. ## Quick Start Ask the agent to build the requested Astro pages for your site using the astro-website-builder skill, starting from your existing project setup.

Frequently Asked Questions about astro-website-builder

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

FAQPage Schema
How do I build an Astro content website with collections?▼

Define collections in src/content.config.ts using defineCollection, a glob loader, and a Zod schema from astro/zod. Then create static routes with getStaticPaths that consume a shared, publication-filtered selection of entries.

How do I filter drafts and scheduled posts in Astro?▼

Use one shared predicate checking an explicit draft flag and a publishAt date against a single build-time cutoff. Apply that same filtered selection to list pages, static paths, RSS, and sitemap sources so drafts never reach any public surface.

Does this skill work with both Astro 5 and Astro 6?▼

Yes, the worked contract covers Astro 5 and 6 Content Layer. Both export z from astro/zod, but Zod 3 versus 4 behavior differs, so version-specific transforms should not be carried across the boundary.

Can this skill deploy my Astro site or set up a database?▼

No. It is Markdown guidance only and explicitly excludes deployment, cloud provisioning, auth, database setup, and image generation. Those remain separate authorized tasks with their own tested contracts.

Why does my Astro build succeed but drafts still appear on the site?▼

A successful build does not prove publication policy. Filtering only the index page leaves draft routes emitted; verify the draft URL and unique body markers are absent from final HTML, feeds, and search data.