knowledge-base
4
interrogate-spec
Reads a detailed specification and critically consider any issues or problems to make sure that the design makes sense
simonrw
documentation
结果数
53,183
符合搜索条件的技能
当前页
1696
共 2660 页
关键词
ai
按名称、标签或描述搜索
knowledge-base
4
structured-writing
構造化ライティングを実践するためのスキル。DITAやトピックベースの原則に沿って文書を分割・再利用し、手順/概念/参照の役割を明確にする。 Anchors: • DITA 1.3 Specification / 適用: トピック設計 / 目的: 文書構造の標準化 • Information Architecture for the World Wide Web / 適用: 情報設計 / 目的: 探しやすさの向上 • Topic-Based Authoring / 適用: 再利用設計 / 目的: モジュール化と保守性の改善 Trigger: Use when designing topic-based documentation, modular content, or reusable docs with clear task/concept/reference separation. structured writing, DITA, topic-based authoring, content reuse, documentation structure
daishiman
documentation
productivity-tools
4
create-memory
Store important information, decisions, implementations, or learnings to the knowledge base. Use when preserving context, decisions, debugging solutions, or implementation details for future reference.
Lira-tron
tools
knowledge-base
4
gobby-memory
This skill should be used when the user asks to "/gobby-memory", "remember", "recall", "forget memory". Manage persistent memories across sessions - store, search, delete, update, and list memories.
GobbyAI
documentation
knowledge-base
4
sources-section
Appends a Sources/References section using only web sources from the sources pool.
elenaviter
documentation
productivity-tools
4
docs-validating-factual-accuracy
Universal methodology for verifying factual correctness in documentation using WebSearch and WebFetch tools. Covers command syntax verification, version checking, code example validation, API correctness, confidence classification system ([Verified], [Error], [Outdated], [Unverified]), source prioritization, and update frequency rules. Essential for maintaining factual accuracy in technical documentation and educational content
wahidyankf
tools
knowledge-base
4
skill-librarian-commands
スキルライブラリの管理、検索、一覧表示、構造検証を行うコマンド群を提供するスキル。 スキルの発見、品質検証、使用状況の記録を効率化し、スキルエコシステムの健全性を維持する。 Anchors: • The Pragmatic Programmer (Hunt & Thomas) / 適用: 自動化・ツール設計 / 目的: 効率的なスキル管理 • 18-skills.md / 適用: スキル構造・検証基準 / 目的: 品質基準の担保 • Unix Philosophy / 適用: 小さなツールの組み合わせ / 目的: 柔軟なコマンド設計 Trigger: Use when listing skills, validating skill structure, searching for skills, or managing skill metadata. skill list, skill search, skill validation, skill management, librarian commands
daishiman
documentation
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
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
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
debugging
4
explain-code
Explain how code/features work by tracing execution flow. Saves markdown to ~/Developer/explanations/ and previews in browser.
ahkohd
tools
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
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