القائمة
Astro Starlight documentation framework — setup, sidebar navigation, frontmatter, built-in components, asides, theming, i18n, search
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate repository wiki pages mapping architecture, specs, and status. Trigger: orchestrator launches sdd-document.
Shared SDD references for installed skills. Not invokable.
Read-only generalist screening contract for selective 4R review.
Read-only targeted correction validator for a bounded review lineage.
Write SDD delta specs with requirements and scenarios. Trigger: orchestrator launches spec work for a change.
Create pull requests with branch, validation, and publication checks. Trigger: creating, opening, or preparing PRs for review.
| name | stack-starlight |
| description | Astro Starlight documentation framework — setup, sidebar navigation, frontmatter, built-in components, asides, theming, i18n, search |
| license | Apache-2.0 |
| metadata | {"author":"manuel-retamozo-garcia","version":"1.0"} |
| capabilities | ["starlight"] |
Documentation-site patterns for Starlight (Astro) projects. Covers project setup, astro.config.mjs configuration, sidebar navigation, page frontmatter, built-in components, Markdown authoring extensions, theming, and i18n.
npm create astro@latest -- --template starlight)starlight() integration in astro.config.mjssrc/content/docs/ (frontmatter, asides, code blocks)<StarlightPage> or overriding UI components--sl-* CSS custom properties) or setting up i18nsrc/content/docs/; folders become URL segments. Every page MUST have title in frontmatter — the schema validates and fails the build without it.starlight({ ... }) integration inside astro.config.mjs. title is required; set Astro's site to enable sitemap generation.autogenerate: { directory } per section over hand-listing slugs; control order/label/visibility per page with the sidebar frontmatter field (order, label, hidden, badge).@astrojs/starlight/components and only work in .mdx (or Markdoc {% %} tags). Plain .md supports asides (:::note … :::) and Expressive Code markers — do not put JSX in .md.src/pages/*.astro wrapped in <StarlightPage frontmatter={{ title }}>; to change built-in UI use the components config override map — never copy/patch theme internals.customCss files overriding --sl-* custom properties (colors, --sl-font); use logo.light/logo.dark for theme-aware logos. Apply not-content class to opt elements out of content styling.pagefind: false and keep it out of production builds with draft: true.locales/defaultLocale in config; mirror content per locale directory. Untranslated pages fall back to the default locale automatically; translate sidebar labels with translations.For full configuration options, frontmatter fields, component catalog, and code examples, refer to: