Build or modify backend APIs, services, jobs, persistence, and integrations while preserving contracts, authorization, data integrity, and failure behavior. Use for server-side features, database changes, background processing, backend defects, and service refactors; do not use for frontend-only or infrastructure-only work.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Read references/contracts-and-data.md when the task changes a public API, schema, transaction, job, or integration.
Implement the smallest change at the owning layer. Cover success, invalid input, authorization, and material failure paths. Prefer:
reproducing/focused test → contract/integration test → type/lint → build
For migrations, validate forward behavior and document rollback or roll-forward strategy.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.
日本語の概要は準備中です。原文の説明を表示しています。
Select the smallest useful Codex engineering workflow from this repository's existing skills. Use when a task spans multiple engineering concerns, the user is unsure which skill to invoke, or loading every specialist would waste context; return a recommendation only and do not execute the engineering task.
日本語の概要は準備中です。原文の説明を表示しています。
Implement a repository code or configuration change through reproduction, focused checks, review, and evidence. Use for end-to-end features and fixes; not for explanation-only, review-only, research, content publishing, or production operations.
日本語の概要は準備中です。原文の説明を表示しています。
Review a small code or documentation change and return only evidence-backed correctness findings. Use in the Codex How To local plugin lab; do not modify files or post remote comments.
日本語の概要は準備中です。原文の説明を表示しています。
Maintain a review-first Markdown knowledge base for Codex practices with source provenance, engineering capture, citation-aware queries, explicit archive and promotion, and deterministic linting. Use when asked to capture a durable engineering lesson, ingest Codex research, query or archive what the repository knows, check wiki health, reconcile conflicting guidance, or promote verified knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Plan and implement infrastructure, CI/CD, container, deployment, observability, and operational configuration changes with least privilege, staged validation, and rollback awareness. Use for pipelines, infrastructure as code, Kubernetes, containers, release automation, monitoring, and production-readiness work; do not use to perform destructive production actions without explicit authorization.
日本語の概要は準備中です。原文の説明を表示しています。