「doc」の検索結果

使用 ve docs search/fetch 检索火山引擎官方文档并获取全文。Use when 用户咨询火山引擎产品的概念、用法、计费规则、部署步骤、最佳实践或服务条款，或提供 www.volcengine.com/docs/、docs.volcengine.com/docs/ 链接需要阅读正文时。

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

Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

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

Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.

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

Use when setting up or reviewing Storybook component documentation, design-system presentation, isolated component state previews, stories, addons, decorators, MDX docs, component-state interaction checks, visual baselines, or Chromatic. For real-browser cross-page journeys or broader coverage planning, choose the matching testing workflow first; Chinese triggers include Storybook, component documentation, Design System, visual regression.

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

Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the business need", "vision and scope document", "business case for this feature", "what does the business need", "strategic requirements", "document why we need this" - even if they don't explicitly say "BRD".

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

Write a data schema specification document. Use when the user says "schema spec", "document this schema", "schema design doc", "data model spec", "table spec", "field definitions", "schema contract", "data dictionary", "define these fields", or needs to formally document a database schema, event schema, or API payload schema - even if they don't explicitly say "schema spec".

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

Convert any pile of documents (PDF, Word, HTML pages, wiki exports, PowerPoint slides) into clean, LLM-ready markdown context: inventories the sources, picks the right extractor per file type (pdftotext or PyMuPDF for PDF, pandoc or mammoth for docx, readability extraction for HTML.

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

Stress-test a Yuzu plan against the repo's domain language, code, CONTEXT.md, and ADRs while updating docs as decisions crystallize. Use when the user says `/grill-with-docs`, asks to grill a design with docs, wants decision interrogation, or needs ADR-adjacent planning.

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

Documentation templates and structure guidelines. README, API docs, code comments, and AI-friendly documentation.

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

Use when authoring, reviewing, or maintaining Salesforce DevOps operational documents — runbooks, environment matrices, deployment guides, and post-deploy validation checklists. Triggers: 'runbook', 'environment matrix', 'deployment guide', 'pre-deploy checklist', 'post-deploy validation', 'how do I document a deployment', 'rollback procedure template'. NOT for what actually belongs on the pre-deploy gate — use devops/pre-deployment-checklist. NOT for release calendar, versioning, or go/no-go governance — use devops/release-management. Also covers: the devops-process YAML artefact (environment ladder, change-request state machine, deploy contract, deploy order, RACI), the deployOptions the runbook must record (checkOnly, testLevel, rollbackOnError, ignoreWarnings, purgeOnDelete, singlePackage, runTests), destructiveChangesPre/Post ordering, and the change-request emergency path.

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

Mechanical documentation hygiene. Spawns a doc-maintainer agent to audit all project documentation and fix correctness, completeness, freshness, and consistency issues autonomously within its authority. Surfaces anything requiring user judgment for approval.

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

Write, rewrite, review, and organize developer-facing documentation for web software projects. Use when creating or improving README files, docs homepages, quickstarts, tutorials, how-to guides, API/reference pages, conceptual explanations, migration guides, or troubleshooting content for frontend, backend, full-stack, SDK, API, or framework-based web products. This skill applies strong information architecture, task-first page structure, clear voice, runnable examples, version and prerequisite hygiene, accessibility rules, and docs-as-code maintenance habits. Do not use it for marketing copy, legal text, or non-technical customer-support articles.

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

Creates 5 root documentation files (PROJECT.md, docs/README.md, documentation_standards.md, principles.md, tools_config.md).

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

Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices).

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

中国大陆地区法院类案快速检索与《案件检索报告》（DOCX）生成技能。以案件五项要点（案由/法律关系、争议焦点、关键事实、我方诉请与诉讼地位、请求权基础法条）为检索锚点，经一次四问确认即开工（其中**检索地域范围**与**裁判时间范围**为强制选择题，默认范围为「2021年1月1日以后裁判的浙江省范围内的法院案例」，用户点选默认后须回显该范围提示）；按**请求权基础、法律关系、案件事实三要素**判定高匹配——用户**指定**检索特定结果的案例时结果相似度计入评分（四要素满分 10 分），用户**未指定**时结果相似度不作为高匹配考虑因素（三要素满分 8 分）；r1 判定须**核对法条版本与时间效力**，援引已失效旧法条者不得给满分；以语义向量检索为主召回、精确结构检索为条件兜底，本地脚本加权打分后按「得分率 ＞ 法院层级 ＞ 审判程序 ＞ 裁判日期」排序，并检测**同院同日同标题的重复入库**案件、疑似重复者不占入报名额；截取匹配度最高的 5–10 例类案，逐案调详情核验案号并摘录判词原文，最后直接输出含页脚页码的 DOCX 报告（默认保存至桌面）。全流程人工确认 1 次、检索类调用控制在 2 次召回 ＋ ≤10 次详情以内，报告阶段检索冻结。未指定结果时三要素高匹配而结果相反者亦会入报（逐例标注结果方向），指定结果时结果相反者一律剔除；报告内以两处固定声明披露「未设不利先例定向检索路径」的局限。当用户要求「快速检索类似案例」「找几个正向案例」「快速版案例检索报告」「检索 5 到 10 个类案并出报告」「出一份类案检索报告 docx」时使用。需要四象限归位、反向案例定向检索、补充召回多轮迭代或 14 分制硬软条件精判时，应使用完整版技能「案例检索报告Plus」而非本技能。基于华宇元典法律数据 MCP。

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

Deep analysis of competitor patent claims: element decomposition, scope interpretation, equivalents prediction, prosecution history estoppel analysis. Automatically converts PDF/DOCX/DOC patent files to structured Markdown via patent-pdf-to-md skill before analysis. Invoke when user asks to analyze/parse competitor patent claims, decompose claim elements, assess claim scope, or perform 权利要求解析/要素分解/保护范围解读. 竞品专利权利要求深度解析：要素分解、保护范围解读、等同范围预判、审查历史限制分析。自动调用patent-pdf-to-md技能将PDF/DOCX/DOC专利文件转换为结构化Markdown后再进行分析。当用户要求解析竞品专利权利要求、要素分解、保护范围时触发。

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

Creates comprehensive documentation for design systems - token tables, usage guidelines, component examples, and accessibility notes. Use after generating tokens to create developer-friendly docs.

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

CI/CD caching optimizer for dependency caching, Docker layer caching, and build speed improvements. Activate on: CI cache, build speed, dependency caching, Docker layer cache, turbo remote cache, GitHub Actions cache, pnpm store cache. NOT for: CI/CD pipeline creation (use github-actions-pipeline-builder), deployment strategy (use blue-green-deployment-orchestrator), Docker image building (use docker-multi-stage-optimizer).

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

Use this skill when running local AI models with Docker Model Runner — the `docker model` CLI — e.g. "run an LLM locally with Docker", "pull a model from the ai/ namespace", "connect my app to a local model", "use a local model as backend for the Drupal AI module", or when wiring the `models:` top-level element into a compose.yaml. Covers pulling/running models, OpenAI-compatible endpoints, and Compose integration.

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

Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.

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

Interactive Archon integration for knowledge base and project management via REST API. On first use, asks for Archon host URL. Use when searching documentation, managing projects/tasks, or querying indexed knowledge. Provides RAG-powered semantic search, website crawling, document upload, hierarchical project/task management, and document versioning. Always try Archon first for external documentation and knowledge retrieval before using other sources.

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

Establish, author, restructure, or audit human-first processor Architecture, Design, Research, Review, and Verification documentation. Use for progressive documentation scaffolding, authority maps, reading paths, document-type content contracts, length-budgeted splitting, or maintainability reviews. Do not use as a substitute for cycle-accurate microarchitecture analysis or RTL implementation.

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

Write technical documentation that matches the measured profile of professionally-written docs. Carries the craft rules derived from 114k words of pre-2022 documentation (SQLite, PostgreSQL, Python, Django, Rust, Go, Pro Git, nginx), the per-Diátaxis-type numeric targets, and the copywriting register for page leads. Use when drafting or rewriting any documentation prose, or when a page is factually right but reads as machine-written.

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

Workflow Phase 3 — Research and Solution Exploration. Surfaces 2–4 candidate solution approaches with concrete tradeoffs, grounded in current library docs (fetched through the provider named in `.claude/docs-provider.json`) — never in training-data recall. Output lives at `docs/research/<slug>.md`. Candidate ranking and the memo execute in main context; doc/source gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).

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