2,053 件 ・ 関連度順
概要と使いどころ
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
日本語の概要は準備中です。原文の説明を表示しています。
Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Use when a programming question needs external documentation or upstream evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Creates professional API documentation using OpenAPI specifications with endpoints, authentication, and interactive examples. Use when documenting REST APIs, creating SDK references, or building developer portals.
日本語の概要は準備中です。原文の説明を表示しています。
Diátaxis-driven documentation for AI coding agents: write, improve, or audit tutorials, how-tos, reference, explanation, and developer docs (README, CONTRIBUTING, ADRs). Detects the docs stack; gates on the outline before writing prose; verifies every claim against the code before it ships. Triggers on "absolute docs", "write docs", "write a tutorial", "write a README", "document this", "improve this doc", "audit our docs".
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured documentation templates for components, patterns, or guidelines within a design system.
日本語の概要は準備中です。原文の説明を表示しています。
MiniMax presents itself as a premium AI infrastructure brand through a striking duality — bold black-pill CTAs and stark white canvas for marketing, paired with vibrant gradient product cards (orange-red, magenta-pink, purple, blue) that turn each model release into a distinctive visual identity. The system uses DM Sans across all surfaces, employs an oversized 80px hero display, anchors major actions in deep near-black pills, and layers content density via a 3-column documentation grid with sidebar nav, prose body, and TOC. Coverage spans the marketing homepage, model showcase pages, developer documentation, and platform pricing surfaces.
日本語の概要は準備中です。原文の説明を表示しています。
Context7 fetches current, version-specific documentation and code examples for software libraries and hands them to an AI coding agent, so generated code matches the library version in use instead of stale training data. Use when someone says "use context7", "get the latest docs for this library", "look up the current API", "the agent keeps using a deprecated method", "set up Context7 in Claude Code or Cursor", or asks how to call a framework whose API changed recently. Covers the ctx7 CLI, the MCP server and its two tools, library IDs and version pinning, API keys and rate limits, and the REST API.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive documentation for undocumented or poorly documented codebases. Use when a user asks to document code, add JSDoc/docstrings, create README files, generate architecture docs, explain what a codebase does, produce onboarding guides, or document internal APIs. Works with any language.
日本語の概要は準備中です。原文の説明を表示しています。
Generate release notes and changelogs from git commits, feature lists, or project updates. Use when a user asks to generate a changelog, create release notes, summarize recent changes, draft a CHANGELOG entry, or prepare release documentation from git history.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in understanding and navigating legacy codebases. Covers code archaeology techniques, finding hidden knowledge, mapping dependencies, and extracting understanding from code without documentation. Knows how to read the stories that old code tells. Use when "legacy code, old codebase, understand this code, archaeology, what does this do, no documentation, ancient code, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert in building and nurturing developer communities - DevRel strategy, developer experience, technical content, documentation communities, and turning developers into advocates. Covers OSS community building, API ecosystems, and developer-first go-to-market. Use when "developer community, devrel, developer relations, developer experience, open source community, api community, documentation community, developer advocacy, " mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
World-class design systems architecture - tokens, components, documentation, and governance. Design systems create the shared language between design and engineering that makes products feel cohesive at any scale. Use when "design system, component library, design tokens, atomic design, style guide, theme, theming, design scale, component api, variant, figma tokens, style dictionary, design-system, tokens, components, theming, documentation, figma, accessibility, versioning" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
Expert at designing clean, consistent, and developer-friendly APIs. Covers RESTful conventions, versioning strategies, error handling, pagination, rate limiting, and OpenAPI documentation. Designs APIs that are intuitive to use and easy to evolve. Use when "API design, REST API, RESTful, API versioning, API documentation, OpenAPI, Swagger, API error handling, pagination, rate limiting, api, rest, http, versioning, pagination, openapi, swagger" mentioned.
日本語の概要は準備中です。原文の説明を表示しています。
api-documenter workflow skill. Use this skill when the user needs Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
api-documenter workflow skill. Use this skill when the user needs Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Generate progressive disclosure indexes for GitHub repositories to use as Claude project knowledge. Use when setting up projects referencing external documentation, creating searchable indexes of technical blogs or knowledge bases, combining multiple repos into one index, or when user mentions "index", "github repo", "project knowledge", or "documentation reference".
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured documentation templates for components, patterns, or guidelines within a design system.
日本語の概要は準備中です。原文の説明を表示しています。
Audits any developer documentation site across 33 checks in 7 categories and produces a scored report (out of 100) with Pass / Warn / Fail status per check. Use this skill whenever a user provides a docs URL and asks to audit it, review it, score it, check its quality, or evaluate it for AI discoverability, SEO, structure, content, or completeness. Also trigger when the user says "run a docs audit", "audit these docs", "check this documentation", "how good are the docs for X", or pastes a docs URL with any evaluative intent. Always use this skill — do not attempt a freeform docs review without following this structured workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Audits any API documentation site by crawling every endpoint page and scoring each one across 5 checks: description quality, OpenAPI spec presence, body param descriptions, response codes, and response schema completeness. Produces a polished interactive HTML report with a summary scorecard, site-wide pattern analysis, ranked top issues, and per-endpoint findings with specific fix guidance. Trigger this skill whenever a user provides a documentation URL and asks to audit, review, analyse, or check their API docs. Also trigger for: "do the same audit for X", "audit docs.company.com", "check the API docs at X", "run the API docs audit on X", "review the docs for Y API", or pastes a URL alongside words like audit, review, crawl, check, analyse, quality, completeness, or gaps. Always use this skill — do not attempt the audit without following this structured crawl-score-report workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Answer user questions about QwenPaw installation and configuration: first locate and read local documentation, then distill the answer; if local information is insufficient, fall back to the official website documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Write and improve documentation for ComfyUI nodes in per-node JSON files. Use when asked to document nodes, write node descriptions, add tips to nodes, improve node docs, enrich node content, fill in empty node descriptions, or batch-write documentation for new/updated nodes. Also triggers on "write docs for nodes", "document the new nodes", "improve node tips", "fill in node descriptions", "enrich nodes", "node content pass", "update nodes", "sync comfyui nodes", "new comfyui version", or "node enrichment".
日本語の概要は準備中です。原文の説明を表示しています。
Search an index of public repositories, GitHub issues, merged pull requests, repository READMEs, and curated documentation sites. Use when a programming question needs external documentation or upstream evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Use when documentation needs creating, checking, or maintaining — docs may have drifted from code, pre-release doc verification, updating docs after finishing code work, adding or enforcing project terminology, deciding where a new doc should live, or a routine re-audit of previously verified docs.
日本語の概要は準備中です。原文の説明を表示しています。
Generate READMEs, API docs, changelogs, and knowledge base articles. Covers README structure with personality, OpenAPI-based API documentation, changelogs from conventional commits, typedoc patterns, and support KB articles.
日本語の概要は準備中です。原文の説明を表示しています。