Codex Dream Skin

Apply a reversible renderer skin through Chromium DevTools Protocol while launching the official Store-installed Codex executable. Never replace or take ownership of files under WindowsApps.

Workflow

Run this workflow directly when the skill is invoked. Do not tell the user to open PowerShell or click a shortcut unless they explicitly ask for manual instructions.

1. Run scripts/install-dream-skin.ps1 once to initialize local state and create optional launch/restore shortcuts. It must not read or change Codex config.toml.
2. Run scripts/start-dream-skin.ps1. Add -RestartExisting only when the user authorized restarting an already-open Codex app.
3. Run scripts/verify-dream-skin.ps1 -ScreenshotPath <absolute-path> after launch. Treat a missing hero, native composer, sidebar skin, or injection marker as failure. The native suggestion count is responsive and may be two to four.
4. Inspect the screenshot against references/qa-inventory.md. Verify both the home screen and a normal task before signing off.
5. Run scripts/restore-dream-skin.ps1 for live removal. Add -Uninstall only when the user also asks to delete shortcuts and local integration.

Guardrails

• Preserve the official executable, package signature, user threads, pets, plugins, and authentication state.
• Do not use the full reference screenshot as a fake whole-window overlay. It is only a cropped hero/polaroid asset; all controls remain live Codex controls.
• Keep the reference image confined to the single top banner and decorative crop. Keep the cards below it as native Codex suggestion buttons with native labels/icons.
• Attach the "选择项目" treatment to Codex's real project-selector toolbar and keep the current project button clickable; never draw a disconnected replacement.
• Keep decorative layers pointer-events: none and keep real buttons, navigation, and composer above them.
• On app updates, rerun install and launch; the scripts discover the current Appx package dynamically.
• If port 9335 is occupied, choose another port consistently for start, verify, and restore.
• Keep the injection daemon running for navigation/reload resilience. Its state and logs live under %LOCALAPPDATA%\CodexDreamSkin.

Resources

• scripts/injector.mjs: CDP connection, renderer injection, verification, screenshot, and removal.
• assets/dream-skin.css: full visual layer.
• assets/renderer-inject.js: idempotent DOM integration and cleanup.
• assets/dream-reference.png: user-provided visual reference used only in cropped decorative regions.
• references/qa-inventory.md: required functional and visual signoff coverage.
• references/runtime-notes.md: troubleshooting and update behavior.