2449 个 · 按相关度排序
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
中文简介正在准备中。当前显示原文说明。
Consolidates redundant documentation while preserving all valuable content; keeps a doc set truthful after things change. Modes: (1) POST-CHANGE GOVERNANCE — when code, scripts, config, env vars, ports, paths, deployment, auth, tests, or a documented procedure changed; also "which docs are now wrong", "check docs for inconsistencies", "过时的命令/路径", "文档同步". Use it even when the user mentions only the change and never the docs — updating them is part of the change, not optional cleanup. (2) CONSOLIDATION — "clean up docs", "documentation bloat", "reduce documentation sprawl", "consolidate documentation", "too many doc files", "merge redundant docs", "merge these docs", "文档太多/太乱", multiple files covering the same topic, or documentation exceeding 500 lines across multiple files on similar topics. Finds stale copies of a fact changed in only one place, values that should never have been persisted (counts, totals, "N items", restated summaries), rival definitions that drift apart, and orphaned cross-references.
中文简介正在准备中。当前显示原文说明。
Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.
中文简介正在准备中。当前显示原文说明。
Generate comprehensive technical documentation including API docs (OpenAPI/Swagger), code documentation (TypeDoc/Sphinx), documentation sites (Docusaurus/MkDocs), Architecture Decision Records (ADRs), and diagrams (Mermaid/PlantUML). Use when documenting APIs, libraries, systems architecture, or building developer-facing documentation sites.
中文简介正在准备中。当前显示原文说明。
Comprehensive documentation specialist covering API documentation, technical writing, design documentation, migration guides, and changelog generation. Use when creating OpenAPI/Swagger specs, generating SDKs, writing user guides, creating README files, documenting architecture, writing design specs, creating ADRs, writing migration guides, or generating changelogs from git commits. Handles versioning, examples, developer experience, and user-facing documentation.
中文简介正在准备中。当前显示原文说明。
Provides automated documentation updates by analyzing git changes between the current branch and the last release tag. Performs git diff analysis to identify modifications, then updates README.md, CHANGELOG.md following Keep a Changelog standard, and discovers documentation folders for contextual updates. Use when preparing a release, maintaining documentation sync, or before creating a pull request. Triggers on "update docs", "update changelog", "sync documentation", "update readme", "prepare release documentation".
中文简介正在准备中。当前显示原文说明。
API Documentation Generator workflow skill. Use this skill when the user needs Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
中文简介正在准备中。当前显示原文说明。
Guide documentation structure, README content, and project documentation best practices. Use when: creating README, documentation, docs folder, project setup. Keywords: README, docs, documentation, CONTRIBUTING, CHANGELOG, 文件, 說明文件.
中文简介正在准备中。当前显示原文说明。
Searching internet for technical documentation using llms.txt standard, GitHub repositories via Repomix, and parallel exploration. Use when user needs: (1) Latest documentation for libraries/frameworks, (2) Documentation in llms.txt format, (3) GitHub repository analysis, (4) Documentation without direct llms.txt support, (5) Multiple documentation sources in parallel
中文简介正在准备中。当前显示原文说明。
Generate and maintain the project's TECHNICAL documentation from its codebase — scans the project structure, tech stack, and module boundaries, then writes a lean README landing page plus detailed topic pages (architecture, modules, setup, build, APIs), only the docs that are relevant. Use whenever the user wants to create, update, or validate documentation of the CODE or the project itself, e.g. "generate documentation", "create docs", "write the README", "update the project docs", "document the codebase", "document this project's architecture", "validate the project documentation". This is CODE / project documentation only — it never documents the game design. To render the GAME DESIGN (the GDD: systems, flows, content, economy) for people to read use /unikit-gd-docs.
中文简介正在准备中。当前显示原文说明。
Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).
中文简介正在准备中。当前显示原文说明。
Retrieve up-to-date library, framework, and project documentation using scripts + MCP tools (Context7, Context Hub) with intelligent fallback. Use this skill whenever the user or agent needs documentation for any library, framework, API, SDK, or internal project spec. Triggers on "docs for [X]", "how does [library] work", "find documentation", "API reference for", "look up [feature] in [library]", "latest docs", "what's the API for", "find our [internal spec]", or any request that requires current, accurate documentation rather than relying on training data. Always prefer this skill over raw WebSearch for documentation retrieval — it returns structured, context-efficient results.
中文简介正在准备中。当前显示原文说明。
Automated documentation generation, API documentation, code comments, README templates, and knowledge base maintenance. Use when creating documentation, updating READMEs, generating API docs, or maintaining project documentation.
中文简介正在准备中。当前显示原文说明。
Comprehensive toolkit for preparing ISO 13485 certification documentation for medical device Quality Management Systems. Use when users need help with ISO 13485 QMS documentation, including (1) conducting gap analysis of existing documentation, (2) creating Quality Manuals, (3) developing required procedures and work instructions, (4) preparing Medical Device Files, (5) understanding ISO 13485 requirements, or (6) identifying missing documentation for medical device certification. Also use when users mention medical device regulations, QMS certification, FDA QMSR, EU MDR, or need help with quality system documentation.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user requests to generate, create, or improve documentation for code, APIs, libraries, repositories, or software projects. Supports README generation, API reference documentation, inline code comments, architecture documentation, changelog generation, and developer guides. Trigger on requests like "document this code", "create a README", "generate API docs", "write developer guide", or when analyzing codebases for documentation purposes.
中文简介正在准备中。当前显示原文说明。
Expert in developer tool documentation as a product. Activate on: docs site, getting started guide, API reference, developer documentation, Docusaurus, Mintlify, Nextra, ReadMe, migration guide, troubleshooting page, docs information architecture, documentation testing, llms.txt. NOT for: marketing copy (use seo-content-blogging), API design itself (use api-architect), general technical writing (use technical-writer).
中文简介正在准备中。当前显示原文说明。
为功能、模块或整个项目从零补写缺失文档。按照 Diataxis 的用途分类，组织学习教程、操作指南、参考信息和原理说明，为不同阅读需求准备相应内容。
检查项目所用框架和库的版本，依据对应的官方文档实现代码，为设计决策提供来源链接，并标明已弃用的 API、未验证的方法及与现有代码的冲突。
根据近期代码和功能变更，找出文档说明与实际行为的差异，仅更新相关资料和使用示例，并整理以用户影响为重点的发布说明。
Prototype a documentation page in one HTML file, with navigation, an article, and a linked table of contents. Includes realistic explanatory text, command examples, code, and tables, plus layouts that adapt to narrower screens and right-to-left text.
中文简介正在准备中。当前显示英语简介。
Review Storybook's minimum supported browser versions using Plausible documentation traffic data. The skill presents usage evidence and proposed versions for approval, then updates pinned settings and documentation and opens a pull request with the recorded decision.
中文简介正在准备中。当前显示英语简介。
Audit and improve `/llms.txt`, a curated starting point for AI tools browsing documentation. Check its location, the usefulness and accessibility of linked pages, and its separation from existing crawl and indexing controls.
中文简介正在准备中。当前显示英语简介。
Create and edit Remotion documentation with consistent API pages, code examples, version labels, and compatibility information. The skill also guides sidebar placement and preview card generation when adding or updating pages.
中文简介正在准备中。当前显示英语简介。