メニュー
Decide where instructions, memory, plans, and artifacts should live between global Codex baseline and project-specific files. Use when creating/updating AGENTS/ROADMAP/memory docs, introducing new workflow rules, or deciding whether content belongs in ~/.codex/rules versus a repository.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create premium Accenture-branded PowerPoint presentations following Tufte data visualization principles and Dieter Rams design philosophy. Use when creating slides, presentations, or decks for Accenture corporate settings that require (1) Accenture brand identity (purple A100FF chevron logo clean layouts) (2) Minimal data-focused design (Tufte less but better) (3) Executive-ready aesthetics for boardroom presentations client pitches or internal reports
Route proposed additions to the global Codex control plane by deciding whether a request belongs in `~/.codex/AGENTS.md`, a global workflow or reference doc under `~/.codex/docs`, `~/.codex/bin/workflow.py`, or an enforceable non-prose surface. Use when asked to "add this to global AGENTS", "promote this workflow to global", "add a new global trigger", or decide whether something should be a trigger, workflow, reference, hook, lint rule, or runtime guard.
Add, remove, serve, test, and operate a server-backed in-page agent feedback capability for HTML artifacts, static pages, or local app builds. Use when the user wants Browser-style annotation inside the artifact/app itself, marker-local chat, comment-triggered agent work, queued marker processing, deterministic install/remove scripts, preflight/closeout checks, browser acceptance evidence, or progressive-disclosure access to marker context.
Audits any agent harness codebase against 13 meta-principles of quality, scores each 0 to 10 with code citations, generates a self-contained HTML report for operators, and writes an agent-readable AGENTS.md improvement directive with file-level architecture recommendations to reach 9.5 or better. Use when the user wants to audit or rate an agent harness, evaluate harness quality, score an agent framework, get a roadmap for improving a harness, run agentharness-audit, audit this harness, rate Hermes, audit Codex, or audit a Claude Code harness. Not for individual skill audits or general code review.
Use when controlling ChatGPT Atlas through Codex Computer Use, especially browser tasks where context efficiency matters: fewer screenshots, fewer UI snapshots, fewer clicks, and cleaner browser state.
Audit project against golden principles, produce scorecard. Use for /audit, "check project quality". NOT for system setup health (/harness-audit) or eval scoring (/eval-score).
| name | project-context-router |
| description | Decide where instructions, memory, plans, and artifacts should live between global Codex baseline and project-specific files. Use when creating/updating AGENTS/ROADMAP/memory docs, introducing new workflow rules, or deciding whether content belongs in ~/.codex/rules versus a repository. |
Apply a deterministic routing workflow so each update is stored once, in the correct scope, with minimal duplication.
global, project, or target-project).~/.codex/rules):
AGENTS.md, principles.md, soul.md, default.rules, global ROADMAP.md.AGENTS.md, repository ROADMAP.md, task-specific docs.JARVIS.md and project execution memory for that target app.~/.codex/rules/ROADMAP.md.<repo>/ROADMAP.md.~/.codex/rules/AGENTS.md.<repo>/AGENTS.md.JARVIS.md only inside non-core target repos where Jarvis executes work.When the same rule appears in multiple places:
references/context-placement-matrix.md.