duo-codex

Coordinates Claude and Codex pair workflow for diagnosing and fixing Unity mini-game issues.

1|Updated Jul 29, 2026
One-click install
npx skills add https://github.com/Bornqazaq/sleepover --skill duo-codex-bornqazaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: duo-codex
Source: https://github.com/Bornqazaq/sleepover/tree/main/.claude/skills/duo-codex
Command: npx skills add https://github.com/Bornqazaq/sleepover --skill duo-codex-bornqazaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Working with Codex (Astra 6) on Unity mini-games wastes its usage limit on problem discovery rather than fixes, and poorly scoped prompts cause context compaction, lost task items, and wasted effort. This Skill defines a division of labor where Claude diagnoses issues in the running game and writes targeted prompts, while Codex only executes fixes. ## Core Features & Use Cases - Role separation workflow: Claude enters Play mode via Unity MCP, captures screenshots, diagnoses bugs, and verifies results; Codex writes code, builds art, and edits scenes. - Prompt modes and reasoning levels: Distinguishes cheap targeted prompts (symptoms listed, medium reasoning) from expensive creative prompts (artistic search, xhigh reasoning), with rules for prompt size and session splitting. - Post-Codex verification checklist: Validates frozen files, console output, in-game visuals, network code, and commits after every Codex session. - Use Case: A game designer notices broken UI in a Unity mini-game. Claude enters Play mode, captures screenshots of the failure, writes a five-point targeted prompt with exact symptoms, Codex fixes it, and Claude verifies the result in-game before committing. ## Quick Start Ask Claude to enter the Unity game, diagnose the visible problems, and write a targeted prompt for Codex to execute.

Frequently Asked Questions about duo-codex

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split work between Claude and Codex on a Unity project?

Claude enters Play mode via Unity MCP, captures screenshots, diagnoses bugs, and writes the prompt; Codex only executes fixes. This avoids spending Codex's limit on problem discovery, which costs more than the fix itself.

How to write a prompt for Codex that does not lose tasks?

Keep one prompt to one area with no more than five or six items, and make each prompt self-contained with files and symptoms included. Codex context compacts quickly, and after compaction it silently drops the tail of long task lists.

What reasoning level should I use for Codex tasks?

Use medium for fixes based on an existing diagnosis, high for tasks with one non-obvious spot, and xhigh only for multi-file connected work like composition overhauls. High levels on simple targeted prompts cause overengineering and waste.

Why does Codex revert its own work after receiving a prompt?

This happens when the prompt contains a stale diagnosis describing code Codex already changed. Always verify with git status and file modification times before sending, since Codex will roll back its own fresh work to match outdated symptoms.

When should I not enter Unity Play mode while Codex works?

Never enter Play mode while Codex is working, because it hijacks the editor and triggers recompilation. Ask whether Codex has finished before launching the game for verification.