Start Astro creates a lean, static-first Astro website in the directory you already opened. It starts from Astro’s minimal scaffold, derives the visible project name from the folder, and overlays a complete but intentionally modest site foundation.
You get the pieces every small site needs on day one, without committing the project to a framework runtime or layers that have no real consumer yet.
The included experience
- Home, Work, Contact, and accessible animated 404 pages.
- A shared document layout with Header and Footer ownership kept clear.
- Central
SITEandROUTESconstants plus a consistent@/source alias. - A no-flash light and dark theme with an accessible toggle.
- Astro View Transitions and navigation behavior that survives page swaps.
- Seven local social icons and the bundled
gxb.otfbrand font. - Responsive, component-local styling with foundational tokens kept global.
Only @lucide/astro is added beyond Astro. Images, fonts, and icons stay local so the base does not depend on third-party asset hosts at runtime.
How it works
The skill scaffolds Astro’s current minimal template in place, then applies its maintained site files over that foundation. Generated package metadata, Astro configuration, Git and editor instructions, and favicons are preserved unless the requested site explicitly needs a change.
After the overlay, it installs the declared packages and requires a successful production build. The generated structure is documented so the next developer can see which layer owns layout, routes, theme behavior, and component styles.
Architecture guarantees
The output stays pure Astro and static by default: no adapter, server output, React island, or client framework runtime is introduced. Global CSS owns tokens and document foundations; each component owns the rest of its presentation.
Theme initialization happens before paint, respects saved preference and system preference, and remains compatible with view-transition navigation. Interactive controls retain keyboard focus, reduced-motion handling, and useful labels.
Deliberately absent
Start Astro does not pre-create content collections, API routes, services, stores, shared lib or types folders, Tailwind configuration, or placeholder application layers. Those structures are valuable only when the actual site earns them.
That restraint makes the generated site a clean starting point rather than a catalogue of guesses about its future.



