'documentation' 검색 결과

Write and revise Chinese technical documentation using consistent spacing, punctuation, terminology, and structure. Includes README.md and API documentation templates, bilingual formatting examples, and a checklist for reviewing documents before publication.

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

• Standardizing spacing and punctuation in Chinese documents
• Writing a Chinese README.md
• Organizing API documentation in Chinese and English

Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.

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

• Create an OpenAPI specification from an existing API
• Write getting-started and authentication guides
• Prepare and test API request examples

Generate or update up to nine project documentation files using agents that inspect the code directly. Check documentation against the implementation, review existing files without writing changes, or explicitly regenerate all documentation.

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

• Create project documentation from the codebase
• Update documentation after implementation changes
• Check existing documentation without writing files

Route broad requests about project documentation to a suitable specialist skill. When requested, run a read-only audit of document roles, local links, architecture decision indexes, and evidence references, reporting failures and items needing review.

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

• Choose a workflow for organizing project documentation
• Identify existing documentation sources
• Audit local links and architecture decision indexes

Turn source code into project documentation, from a README with installation steps and examples to API references, architecture diagrams, developer guides, and changelogs. Match the scope and comment format to the project's size and programming language.

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

• Creating a README with installation steps and usage examples
• Documenting public functions, parameters, and return values
• Preparing architecture and contributor guides for new developers

Generate and update API or project documentation, and flag inconsistencies between existing docs and current code. Schedule recurring maintenance and save the documentation approach for reuse in later work.

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

• Updating documentation after code changes
• Finding inconsistencies between code and docs
• Generating API or project documentation

Maintain Cherry Studio documentation by checking it against source code, placing facts in appropriate files, and removing duplication. Review documentation affected by code changes and keep relevant English and Chinese counterparts aligned.

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

• Organizing READMEs and reference documentation
• Reviewing documentation affected by code changes
• Checking comments and agent instructions against code

Creates software documentation using Diátaxis, a framework that separates learning, task instructions, reference information, and explanation. Clarifies the audience, goal, and scope, then proposes an outline before writing Markdown content consistent with existing documentation.

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

• Writing a practical tutorial for newcomers
• Creating a guide to solve a specific problem
• Organizing technical details into reference documentation

Maintain Composio's documentation site and record documentation decisions. Work on content, Fumadocs configuration, changelogs, automation prompts, and review guidance, including ADR-style records that capture decisions and their rationale.

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

• Update Composio documentation content and changelogs
• Revise Fumadocs settings and documentation automation prompts
• Record or update documentation decisions

Use when you need to generate or improve Java project documentation — including README.md files, package-info.java files, and Javadoc enhancements — through a modular, step-based interactive process that adapts to your specific documentation needs. This should trigger for requests such as Improve the code with documentation; Apply documentation; Refactor the code with documentation; Generate README or developer documentation for a Java project; Document Java APIs architecture or project workflows. Part of Plinth Toolkit

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

API Documentation Workflow workflow skill. Use this skill when the user needs API documentation workflow for generating OpenAPI specs, creating developer guides, and maintaining comprehensive API documentation and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

기술 문서와 에이전트·기여자용 지침 파일을 작성하고 검토합니다. 설명과 운영 절차, 다국어 버전의 일관성을 확인하고 근거가 충분한 문제를 수정합니다.

• 기술 문서 작성 및 갱신
• README와 문서 변경 사항 검토
• 에이전트 지침과 기여 절차 정리

Compare release changes with project documentation, then update files such as README and CHANGELOG to reflect what shipped. The skill also checks architecture diagrams, maps missing documentation, and records remaining documentation work in the pull request.

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

• Updating project documentation after a release
• Checking architecture diagrams against shipped changes
• Polishing changelog entries and organizing TODOs

Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.

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

• Improve the structure and examples of a documentation page
• Draft documentation for a new feature
• Plan page types and outlines

Find current documentation and code examples through the Context7 MCP server. Look up library setup, API usage, migration steps, and library-specific problems, using documentation for the requested version when available.

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

• Looking up documentation for a specific version
• Finding library setup and configuration steps
• Finding examples for code that uses external libraries

Configure MCP connections, which link AI agents to tools, for AWS documentation search and API access. Check existing settings, choose between documentation-only and full API access, verify available tools, and troubleshoot connection or credential problems.

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

• Set up AWS documentation search for an AI agent
• Configure an MCP connection for AWS API access
• Check existing AWS MCP settings

Turn API code into documentation covering endpoints, inputs, authentication, responses, and errors. Add request examples in multiple languages and usage guides to help developers understand and start using the API.

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

• Writing documentation for a new API
• Updating API documentation after code changes
• Preparing API guides for new developers or external users

Search automatically generated code documentation to check function parameters, class definitions, API details, and comments before making changes. Find relevant documents by meaning, exact keywords, or document type, then retrieve their full contents.

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

• Check function parameters before implementation
• Find documentation about authentication
• List class and component documentation

Find and retrieve official OpenAI documentation to answer API integration questions with source evidence. Check endpoint definitions, parameters, and documented limits, and receive setup guidance when the documentation connection is unavailable.

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

• Verify specifications before integrating an OpenAI API
• Check endpoint parameters and schemas
• Support technical explanations with official documentation

Organize Confluence documentation with clear page hierarchies, reusable templates, and access plans. Create and update pages, embed Jira reports, and audit existing content to identify outdated material and establish review responsibilities.

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

• Restructure a team's Confluence space
• Standardize meeting notes and decision logs
• Embed Jira issues and charts in documentation

Keep project documentation aligned with recent code changes. Review commits since the last checkpoint, update affected guides and README files, and open a pull request for human review only when documentation needs correcting.

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

• Keeping documentation aligned with daily code changes
• Updating guides after API or configuration changes
• Catching up on documentation after missed sync runs

Create and maintain code comments, API specifications, documentation sites, and user guides. Apply consistent formats, document parameters and errors, validate code examples, and report which parts of the code have been documented.

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

• Add explanations to public functions and classes
• Create API specifications and reference pages
• Build a documentation site

Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.

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

• Creating or updating technical documentation
• Reviewing README files and documentation changes
• Aligning agent instructions with contribution procedures

Write and edit READMEs, guides, and other documentation using the code as evidence. Improve structure, wording, and terminology while checking related pages and links against the project's contribution process and documentation style guide.

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

• Writing a guide for an existing feature
• Improving a README's structure and wording
• Updating documentation to match the implementation