Jewel591
UserClaude Code skills that turn the OpenAI Codex CLI into Claude's second perspective: persistent tmux review loops, strict reviewer/doer separation
Categories
Indexed Skills (2)
codex-image-gen
When the task is to produce image assets (app icons, illustrations, placeholder art, draft marketing visuals, etc.), delegate to the tmux Codex pane instead of writing drawing scripts yourself. Applies to any task whose deliverable is "one or a set of image files".
using-codex-collaboration
Use proactively whenever the work involves substantial code changes (multi-file, core logic, architecture), a freshly written execution plan, a sticky bug that resists single-perspective diagnosis, or a non-obvious design decision that needs adversarial challenge — establishes when and how to bring Codex in as a reviewer (not as an executor). The ONLY channel is the persistent Codex pane reached via tmux (send-keys / capture-pane) — this holds even when Claude's own session is NOT running inside tmux (drive the tmux server externally; create a detached session if needed). Direct `codex` CLI invocation (codex exec etc.) is FORBIDDEN unless the user explicitly requests it, because it loses context. Covers locating/launching the Codex pane, the predefined collaboration scenarios (review-uncommitted, plan review, adversarial challenge, bug rescue), and the review⇄fix consensus loop that runs until Codex passes.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.