'documentation' 검색 결과

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create missing documentation for a feature, module, or whole project. Use Diataxis, a framework that separates tutorials, practical guides, reference information, and explanations, to organize documents around what readers need to learn or accomplish.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing documentation for an undocumented feature
• Creating tutorials and practical guides
• Preparing module references and explanations

Check project dependency versions and consult the relevant official documentation before writing framework-specific code. Produce implementations with source links, identify deprecated APIs, and flag unverified approaches or conflicts between documentation and existing project patterns.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Verify an implementation against version-specific documentation
• Create starter code with documented patterns
• Review code for deprecated APIs

Keep project documentation consistent with recent code changes. Find outdated instructions, update affected reference pages and examples, and write release notes focused on user impact while leaving unchanged sections intact.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Update documentation after a feature ships
• Check documentation before a release
• Fix outdated defaults and instructions

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prototyping an API reference page
• Designing a tutorial with commands and code
• Planning a guide with navigation and a table of contents

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review minimum browser versions using documentation traffic
• Compare browser version shares and approve support floors
• Update browser settings and migration documentation together

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Audit llms.txt on a public documentation site
• Select useful API references and getting-started guides
• Check documentation links for availability

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a documentation page for a public API
• Standardize code examples and parameter descriptions
• Review version labels and compatibility information

Fetch current library documentation with the ctx7 CLI to check API usage while coding. The skill also guides Context7 MCP setup, which connects documentation access to Claude Code, Cursor, or OpenCode, and covers login and authentication options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Fetch current documentation for a library
• Check API signatures while writing code
• Set up Context7 for an AI coding agent