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 从公开仓库中收录这些内容。

举报或申请下架