「doc」の検索結果

Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale.

日本語の概要は準備中です。原文の説明を表示しています。

Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.

日本語の概要は準備中です。原文の説明を表示しています。

[Documentation] Use when a workflow step or the user asks for documentation sync after code/spec/test changes (--mode=update), or explicit reference-doc initialization and reconciliation (--mode=init).

日本語の概要は準備中です。原文の説明を表示しています。

[Document Processing] Use when converting between Word DOCX and Markdown (GFM, math rendering). --to={markdown|docx}.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Docker — Dockerfile edits, docker-compose services, containers, or the dual-container (fast + Xdebug) setup — even when the user just says 'my container won't start'.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive quality control for U.S. patent application filing documents. Use when the user asks to QC, check, validate, or review patent filing documents before submission to the USPTO. Performs 70+ automated and manual checks across specification, drawings, ADS, declaration, assignment, and power of attorney documents. Detects cross-document inconsistencies, formatting issues, missing required fields, and common errors.

日本語の概要は準備中です。原文の説明を表示しています。

Document brownfield projects for AI context. Use when the user says "document this project" or "generate project docs"

日本語の概要は準備中です。原文の説明を表示しています。

Interact with Paddock — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via Paddock APIs.

日本語の概要は準備中です。原文の説明を表示しています。

[Documentation] Use when a workflow step or the user asks for a refresh of every selected, evidence-applicable reference-doc scan target, or a --targets= subset, at once. One doc: scan; first-time setup: docs-manager --mode=init.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the user asks how to build with OpenAI products or APIs, asks about Codex itself or choosing Codex surfaces, needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; use OpenAI docs MCP tools for non-Codex docs questions, use the Codex manual helper first for broad Codex self-knowledge, and restrict fallback browsing to official OpenAI domains.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Especialista em containerização Docker com conhecimento profundo de multi-stage builds, otimização de imagens, segurança em containers, orquestração com Docker Compose e padrões de deploy em produção. Use PROATIVAMENTE para otimização de Dockerfile, problemas em containers, problemas de tamanho de imagem, hardening de segurança, networking e desafios de orquestração.

日本語の概要は準備中です。原文の説明を表示しています。

Crawl websites and extract content from multiple pages via the Tavily CLI. Use this skill when the user wants to crawl a site, download documentation, extract an entire docs section, bulk-extract pages, save a site as local markdown files, or says "crawl", "get all the pages", "download the docs", "extract everything under /docs", "bulk extract", or needs content from many pages on the same domain. Supports depth/breadth control, path filtering, semantic instructions, and saving each page as a local markdown file.

日本語の概要は準備中です。原文の説明を表示しています。

Use when the 文档/交付 role maintains client-facing project delivery document packages, especially Word/DOCX deliverables such as delivery lists, demo scripts, acceptance forms, change confirmations, quote notes, contract-adjacent materials, README/docs indexes, and internal handoff notes.

日本語の概要は準備中です。原文の説明を表示しています。

Manage Docker containers, images, volumes, networks, and Compose stacks — lifecycle ops, debugging, cleanup, and Dockerfile optimization. Use when running, debugging, or cleaning up Docker containers or Compose stacks.

日本語の概要は準備中です。原文の説明を表示しています。

Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.

日本語の概要は準備中です。原文の説明を表示しています。

Use Exasol document-file virtual schemas for federated read-only access to object and file storage — S3, Google Cloud Storage, Azure Blob Storage, and Azure Data Lake Storage Gen2 document files. Covers document-file adapter family selection, the EDML `MAPPING` definition, `CREATE VIRTUAL SCHEMA` usage, refresh workflows, and query-side troubleshooting.

日本語の概要は準備中です。原文の説明を表示しています。

Build document analysis applications with Azure Document Intelligence (Form Recognizer) SDK for Java. Use when extracting text, tables, key-value pairs from documents, receipts, invoices, or building custom document models.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Read and understand PDF documents with the pdf_* tools - inspect a document before reading it, extract text in reading order or as reconstructed layout, search a document without reading all of it, recognize scanned pages that have no text layer, and render pages as pictures. Covers scanned documents, chat attachments, page-range and character caps, and the read-only and untrusted-content rules.

日本語の概要は準備中です。原文の説明を表示しています。

ISTQB/JSTQB のテストプロセス各工程の出口ゲートとして、工程成果物（test-plan.md / test-analysis.md / test-design.md / test-case.md / テスト実装 / test-execution-log.md / test-monitoring.md / test-summary-report.md）をレビューするスキル。決定論スクリプトの機械検査（トレーサビリティ ID 突合・テンプレ準拠）と test-reviewer サブエージェントの定性レビューを行い、利用者が通過/条件付き通過/差し戻しを判定して軽量記録 test-review-<工程>.md を残す。上流の仕様・基本設計（spec / design-doc 工程。docs/dev/<対象>/spec.md・basic-design.md）は機械検査と利用者判定のみの軽量ゲートとして扱う。各工程スキル（test-plan〜test-report / feature-spec / basic-design）が完了宣言の前に本スキルの実行を促す。ソースコード diff のレビュー（diff-review）とは別物で、対象はテストプロセスの成果物のみ。成果物の修正・代作はしない。/test-review <テスト対象名> [工程] で明示的に呼び出されたときのみ使用する。

要件定義と実装の間を埋める技術仕様書を体系的に作成するスキル。 画面設計、API設計、DB設計、シーケンス図、状態遷移図をMermaid形式で生成し、 IEEE 830/ISO 29148準拠の仕様書を出力する。Use when creating functional specifications, API design documents, database design documents, screen design specifications, or sequence/state diagrams from requirements. Triggers: "technical specification", "functional spec", "API design", "database design", "screen design", "画面設計書", "API設計書", "DB設計書", "技術仕様書", "シーケンス図", "状態遷移図"

Relentless one-question-at-a-time interview (tappable options with a recommended answer) that sharpens a requirement, business plan, project plan, proposal, or raw idea through conversation, then writes it up as a brief with a glossary and decision log. Use whenever the user wants their thinking stress-tested or pinned down before acting — trigger phrases include "grill me", "grill this", "詰めて", "詰めたい", "壁打ち", "要件を固めたい", "企画を練りたい", "計画を整理したい", "アイデアをぶつけたい", "突っ込んで", "clarify", "質問して", "何が決まってないか教えて", or when the user describes a plan/idea vaguely and asks what to do next. Do NOT use for reviewing a finished document (use a document-review skill) or when the user just wants an answer, not questions.

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", "監査計画", "監査プログラム", "監査調書", "是正措置", "リスク評価".