Rspress Description Generator

rstackjs/agent-skills/skills/rspress-description-generator

作者 rstackjs2966acbef746無授權條款95 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫今天更新

Generate missing description frontmatter for Rspress Markdown/MDX pages, including new docs pages and site-wide SEO metadata updates.

僅含說明AI & Agents
AI 產生的概覽

為 Rspress 的 Markdown 與 MDX 文件頁面產生缺少的 description frontmatter。

功能
此技能會從設定檔中找出 Rspress 文件根目錄,辨識 i18n 語言子目錄,並掃描 Markdown 與 MDX 頁面中缺少的 description frontmatter。它會將 50 至 160 字元的純文字描述寫入頁面 frontmatter,語言與內容一致,首頁則依 hero 欄位產生。它也涵蓋批次處理以及最後重新掃描以找出遺漏的檔案。
適用情境
當 Rspress 文件網站有缺少 description frontmatter 的頁面,或新增文件頁面需要 SEO 與社群預覽中繼資料時使用。它適合單一語言或 i18n 文件專案的全站中繼資料更新。
執行需求
需要存取 Rspress 專案的設定檔與文件目錄;不附帶指令碼,僅提供說明。不需要網路存取,但文件中連結了外部 Rspress 文件。

Rspress description generator

The description field in Rspress frontmatter generates <meta name="description" content="..."> tags, which are used for search engine snippets, social media previews, and AI-oriented formats like llms.txt.

Step 1 — locate the docs root

  1. Find the Rspress config file. Search for rspress.config.ts, .js, .mjs, or .cjs. It may be at the project root or inside a subdirectory like website/.
  2. Read the config and extract the root option.
    • The value might be a plain string (root: 'docs') or a JS expression (root: path.join(__dirname, 'docs')). In either case, determine the resolved directory path.
    • If root is set, resolve it relative to the config file's directory.
    • If root is not set, default to docs relative to the config file's directory.
  3. Confirm the directory exists. If neither docs nor the configured root exists, check for doc as a fallback.

Step 2 — detect i18n structure

Rspress i18n projects place language subdirectories (e.g., en/, zh/) directly under the docs root:

docs/├── en/│   ├── guide/│   └── index.md└── zh/    ├── guide/    └── index.md

Check if the docs root contains language subdirectories (two-letter codes like en, zh, ja, ko, etc.). If so, process each language directory separately — the description language should match the content language.

If there are no language subdirectories, treat the entire docs root as a single-language site.

Step 3 — scan and process files

Glob for **/*.md and **/*.mdx under the docs root. Exclude:

  • node_modules, build output (doc_build, .rspress, dist)
  • _meta.json / _nav.json (sidebar/nav config files, not doc pages)
  • **/shared/** directories (reusable snippets included via @import, not standalone pages)

For each file:

  1. Read the file.
  2. Check for existing description in frontmatter. If it exists and is non-empty, skip.
  3. Check pageType in frontmatter. For home pages, derive the description from the hero.text / hero.tagline fields or the features list, not from body content.
  4. Generate a description following the writing guidelines below.
  5. Insert description into frontmatter:
    • If the file has frontmatter with a title field, insert description on the line after title.

    • If the file has frontmatter without title, insert description as the first field.

    • If the file has no frontmatter block, add one:

      yaml
      ---description: Your generated description here---

YAML formatting

Most descriptions can be bare YAML strings:

yaml
description: Step-by-step guide to setting up your first Rspress site

If the description contains colons, quotes, or other special YAML characters, wrap in double quotes:

yaml
description: 'API reference for Rspress configuration: plugins, themes, and build options'

Step 4 — batch processing

For sites with many files, use parallel agent calls to process independent files simultaneously. Group by directory (e.g., all files in guide/, then all in api/) to maintain focus and consistency within each section.

After processing all files, do a quick scan to ensure no files were missed — re-glob and check for any remaining files without description.

Description writing guidelines

The description serves three audiences: search engines (Google snippet), AI systems (llms.txt, summarization), and humans (scanning search results). A good description helps all three.

Rules

  • Length: 50–160 characters. Under 50 is too vague for search engines; over 160 gets truncated in snippets.
  • Language: Match the document content. Chinese docs get Chinese descriptions, English docs get English descriptions.
  • Be direct: State what the page covers. Avoid starting with "This document", "This page", "Learn about" — jump straight to the substance.
  • Be specific: Mention concrete technologies, APIs, or concepts the page covers. "Configure Rspress plugins for search, analytics, and internationalization" beats "How to use plugins."
  • No markdown: Plain text only, no formatting syntax.

Examples

Good:

ContentDescription
Plugin development guideCreate custom Rspress plugins using the Node.js plugin API and runtime hooks
MDX component usageImport and use React components in MDX documentation files
Rspress 快速开始从安装到本地预览,搭建 Rspress 文档站点的完整流程
主题配置自定义 Rspress 主题的导航栏、侧边栏、页脚和暗色模式
Home page (pageType: home)Rspress documentation framework — fast, MDX-powered static site generator

Bad:

DescriptionWhy
"About plugins"Too vague — which plugins? what about them?
"This page explains how to configure the Rspress theme"Wastes characters on "This page explains how to"
"Learn everything about Rspress!"Marketing fluff, says nothing specific

Documentation

來源與署名

來源:rstackjs/agent-skills位於skills/rspress-description-generator提交2966acb

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架