Results for “documentation”

Update Han plugin documentation so every skill, agent, guidance doc, index, and cross-reference is current and accurate. On a non-default branch, scopes the pass to entities the branch actually touched. On the default branch, performs a full documentation sweep across the whole plugin. Use when updating, refreshing, syncing, auditing, or verifying Han's docs after changing skills, agents, references, or top-level guidance — including "update the docs", "doc sweep", "refresh documentation", "audit the docs", "make sure the docs are current". This is a repository-maintenance skill for the Han repo itself, not a general documentation skill — use /project-documentation to document features in arbitrary projects, /han-release to cut a release (and update CHANGELOG), and /update-pr-description for PR bodies.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Review documentation for quality, clarity, SEO, and technical correctness. Optimized for Docus/Nuxt Content but works with any Markdown documentation. Use when asked to: "review docs", "check documentation", "audit docs", "validate documentation", "improve docs quality", "analyze documentation", "check my docs", "review my documentation pages", "validate MDC syntax", "check for SEO issues", "analyze doc structure". Provides actionable recommendations categorized by priority (Critical, Important, Nice-to-have).

The English summary is being prepared. Showing the original description.

Look up current library and framework documentation through Context7 MCP, a connection to live documentation tools. Supports setup questions, API references, and code examples, using version-specific sources when available to ground answers in retrieved material.

• Looking up framework setup and configuration
• Checking library API methods and usage
• Finding documentation examples for Prisma queries

Launch the Remotion documentation site locally and open it in the Codex in-app browser. The workflow installs dependencies, builds the project, starts Docusaurus, and reports the actual preview URL and server status.

• Launch the local Remotion documentation site
• Preview documentation changes in Docusaurus
• Open the documentation preview inside Codex

Find current Remotion documentation for a feature or API, the interface used by code. Search for relevant pages and read their Markdown text so implementation follows the documentation available now.

• Check how to use a Remotion API
• Find documentation for a feature before implementation
• Read relevant documentation pages as Markdown

Search current library documentation and code examples with Context7 CLI, a command-line tool. Find API usage and configuration guidance, select available version-specific documentation, and prioritize examples in the programming language you use.

• Checking current API usage and configuration
• Finding documentation for a requested version
• Prioritizing code examples in a chosen language

Create task-oriented READMEs, API references, architecture documentation, and security reports. Organize information from quick starts to deeper explanations, and turn completed investigations into formal Markdown reports with supporting evidence, reproducible steps, and appropriately masked sensitive information.

• Writing a README with a clear quick start
• Organizing API and architecture documentation
• Reporting reverse engineering or penetration test findings

Create or update API documentation from source code. The skill produces OpenAPI/Swagger specifications, descriptions of API operations, parameter and response references, authentication guidance, and practical examples for developers integrating an API.

• Creating API documentation from source code
• Generating OpenAPI/Swagger specifications
• Preparing API request and response examples

Scan a codebase to create project documentation and project-specific agent instructions. The first run examines the whole project; later runs focus on changed files, with human confirmation required before updating agent instructions after architectural changes.

• Create documentation when starting agent-assisted development
• Refresh project documentation after architecture changes
• Check changed code for documentation drift

Create technical documentation that people and AI can navigate by separating facts, context, known bugs, and uncertain claims. Convert existing Markdown to HADS, a structured documentation format, and check its required elements.

• Write API documentation for people and AI
• Convert an existing README to HADS
• Check document structure and block formatting

Create or refresh documentation for object-oriented components, software parts built around classes and interfaces. Analyze the current code to describe architecture, public APIs, dependencies, and usage examples using a shared Markdown template.

• Creating component documentation from source code
• Updating existing documentation to match current code
• Explaining class relationships and public APIs

Reorganize NemoClaw documentation into focused pages with clearer navigation and a single home for each topic. Plan or implement structural changes while preserving useful information and existing published URLs, then validate routes, links, and builds.

• Splitting long documentation pages into focused topics
• Consolidating duplicated troubleshooting and reference content
• Reorganizing navigation while preserving published URLs

Update NemoClaw documentation after merged changes or audit it for outdated guidance. Verify current behavior against source and tests, edit the pages responsible for that guidance, and check affected links and generated variants.

• Catch up documentation after merged changes
• Audit documentation for outdated guidance
• Update guides for changed user behavior

Find and synthesize official Google developer documentation for platforms including Google Cloud, Gemini, Android, and Firebase. Retrieve command syntax, API details, permissions, and product comparisons through Developer Knowledge, then turn the findings into practical technical answers.

• Checking gcloud commands and flags
• Looking up API syntax and required permissions
• Comparing Google products and architectures

Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.

• Update documentation after feature releases
• Check documentation gaps before a release
• Review changes since a specific tag

Update documentation to match source changes on the current branch. Map changed files to existing pages, verify behavior against the code, revise affected references and examples, and report missing documentation using repository-specific mapping rules.

• Updating API documentation after code changes
• Fixing guides and examples affected by renamed parameters
• Finding missing documentation pages or sections

Fill documentation gaps identified by a CARLA documentation audit, following the project's writing style. Work through one category at a time, assess which findings deserve entries, update source files, and report changes and skipped findings.

• Add missing Python API documentation
• Expand sensor reference documentation
• Review outdated API entries for renaming or removal

Read existing code to reconstruct system specifications, including architecture, data flows, APIs, and business rules. Produces documentation tied to code locations, separating observed behavior from inferences and questions that need clarification.

• Understand an undocumented legacy system
• Document existing APIs and business rules
• Map module dependencies and data flows

Write, review, and edit developer documentation for SDKs, libraries, and frameworks. Organize guides, API references, and code examples around readers’ tasks, checking technical claims against source code and official documentation while following the destination site’s conventions.

• Writing a getting-started guide
• Reviewing API documentation and code examples
• Updating migration and troubleshooting guides

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.

The English summary is being prepared. Showing the original description.

Audit, write, and improve developer documentation using Google's Developer Documentation Style Guide and Technical Writing courses. Use this skill for any documentation work, even when the user names no style guide: "audit our docs", "review this README", "write a README", "getting started guide", "how-to or tutorial", "API reference", "docstrings", "CLI help text", "changelog or release notes", "migration guide", or "our docs are confusing". Also use it when writing docs from code, rewriting a doc for clarity, fixing headings, procedures, or code samples, or enforcing consistent voice and terminology across a docs set — prefer it over editing documentation unaided. Covers reader and doc-type fit, second person and active voice, procedures, headings, lists and tables, code samples and placeholders, link text, notices, the word list, timeless docs, and accessibility. For code comments and naming, see clean-code. For marketing or landing-page copy, see storybrand-messaging.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.