2,096 件 ・ 関連度順
概要と使いどころ
Generate a README.md for the current project by analyzing the codebase structure, package files, and existing documentation. Use when asked to write a README, create documentation, or document the project.
日本語の概要は準備中です。原文の説明を表示しています。
Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieve current documentation, API references, and code examples for any library, framework, SDK, CLI tool, or cloud service — including well-known ones like React, Next.js, Prisma, Django, or Spring Boot. Use for API syntax, configuration options, version migrations, setup instructions, and library-specific debugging, even when you already think you know the answer: training data on API details and signatures is frequently outdated. Prefer this over web search for library documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Finalize documentation changes for production readiness by discovering existing conventions, verifying code-doc alignment, reviewing format/terminology/tone consistency, verifying branch/worktree intent, and structuring clean commits with a post-publish branch/worktree cleanup decision. Counterpart of finalize-and-commit for documentation projects.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when finding technical documentation for libraries, frameworks, repositories, or implementation topics.
日本語の概要は準備中です。原文の説明を表示しています。
[Documentation] Use when updating impacted documentation after code, spec, or test changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when publishing, updating, moving, or removing DeepSeek Harness documentation website pages; editing website/docs.ts mappings or navigation; diagnosing a page missing from the VitePress site; fixing projected documentation links; or running the docs:dev, docs:check, and doc-sync workflow after website-content changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
日本語の概要は準備中です。原文の説明を表示しています。
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. Use PROACTIVELY for API documentation or developer portal creation.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Standard Operating Procedures for web research, documentation lookup, evidence synthesis with citations.
日本語の概要は準備中です。原文の説明を表示しています。
Standard Operating Procedures for technical writing, README creation, API specifications, runbooks, and documentation updates.
日本語の概要は準備中です。原文の説明を表示しています。
Route requests for current library, framework, SDK, API, CLI, or cloud-service documentation through available documentation tools and primary sources.
日本語の概要は準備中です。原文の説明を表示しています。
Convert Markdown documents to PDF. Two modes available — (1) Playwright-based conversion with Mermaid diagram support for technical documentation, and (2) fpdf2-based professional PDF generation with cover pages, themed styling, and business-quality table formatting for estimates, proposals, and reports. Use this skill when converting Markdown to PDF, generating business documents from Markdown, or converting Mermaid diagrams to images. Triggers on short phrases like "PDFに変換して", "markdownをpdfにして", "PDFにして", "PDF化して", "PDF出力して", "convert to PDF", "make a PDF", or any request involving converting content to PDF format.
Automatically analyze a codebase and generate comprehensive CLAUDE.md documentation for future Claude Code sessions. Use when onboarding to a new project, creating project documentation, or generating AI coding assistant context files.
日本語の概要は準備中です。原文の説明を表示しています。
コンプライアンス・内部統制支援の専門スキル。J-SOX/SOX対応、リスクコントロールマトリクス（RCM）作成、 内部監査計画策定をサポート。内部統制の整備・運用評価から監査対応まで一貫した支援を提供。 日英両言語のテンプレートを提供し、グローバル企業にも対応。COSO内部統制フレームワーク（2013年版）に準拠。 Use when: creating J-SOX/SOX compliance documentation, building risk control matrices, planning internal audits, or assessing internal control effectiveness. Triggers: "J-SOX", "SOX", "内部統制", "コンプライアンス", "RCM", "リスクコントロールマトリクス", "内部監査", "compliance", "internal control", "internal audit", "risk assessment", "COSO"
Internal audit support skill aligned with IIA (Institute of Internal Auditors) International Standards. Provides risk-based audit planning, audit program development, workpaper documentation, finding development (Condition/Criteria/Cause/Effect), and Corrective Action Request (CAR) tracking. Use when: planning annual/quarterly audits, creating risk assessment matrices, developing audit programs and test procedures, documenting audit workpapers, writing audit findings and reports, tracking corrective actions and follow-ups, preparing for external audits (SOX, ISO). Triggers: "internal audit", "audit plan", "audit program", "audit workpaper", "audit finding", "risk assessment", "CAR tracking", "corrective action", "IIA Standards", "COSO framework", "監査計画", "監査プログラム", "監査調書", "是正措置", "リスク評価".
設計書から実装タスクへの分解を行う。デフォルトで各タスクをGitHub Issueとして起票し（1タスク＝1 Issue、詳細はIssue本文に集約、ラベルでフェーズ・ステータス管理）、ユーザーがファイル管理を明示した場合のみdocs/sdd/tasks/にファイル生成する。AIエージェント向けの具体的な実装指示やTDD手順を定義する。タスク計画フェーズのみを単独で実行する際に使用する。Do NOT use for SDDワークフロー全体の管理（sdd-documentationを使用すること）。
Structured 6-step procedure for improving, renovating, or rebuilding existing pipelines, individual project folders, documentation structures, or software stacks. Addressable as "pipeline optimizer" (for whole topic pipelines, e.g. a software, research, or game-dev pipeline) or "project-folder optimizer" (for individual project folders within a pipeline, e.g. a single software tool or paper project). Triggers on tasks like "improve pipeline X", "optimize the stack", "rebuild Y", "renovation", "pipeline refactoring", "clean up project folder", "improve folder structure", "unify conventions", "documentation consolidation", "integrate into existing system", or any substantial intervention in established structures. Delivers building-stock analysis, purpose clarification, ideal sketch, gap plan, empirical pain-point identification, and retests with fresh subagents. Prevents parallel standards, duplication, and pipeline breaks.
日本語の概要は準備中です。原文の説明を表示しています。
Generate comprehensive, developer-friendly API documentation from code, including endpoints, parameters, examples, and best practices
日本語の概要は準備中です。原文の説明を表示しています。
Developer marketing and developer relations for B2B SaaS with technical audiences. Use this skill when the buyer or user is a developer: documentation as a marketing surface, quickstarts and time-to-first-call, SDKs and sample apps, developer community and DevRel programs, open-source strategy, and technical content that survives engineer scrutiny. Also triggers on: developer marketing, DevRel, developer relations, developer experience, DX, docs, documentation, quickstart, SDK, API marketing, open source strategy, developer community, technical content, dev audience, hacker news, engineering blog.
日本語の概要は準備中です。原文の説明を表示しています。
Documentation structure and maintenance rules for the Megahub project. Use whenever making user-facing changes — adding features, changing behavior, fixing hardware compatibility, or modifying configuration. Describes which files to update, the README structure, and writing style.
日本語の概要は準備中です。原文の説明を表示しています。
AGENTS.md などの恒久ドキュメントに一過性のタスクログが混入していないか、SOP / decision / log / learned の役割が混同されていないか、公開物（README / docs / 記事）に内部メモ・ローカルパス・AI 会話断片が残っていないかを差分で検出する
Documentation conventions for generating high-quality AI agent skills from TypeScript source. Use when preparing a library for skill generation, auditing JSDoc quality, fixing audit warnings, writing @useWhen/@avoidWhen/@never tags, or asking about documentation conventions for skills.
日本語の概要は準備中です。原文の説明を表示しています。