Results for “docs”

Update docs, playbooks, shims, generated docs, and alignment checks so public instructions route to the right canonical sources.

The English summary is being prepared. Showing the original description.

ドキュメント要件分析: docs/ フォルダ内のコンセプトおよび要件ドキュメントを分析し、現在のコードと照らし合わせて要件を検証し、統合差異レポートを作成します。

The English summary is being prepared. Showing the original description.

Create, update, fix, or refine documentation using Diataxis framework and BMad Method style guide. Use when user asks to 'create a doc', 'update docs', 'fix docs style', 'refine docs', or 'improve docs writing'.

The English summary is being prepared. Showing the original description.

ドキュメント観点のレビューエージェント。 README / docs / AGENTS.md と実装の整合性、API ドキュメントとコードの対応、 usage や例の正確性、i18n（JA/EN）整合性、用語統一を検証する。

The English summary is being prepared. Showing the original description.

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, latest/current/default-model prompting guidance, 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.

The English summary is being prepared. Showing the original description.

Templates and structural patterns for API docs, feature docs, config guides, and REST endpoint documentation. Use when structuring docs, applying Markdown templates, or standardizing doc formats.

The English summary is being prepared. Showing the original description.

Publish a project's docs as a static HTML manual on GitHub Pages: check that Pages is enabled, bring the wiki up to date, list the doc gaps, build the site, preview it locally and push it after GO. Use for "publish the docs", "docs site", "put the manual on GitHub Pages".

The English summary is being prepared. Showing the original description.

コードにコメント・ドキュメンテーションコメントを追加・補強する。「コメント追加して」「コメント書いて」 「コメントを補強して」「JSDoc 付けて」「docstring 付けて」「ドキュメンテーションコメント付けて」で使用。 パッケージ・サービス視点での役割境界、呼び出し元・呼び出し先の前提と契約、他ファイル・他サービスからの 文脈を「その場で読める」形で残す。コード自体は変更しない（実装変更は implement-issue へ）。 詳細規約は code-comment-style、コミット作成は create-commit、CLAUDE.md 同期は update-docs を参照。

The English summary is being prepared. Showing the original description.

通用任務開單器 SKILL — 統一建立或回寫 Markdown task card、docs/tasks/tasks-*.json 分片、UI quality shard，並強制遵守 docs/agent-briefs/Readme.md (doc_ai_0023) 與 docs/遊戲規格文件/系統規格書/名詞定義文件.md (doc_spec_0008) 的硬規則。USE FOR: 開任務卡、開單、task card、task shard、tasks-ui.json、tasks-prog.json、tasks-dc.json、tasks-data.json、agent-briefs/tasks、docs/tasks/*_task.md、UI pipeline 開卡。DO NOT USE FOR: 純 runtime 除錯、單純修改既有功能碼但不需要新卡、只做極小 typo 修補。

The English summary is being prepared. Showing the original description.

This skill should be used when the user asks to "ドキュメントを更新して", "sync the docs", "update CLAUDE.md after this change", "実装に合わせてドキュメントを直して", or notices that docs have drifted from the codebase. Diffs git history to identify what changed, proposes targeted updates to CLAUDE.md, docs/architecture.md, docs/requirements.md, and README.md, then applies only approved changes.

The English summary is being prepared. Showing the original description.

開発作業の設計書（design.md）を単体で生成・再生成します。全ドキュメントの一括生成には generate-working-docs（新規機能開発）または generate-performance-docs（パフォーマンス改善）を使用してください。

The English summary is being prepared. Showing the original description.

開発作業の要件定義書（requirements.md）を単体で生成・再生成します。全ドキュメントの一括生成には generate-working-docs（新規機能開発）または generate-performance-docs（パフォーマンス改善）を使用してください。

The English summary is being prepared. Showing the original description.

開発作業のテスト手順書（testing.md）を単体で生成・再生成します。全ドキュメントの一括生成には generate-working-docs（新規機能開発）または generate-performance-docs（パフォーマンス改善）を使用してください。

The English summary is being prepared. Showing the original description.

開発作業のタスクリスト（tasklist.md）を単体で生成・再生成します。全ドキュメントの一括生成には generate-working-docs（新規機能開発）または generate-performance-docs（パフォーマンス改善）を使用してください。

The English summary is being prepared. Showing the original description.

Generates comprehensive documentation templates for open-source and internal projects including README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, LICENSE, and other standard docs with suggested sections and best practices. Use when users request "create project docs", "add OSS documentation", "setup standard docs", or "make it open-source ready".

The English summary is being prepared. Showing the original description.

Create and review technical documentation alongside repository instructions for agents and contributors. The skill checks clarity, working procedures, documentation coverage, and consistency across languages, then provides updated drafts or findings with validation notes.

• Creating or updating technical documentation
• Reviewing README files and documentation changes
• Aligning agent instructions with contribution procedures

Route broad requests about project documentation to a suitable specialist skill. When requested, run a read-only audit of document roles, local links, architecture decision indexes, and evidence references, reporting failures and items needing review.

• Choose a workflow for organizing project documentation
• Identify existing documentation sources
• Audit local links and architecture decision indexes

Review documentation and prose against the Vercel Writing Guidelines, checking voice, tone, formatting, and structure. Findings identify files and line numbers, using a bundled guideline snapshot as the default reference for repeatable reviews.

• Reviewing documentation before publication
• Checking voice and tone across several files
• Finding formatting and structural issues

Create and maintain API documentation in OpenAPI 3.0, a standard format for describing APIs. Document endpoints, request and response data, authentication, and errors with clear examples and reusable definitions.

• Create a specification for a user API
• Document request, response, and error examples
• Update documentation after API changes

Regenerate downloadable PDFs for four Remotion legal documents after updating their MDX source pages. The workflow covers generation, checking content and page layout, and committing the updated sources together with the PDFs.

• Refresh legal PDFs after editing source pages
• Check PDF headings, tables, links, and page breaks
• Commit legal document sources and PDFs together

Maintain Remotion’s expert listings, portraits, and generated cards, then regenerate the homepage animation with transparency. The workflow covers separate Chrome and Safari video formats and checks that matching assets stay consistent across both homepage consumers.

• Add or edit an expert listing
• Update portraits and regenerate expert cards
• Regenerate transparent homepage animations

Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.

• Implementing a new effect for @remotion/effects
• Registering effect imports and parameter types
• Creating documentation and an interactive effect demo

Draft Prisma 8 release notes from merged PRs since the previous published release. Select user-facing changes, put breaking changes first, link migration guidance and PR evidence, and mirror the notes in CHANGELOG.md.

• Draft notes for a stable or RC release
• Summarize changes since the previous published release
• Explain breaking changes with migration guidance

Review and refine source-code comments and documentation attached to functions or other declarations. The skill removes redundant explanations, checks outdated TODOs, and preserves concise, evidence-based reasons and constraints that maintainers cannot readily infer from the code.

• Cleaning up redundant code comments
• Reviewing TODO and FIXME markers
• Checking documentation when changing code