Loading...

Search Results for "document"

documentation

vapvarun's avatarfrom vapvarun★ 3

Write clear technical documentation for themes, plugins, and web products including installation guides, configuration docs, API references, tutorials, and changelogs. Use when creating user guides, developer docs, or help articles.

documentation-standards

OshanKHZ's avatarfrom OshanKHZ★ 3

This skill should be used when the user asks about "documentation templates", "doc structure", "README format", "API documentation format", "how to write tutorials", "documentation checklist", or when the documentation-writer agent needs templates and workflows for specific documentation types. Provides Diataxis-based templates, checklists, and examples for 7 documentation types.

field-agent-documentation

treasure-data's avatarfrom treasure-data★ 3

Comprehensive template and guidelines for documenting Field Agents including technical specifications, system prompts, tool specifications, user interactions, and standardized documentation structure

api-documentor

benreceveur's avatarfrom benreceveur★ 3

Generates OpenAPI/Swagger/GraphQL documentation and SDKs from code

documentation-sync

benreceveur's avatarfrom benreceveur★ 3

Detects code/documentation drift, validates examples, generates diagrams, auto-updates documentation

document-type-adding

jakewaldrip's avatarfrom jakewaldrip★ 3

When adding a new document type to the DocuSign integration

documentation-specialist

CaoMeiYouRen's avatarfrom CaoMeiYouRen★ 3

专注于查阅、维护和生成项目文档 (位于 docs/ 目录下)。

documenter

wtthornton's avatarfrom wtthornton★ 3

Write documentation. Use when generating API docs, README files, or updating docstrings. Includes Context7 documentation standards lookup.

documentation

nguyenthienthanh's avatarfrom nguyenthienthanh★ 3

Create Architecture Decision Records (ADRs) and Runbooks for operational documentation.

command-documentation-patterns

daishiman's avatarfrom daishiman★ 3

コマンドのドキュメント設計(セルフドキュメンティング構造/使用例/トラブルシューティング)を整理し、説明の一貫性と読みやすさを支援するスキル。章構成、記述ルール、検証手順を一貫して整理する。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要求の言語化と構造化 / 目的: 説明品質の安定化Trigger:Use when documenting commands, creating usage examples, or designing troubleshooting sections for command workflows.command documentation, usage examples, troubleshooting, self-documenting structure

requirements-documentation

daishiman's avatarfrom daishiman★ 3

要件ドキュメントの作成・構造化・品質管理・ハンドオフを支援するスキル。カール・ウィーガーズの要求工学理論に基づき、ステークホルダーと開発チームの双方に有用な仕様書を作成する。Anchors:• Software Requirements (Karl Wiegers) / 適用: 要件管理全般 / 目的: 明確で検証可能な仕様• IEEE 830 SRS Standard / 適用: ドキュメント構造 / 目的: 標準準拠の仕様書• Don't Make Me Think (Steve Krug) / 適用: 情報設計 / 目的: 読みやすいドキュメントTrigger:Use when creating requirements documents, writing specifications, preparing stakeholder reviews, or establishing requirements traceability.requirements document, specification, SRS, stakeholder review, traceability matrix, 要件定義書, 仕様書

runbook-documentation

daishiman's avatarfrom daishiman★ 3

運用ランブックの作成・保守スキル。本番システムの障害対応、トラブルシューティング手順、リカバリーワークフロー、運用知識の共有を標準化し、信頼性の高いシステム運用を実現する。Anchors:• Site Reliability Engineering (Google) / 適用: ランブックパターン、ポストモーテム / 目的: 運用の卓越性と信頼性• The Practice of System and Network Administration (Limoncelli) / 適用: 手順書標準化 / 目的: 再現可能な運用• Incident Management for Operations (Mogull) / 適用: インシデント対応 / 目的: 効果的な危機対応Trigger:Use when creating runbooks, documenting incident procedures, standardizing operational workflows,building troubleshooting guides, establishing recovery procedures, improving on-call readiness.runbook, incident response, troubleshooting, recovery procedures, operational documentation, on-call playbook

error-documentation

daishiman's avatarfrom daishiman★ 3

Comprehensive error documentation patterns for APIs, libraries, and systems.Covers error catalogs, troubleshooting guides, recovery procedures, andrunbook creation to improve developer experience and reduce support burden.Anchors:• The Pragmatic Programmer (Hunt, Thomas) / 適用: error communication / 目的: clear actionable messages• Site Reliability Engineering (Google) / 適用: runbook patterns / 目的: operational excellence• API Design Patterns (JJ Geewax) / 適用: error response design / 目的: consistent error contractsTrigger:Use when documenting API errors, creating error catalogs, writing troubleshooting guides,designing runbooks, standardizing error responses, improving error discoverability.

documentation-architecture

daishiman's avatarfrom daishiman★ 3

ドキュメント構造設計・リソース分割・階層設計を専門とするスキル。500行制約に基づく適切なファイル分割とトピックベース組織化により、保守性と発見可能性の高いドキュメントアーキテクチャを実現する。Anchors:• Information Architecture (Rosenfeld/Morville) / 適用: 情報組織化パターン / 目的: 発見可能性向上• Clean Architecture (Robert C. Martin) / 適用: 依存関係ルール / 目的: 責任分離設計• The Pragmatic Programmer (Hunt/Thomas) / 適用: DRY原則 / 目的: 重複回避Trigger:Use when designing documentation structure, splitting large files over 500 lines, organizing resources with topic-based structure, improving discoverability, or establishing naming conventions.documentation structure, file splitting, directory organization, hierarchy design, naming conventions, 500-line constraint

api-documentation-best-practices

daishiman's avatarfrom daishiman★ 3

OpenAPI、Swagger、RESTful APIドキュメンテーションのベストプラクティスを提供する専門スキル。Anchors:• 『RESTful Web APIs』(Leonard Richardson)/ 適用: REST APIドキュメンテーション / 目的: リソース設計とHTTP操作の標準化Trigger:OpenAPI/Swagger定義設計時、APIエンドポイント仕様書作成時、REST APIドキュメント整備時、認証仕様文書化時、エラーレスポンス標準化時、ドキュメントレビュー時に使用

technical-documentation-standards

daishiman's avatarfrom daishiman★ 3

IEEE 830やDoc as Codeなどの標準に基づき、技術文書の構造と品質基準を整えるスキル。テンプレート適用と検証フローを通じて、再利用性と明確性を高める。Anchors:• IEEE 830 / 適用: 仕様書構造 / 目的: 標準化• Documentation as Code / 適用: 文書運用 / 目的: 継続的管理• Software Requirements (Karl Wiegers) / 適用: 要求記述 / 目的: 明確性Trigger:Use when defining documentation standards, creating SRS templates, or reviewing technical docs for consistency.documentation standards, IEEE 830, SRS, doc-as-code, documentation review

entity-relation-based-documentation

ShunsukeHayashi's avatarfrom ShunsukeHayashi★ 3

Generate documentation based on Miyabi's Entity-Relation Model (14 entities, 39 relationships). Use when documenting features, updating architecture docs, or explaining how components work.

aps-documentation

seanchatmangpt's avatarfrom seanchatmangpt★ 3

Comprehensive skill for working with Agile Protocol Specification documentation.Automatically activates when creating, editing, or reviewing APS content.Provides templates, naming conventions, and document lifecycle guidance.

Page 12 →

Frequently Asked Questions

What is a Claude Skill?

It is a modular, protocol-based instruction set that enables Claude to perform specific tasks autonomously and efficiently.

How is this different from regular prompts?

Skills use the official Anthropic protocol for better token efficiency and automatic triggering compared to static prompts.

Does it support the new Claude Code CLI?

Yes, we provide specialized one-click installation commands designed specifically for Claude Code and OpenCode.

Can I use these skills in Cursor?

Absolutely, our library is fully compatible with popular IDEs and extensions including Cursor, Codex, and AntiGravity.

Are the skills on the website free to use?

Most skills in our 90,000+ database are free and open-source for the community to download and deploy.

How can I contribute my own skills?

Developers can easily share their work by submitting their own skill repositories through our community portal.