광고[ For iPhone / iPad ] 🔥 Nugget의 믿을 수 없는 인터랙티브 월페이퍼. 이런 것은 본 적이 없을 것입니다!

skills.homescapability registry 검색

home/categories/documentation

domain cluster

Documentation

Knowledge bases and technical writing tools.

6010 스킬all categories

sorting

stars

current ordering strategy

query

all entries

refine the visible subset

technical-docs

4

error-documentation

Comprehensive error documentation patterns for APIs, libraries, and systems. Covers error catalogs, troubleshooting guides, recovery procedures, and runbook 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 contracts Trigger: Use when documenting API errors, creating error catalogs, writing troubleshooting guides, designing runbooks, standardizing error responses, improving error discoverability.

daishiman

documentation

technical-docs

4

mkdocs

Build professional project documentation with MkDocs and Material theme. Covers site configuration, navigation, plugins, search optimization, versioning with mike, and deployment to GitHub Pages.

vamseeachanta

documentation

technical-docs

4

comment-generator

Generate code comments and docstrings. Use when user asks to "add comments", "document this code", "explain with comments", or "add docstrings".

Dexploarer

documentation

technical-docs

4

swift-docc-comments

Use when writing or enhancing Swift documentation comments for DocC generation, adding inline doc comments to Swift source files, or when user asks for API documentation

ivan-magda

documentation

technical-docs

4

bupkis-docs

How to create & maintain TypeDoc site documentation and the README for Bupkis

boneskull

documentation

technical-docs

4

writing-plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

alexsandrocruz

documentation

technical-docs

4

technical-documentation-standards

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

daishiman

documentation

technical-docs

4

documentation-research

Enforces online documentation research before any technical implementation. Use when implementing features to ensure code follows current best practices by researching official documentation first.

jpoutrin

documentation

technical-docs

4

django-expert

Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.

vintasoftware

documentation

technical-docs

4

swift-docc-github-pages

Use when setting up DocC documentation for a Swift package, deploying to GitHub Pages, or encountering "no such module 'UIKit'" during doc generation

ivan-magda

documentation

technical-docs

4

api-documentation-best-practices

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

daishiman

documentation

technical-docs

4

command-documentation-patterns

コマンドのドキュメント設計（セルフドキュメンティング構造/使用例/トラブルシューティング）を整理し、説明の一貫性と読みやすさを支援するスキル。章構成、記述ルール、検証手順を一貫して整理する。 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

daishiman

documentation

technical-docs

4

tutorial-writing

Technical tutorial writing in modified DigitalOcean style. Use when (1) writing step-by-step technical tutorials, (2) creating documentation for code/applications, (3) explaining technical concepts procedurally, (4) working with Temporal applications/tutorials, or (5) the user asks to write, create, or help with a tutorial. Follows specific style constraints: friendly but formal tone, comprehensive explanations, code sandwich approach, assumes English is reader's second language, and never generates new code (only references provided code).

MasonEgger

documentation

technical-docs

4

tdd-testing

Guide for Test-Driven Development in the DEVS platform. Use this when asked to write tests, implement TDD, or add test coverage for lib/ and stores/ code.

codename-co

documentation

technical-docs

4

writing-plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

alexanderop

documentation

technical-docs

4

markdown-advanced-syntax

技術ドキュメント向けMarkdown高度構文スキル。Mermaid図、複雑テーブル、コードブロック、数式表現を活用。 Anchors: • GitHub Flavored Markdown Spec / 適用: 拡張構文 / 目的: プラットフォーム互換ドキュメント • CommonMark Spec / 適用: 基本構文 / 目的: クロスプラットフォーム互換性 • Mermaid Official Docs / 適用: ダイアグラム / 目的: ビジュアル技術文書 Trigger: Use when creating technical documentation with Mermaid diagrams, complex tables, syntax-highlighted code blocks, mathematical expressions, or YAML front-matter.

daishiman

documentation

technical-docs

4

documentation

Updating user guides, CLI reference, and API documentation for the B2C CLI project

SalesforceCommerceCloud

documentation

technical-docs

4

example-usage-patterns

Documentation patterns for creating clear, executable, and maintainable usage examples across APIs, CLIs, libraries, and frameworks. Anchors: • Docs for Developers (Jared Bhatti et al.) / 適用: 実践的な例示パターン / 目的: 開発者に即座に理解・実行可能な例を提供 • The Documentation System (Diataxis) / 適用: チュートリアル・ハウツー・リファレンス分類 / 目的: 目的に応じた例の種類と粒度を選択 • Clean Code (Robert C. Martin) / 適用: 明確な命名・単一責務 / 目的: 自己説明的なサンプルコード Trigger: Use when creating code examples, writing tutorials, documenting API usage, building sample projects, establishing example conventions, or standardizing example patterns across a codebase. example creation, tutorial writing, API documentation, sample code, documentation patterns

daishiman

documentation

technical-docs

4

sphinx

Generate comprehensive Python documentation with Sphinx. Covers autodoc for API extraction, Napoleon for Google/NumPy docstrings, intersphinx for cross-references, and multiple output formats including HTML, PDF, and ePub.

vamseeachanta

documentation

education

3

architecting-solutions

Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.

Charon-Fan

documentation

knowledge-base

3

consulting-design

Consult Gemini AI for architecture alternatives, design trade-offs, and brainstorming. Use when seeking different perspectives on design, evaluating architectural approaches, comparing solutions, or generating creative ideas.

julianobarbosa

documentation

knowledge-base

3

learning-taxonomy

Expert knowledge for categorizing learnings and routing them to appropriate improvement targets. Use when analyzing session learnings to determine where context improvements should be applied.

yebot

documentation

knowledge-base

3

bcm-specialist

Expert for Business Continuity Management (BCM) with deep knowledge of ISO 22301, ISO 22313, and integration with ISO 27001. Automatically activated when user asks about business continuity, disaster recovery, crisis management, emergency planning, BC plans, BC exercises, or BCM compliance.

moag1000

documentation

knowledge-base

3

agent-guidelines

When you need to understand the project's core mandate, operational rules, or "Constitution". Use this skill to align with the project's identity and strict coding standards.

nextblock-cms

documentation

Page 169 / 251