astro-starlight

Guide Astro and Starlight site development with version-aligned configuration and build validation.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill astro-starlight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: astro-starlight
Source: https://github.com/Mikeys-Tech-Lab/poc/tree/main/.cursor/skills/astro-starlight
Command: npx skills add https://github.com/Mikeys-Tech-Lab/poc --skill astro-starlight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents Astro + Starlight docs work from drifting into mismatched versions, broken content structure, and theme/config pitfalls by enforcing workspace-specific boundaries and build-safe practices.

Core Features & Use Cases

  • Guided Astro/Starlight scaffolding: Use consistent workspace conventions when iterating on the site under apps/site/.
  • Content and register boundaries: Keep practitioner docs, register content, and assets in their intended trees without leaking development-only seeds into public pages.
  • Theming and build verification: Apply Catppuccin theming correctly, avoid frontmatter asset-path mistakes, and verify changes with a passing pnpm run build.

Quick Start

Tell the AI to guide you through scaffolding or updating a page in apps/site/ while checking register placement, locale structure (en-us), and theming constraints, then ensure the result passes pnpm run build.

Frequently Asked Questions about astro-starlight

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

FAQPage Schema
How do I configure Starlight theming without breaking my Astro docs build?

To configure Starlight theming safely, apply customizations like Catppuccin themes within apps/site/ and verify changes with pnpm run build to prevent frontmatter asset-path mistakes.

How do I structure content correctly when adding pages to an Astro Starlight documentation site?

Structure Starlight documentation content by placing practitioner docs and register content in their designated trees within apps/site/ to prevent leaking development-only seeds into public pages.

Why does my Astro Starlight dev-server fail after updating documentation pages?

Your Astro Starlight dev-server may fail due to mismatched versions, incorrect content tree placement, or frontmatter image path aliasing pitfalls, requiring a passing pnpm run build to validate fixes.

What is the best way to scaffold an Astro Starlight site in an existing monorepo?

The best way to scaffold an Astro Starlight site is by enforcing workspace-specific boundaries, version-aligned configuration, and locale structure within apps/site/ before validating the build.

Do I need to run a build verification before committing Astro Starlight configuration changes?

Yes, you need to run pnpm run build before committing Astro Starlight changes to catch theming errors, ensure safe content architecture, and verify version-aligned configuration without breaking the dev-server.