发现 tools technical docs 相关 Skills，比较来源仓库和用途，查看适合你工作流的技能说明。
This skill should be used when the user asks "where is this API endpoint implemented", "find the code for this route", "which file handles this endpoint", "map API findings to code", or needs to correlate OpenA...
自底向上分析代码库并生成层级化 README.md 文档树。从叶子目录开始分析，为每个目录生成包含文件、类、函数一句话描述的 README.md，逐层向上汇总形成完整的代码库文档体系。支持状态持久化和断点续传，适用于理解新项目、生...
Create world-class, production-grade technical documentation with exceptional clarity and precision. Use this skill when the user asks to write READMEs, API references, guides, or code comments. Generates profe...
Guide users through structured documentation workflows for RawDrive. Use when creating specs, proposals, feature docs, ADRs, or technical documentation. Provides three-stage co-authoring process.
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
Generate comprehensive repository documentation following team standards. Use when creating README, CLAUDE.md, ARCHITECTURE.md, DESIGN_DECISIONS.md, or any project documentation. Includes Mermaid diagrams, stat...
Demonstrates progressive disclosure by loading reference documentation on demand. Shows how skills can include additional detailed documentation without loading everything upfront.
Demonstrates how skills can reference external documentation files. Use when you need to load guidelines, best practices, or reference materials on-demand.
Retrieve up-to-date documentation and code examples from Context7. Use when you need library/framework documentation or API examples.
Generates optimized prompts for AI professional developers through interactive clarification. Asks targeted questions to refine requirements, saves tokens, and ensures reliable outputs. Use when seeking the bes...
Project documentation with MkDocs Material - consistent structure, API auto-generation, GitHub Pages deployment
Generates comprehensive documentation including README, docstrings, and API docs. Use when creating documentation, writing README files, or adding code comments.
Guidelines for clear technical writing and documentation.
Writes feature specification documents from user requirements. Use when asked to write a spec, create a spec, draft a feature spec, or document a new feature.
Writes feature specification documents from user requirements. Use when asked to write a spec, create a spec, draft a feature spec, or document a new feature.
Explore codebase, understand architecture, find how things work. Navigate unfamiliar repositories, discover code structure, find where functionality lives by intent rather than exact text. NOT for debugging fai...
Search Haskell APIs using Hoogle. Use this skill when working with Haskell projects to look up function signatures, find functions by type, or discover library documentation. Activate proactively when you need...
OpenAI Codex CLIでタスクを実行し、Claude以外の視点を得る。 コードレビュー、設計分析、実装提案でセカンドオピニオンが欲しいときに使用。 Use for: "codexで見て", "別の視点で", "Codexにレビューさせて", "OpenAIの意見...
Unity開発の公式ドキュメント検索、最新API情報、パフォーマンス最適化、ベストプラクティスを案内するガイドエージェント。Unity Engine/Editor API、UPM/NuGetパッケージ、YAML設定ファイル編集に関する質問や実装支援で使用...
Update or create API documentation after making changes to the public interface of an API. Use when modifying existing endpoints, introducing new endpoints, or when API implementation changes are complete and t...
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow help...
API development workflow and best practices for career_ios_backend FastAPI project. Automatically invoked when user wants to develop, test, or debug API endpoints. Trigger keywords: "API", "endpoint", "route",...
Generate or update project documentation in docs/ directory.
요구사항을 대화로 받아 도메인별 API 목록 문서(md)를 예시 포맷으로 생성/보강한다. 테스트 코드는 만들지 않고, 문서의 테스트 시나리오 체크리스트만 작성한다.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库，同一仓库的多个技能可能共享相同数值；它反映仓库关注度，不代表单个技能的安装量或质量评分。