What problem does it solve? Moving a game project from Claude Code to Codex normally means manually rewriting CLAUDE.md guidance, slash commands, agents, and hooks, with a real risk of losing or corrupting existing configuration. This Skill inspects the Claude project and produces a reviewed, confirmed, and reversible migration plan instead of blind overwrites. ## Core Features & Use Cases - Project Inspection: Reads CLAUDE.md, .claude/, AGENTS.md, .codex/, engine markers, and uncommitted work without modifying anything. - Planned Conversion: Maps Claude slash commands to namespaced $ai-game-studio skill references, converts guidance into root or scoped AGENTS.md files, and places supported agent definitions under .codex/agents/. - Safety Gates: Blocks unsupported Claude-only model names, tool declarations, memory fields, and fixed turn limits, then requires verbatim digest confirmation before applying changes with full rollback support. - Use Case: A studio with an existing Claude Code game project wants to adopt Codex; the Skill generates a migration plan, waits for digest confirmation, applies it, and validates the result with tests and a rollback path. ## Quick Start Use the migrate-claude skill to inspect this Claude Code game project and propose a reversible Codex migration plan before changing any files.
