update-starlight-docs

Updates Astro Starlight user documentation pages to reflect code changes affecting user-facing features.

37|4|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill update-starlight-docs-jmrplens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update-starlight-docs
Source: https://github.com/jmrplens/gitlab-mcp-server/tree/main/.github/skills/update-starlight-docs
Command: npx skills add https://github.com/jmrplens/gitlab-mcp-server --skill update-starlight-docs-jmrplens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes that affect user-facing features often leave documentation stale. This Skill guides the systematic update of an Astro Starlight documentation site so that new tools, configuration options, capabilities, and deployment changes are accurately reflected in both English and Spanish user docs. ## Core Features & Use Cases - Change-to-page mapping: Maps code changes (new MCP tools, config options, transports, security changes) to the specific Starlight doc pages that need updates. - Bilingual EN/ES synchronization: Ensures every English page under site/src/content/docs/ has a mirrored, translated Spanish counterpart under es/. - Starlight conventions enforcement: Covers frontmatter requirements (title, description, chips, datePublished, faq), sidebar registration in astro.config.mjs, and proper use of Starlight components like Aside, Tabs, Steps, and CardGrid. - Use Case: After adding a new MCP tool to the GitLab MCP server, use this Skill to update the tools overview page, add translations, register any new page in the sidebar, and verify the site builds with zero errors. ## Quick Start Update the Starlight user docs to reflect the new configuration option I just added, including the Spanish translations, and verify the site builds successfully.

Frequently Asked Questions about update-starlight-docs

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

FAQPage Schema
How do I update Astro Starlight docs after a code change?

First map the code change to affected pages, then edit the English MDX pages under site/src/content/docs/, mirror the changes in the es/ folder with translated content, and verify with cd site && pnpm run build producing zero errors.

How do I add a new page to a Starlight documentation site?

Create the MDX file with title and description frontmatter, then register it in the sidebar array of site/astro.config.mjs with a slug, label, and translations.es label. Also create the Spanish mirror page under the es/ directory.

Does Starlight support multilingual documentation sites?

Yes, Starlight supports i18n through locale folders. English is the root locale living directly under site/src/content/docs/, while Spanish pages mirror the same structure under site/src/content/docs/es/ with fully translated content.

What frontmatter fields do Starlight MDX pages require?

Every MDX page requires title and description fields. Existing pages in this site also carry chips, datePublished, and faq fields that the site's checks read, so copy the frontmatter shape of a neighbouring page when creating new content.

Why does my Starlight site build fail after editing docs?

Builds commonly fail from missing component imports, broken internal links, or i18n parity issues between locales. Run cd site && pnpm run build and pnpm run lint to catch link, accessibility, and translation parity errors.