Use when frontend, backend, mobile, data, DevOps, or security work needs domain routing and at most four focused references.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Detect the primary domain, load at most 4 references from references/INDEX.md, and stay inside that domain. Frontend UI goes to codex-frontend-implementation. Do not announce this skill at start. Quality gates are loaded by the gate skills, not here.
$codex-domain-specialist..codex/profile.json first (references/project-profile-spec.md). If missing, use detection in references/INDEX.md.Loading: and Skipping:.codex-frontend-implementation, not local frontend catalogs.references/output-quality-gates.md is owned by codex-execution-quality-gate / codex-visual-quality-gate. Do not bulk-load it here.Use references/INDEX.md for the decision table, signal maps, combos, and starters. Compact detection:
| Signal | Domain |
|---|---|
.tsx / components / styling | Frontend → implementation skill |
routes/, services/, api/ | Backend API |
| schema, migration, query | Database |
| auth, secrets, attack surface | Security |
| Docker, CI/CD, deploy | DevOps |
| prompt, RAG, embeddings | AI/LLM |
Prefer the smallest change that satisfies the task, tests, and existing project patterns.
Do not add a new dependency, service, worker, cache, queue, design system, or abstraction unless repo evidence shows the simpler path fails.
If adding complexity, state: Why simpler option fails, What this complexity buys, and How we will verify it.
Use this overlay after domain detection. It does not replace references/INDEX.md.
| Task Signal | Tool Action | Evidence To Record |
|---|---|---|
| Unknown repo structure | Targeted rg and focused reads | Files inspected and why they matter |
| Helper script involved | Run --help first | CLI contract and limits |
| Auth, secrets, upload, deploy | Apply the Security overlay | Attacker-controlled input and closest control |
Rules:
Apply when attacker-controlled input, secrets, auth, public APIs, uploads, or trust boundaries change. Name the closest existing control and choose proportional defenses.
Create tickets when more than one AC, domain, or phase is involved. Include TICKET-###, owner, linked AC, likely files, dependencies, security notes, and a validation check.
Never bulk-load all references. Keep solutions project-specific. Frontend craft lives in codex-frontend-implementation/craft/.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
日本語の概要は準備中です。原文の説明を表示しています。
Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
日本語の概要は準備中です。原文の説明を表示しています。
Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
日本語の概要は準備中です。原文の説明を表示しています。