| name | codex-composer |
| description | Use when the user mentions Composer, Cursor Composer, composer-2.5, Codex Composer, asks to use Composer as a coding/UI/design specialist, or when non-trivial UI/design/code-review work would benefit from delegating to Cursor Composer through the Codex Composer plugin. |
Codex Composer
Use this skill when the user explicitly asks for Composer/Cursor Composer, or when a task benefits from a second specialist model for UI taste, design critique, code review, patch proposals, or larger sandboxed implementation.
Codex remains the operator. Composer is a specialist delegate, not the final authority. Codex still owns applying changes, inspecting diffs, running tests, launching previews, and verifying screenshots.
Tool Map
Use the Codex Composer MCP tools exposed by this plugin:
composer_health: check SDK/auth/model access before a first live use in a session, or when Composer behavior looks suspicious.composer_ask: get design direction, architecture guidance, critique, implementation specs, or second-model review. No edits.composer_patch: ask for a scoped sandboxed change when files and desired edit are known. Returns diff/artifacts; Codex applies separately.composer_agent: delegate a larger sandboxed objective that may create or edit multiple files. Returns diff/artifacts/evidence; Codex applies separately.composer_ui_review: send screenshot/image paths plus optional repo context for visual critique.
Default Workflow
- Prefer
composer_ask for taste, design direction, critique, and planning.
- Use
composer_patch for small, bounded changes with known files.
- Use
composer_agent for larger implementation objectives, greenfield UI, or multi-file work.
- Use
composer_ui_review after Codex renders or screenshots UI locally.
