القائمة
Use when ai-docs content depends on external facts, official documentation, product behavior, CLI flags, package versions, Theme Hope capabilities, or claims that may change
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when planning ai-docs sections, routes, page hierarchy, navigation, sidebar grouping, redirects, indexes, or documentation taxonomy before writing pages
Use when adding Theme Hope Markdown extensions, tabs, code tabs, demos, components, images, include snippets, charts, math, PlantUML, GFM, or advanced Markdown syntax in ai-docs
Use when changing ai-docs Theme Hope styles, SCSS variables, colors, fonts, layout widths, static assets, logos, favicons, images, videos, or public files
Use when changing VuePress Theme Hope config, routing, navbar, sidebar, theme options, plugins, homepage layout, or documentation site behavior in ai-docs
Use when ai-docs documentation, VuePress Theme Hope config, navigation, sidebar, Markdown enhancements, assets, styles, or published routes may be complete or failing
Use when creating, rewriting, expanding, localizing, or reorganizing Markdown documentation pages in the ai-docs VuePress site
| name | ai-docs-research |
| description | Use when ai-docs content depends on external facts, official documentation, product behavior, CLI flags, package versions, Theme Hope capabilities, or claims that may change |
本 skill 用于把外部资料转成可靠文档事实。原则是：先确认来源，再写结论；优先官方文档和项目源码；把不确定性显式写出来，不把猜测包装成事实。
Do not use for purely local copyediting where no factual claim changes.
| Priority | Source | Use |
|---|---|---|
| 1 | Official docs, official repo, official changelog, source code | Normative facts and exact config behavior. |
| 2 | Maintainer issues/discussions with accepted answers | Edge cases and known limitations. |
| 3 | Current project files | Local implementation and enabled features. |
| 4 | Third-party tutorials | Ideas only; verify against priority 1 before writing. |
| 5 | Model memory or old notes | Starting hypothesis only, never final evidence. |
When the user provides specific URLs, read those URLs first. For Theme Hope, prefer theme-hope.vuejs.press and the official vuepress-theme-hope GitHub repo.
package.json, src/.vuepress/theme.ts, navbar.ts, sidebar.ts, and existing Markdown pages.| Need | Official Entry |
|---|---|
| Project setup, commands, content, routes, config, structure, deployment | https://theme-hope.vuejs.press/get-started/ |
| Theme features, layout, Markdown, components, blog, customization | https://theme-hope.vuejs.press/guide/ |
| Theme options, Markdown config, plugin config, frontmatter config, style config | https://theme-hope.vuejs.press/config/ |
| Troubleshooting, common errors, Vite problems, support requirements | https://theme-hope.vuejs.press/faq/ |
| VuePress core config and plugin behavior | https://vuejs.press/ |
src/.vuepress/theme.ts enables it and required dependencies exist in package.json or transitive docs clearly cover it.hotReload is enabled or the dev server restarts.When research affects docs, include:
Do not paste long upstream excerpts. Summarize and link.
| Mistake | Fix |
|---|---|
| Copying a tutorial without checking official docs | Verify against official docs and local config first. |
| Treating upstream default as local enabled behavior | Inspect theme.ts and package.json. |
| Writing "latest" from memory | Check current source before using time-sensitive language. |
| Hiding uncertainty | State "未确认" and provide the next verification step. |
| Using a feature because docs mention it | Check whether the project has enabled it and installed required packages. |