Menu
Build deep Astro documentation pages from a shared content module while keeping stable explicit routes
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Drive package defaults, release packaging, and website version display from one MSBuild property
Validate every meaningful workflow_dispatch input combination before approving release-pipeline changes
Keep mixed validation/release GitHub workflow dispatch inputs from misrouting validation runs
Validate NuGet release artifacts before publish and ensure both package and symbol payloads are release-correct
Ship an Astro docs site to GitHub Pages with SEO, validation, and custom-domain safety checks
Keep repo-local .NET sample apps zero-config by avoiding native apphosts when macOS integrity enforcement can kill them
| name | astro-reference-pages |
| description | Build deep Astro documentation pages from a shared content module while keeping stable explicit routes |
| domain | docs |
| confidence | high |
| source | earned |
Use this pattern when a docs-site needs many reference pages that share structure but still need explicit, linkable routes. It works well when the information architecture is already known and the main risk is duplication or broken internal linking.
/docs/commands/foo/, /analyzers/sf0001/) even if the content is rendered from shared data.docs-site/src/data/reference-content.ts) and keep page files thin.docs-site/src/components/reference/) to render repeated layouts like command contracts, filter pages, analyzer pages, and syntax-highlighted code blocks.cd docs-site && npm run build.docs-site/src/data/reference-content.tsdocs-site/src/components/reference/ReferenceCodeBlock.astrodocs-site/src/pages/docs/commands/*.astro, docs-site/src/pages/analyzers/*.astro