codex-copilot

UI Designer for software interfaces. Use for visual direction, hierarchy, typography, color, spacing, component composition, design systems, visual critique, and making an interface feel intentional before UI implementation.

UX Designer for software workflows. Use for interaction design, task flows, information architecture, page states, usability, accessibility flow, form behavior, empty/loading/error/success states, and making a service concept usable before visual design or implementation.

Use when you need the Codex Copilot equivalent of Claude Copilot /update-project: refresh a project-local Codex Copilot setup from the shared framework.

Use when you need specialist role guidance for architecture, engineering, QA, security, docs, devops, service design, UX, UI design, UI implementation, or industrial design in a Codex session or delegated subagent.

Use when you need the Codex Copilot equivalent of Claude Copilot /config: inspect or explain cc configuration, known references, paths, and environment hydration.

Use when you want to invoke codex-copilot specialist agents natively in Codex, either by selecting the right specialist skill for the main session or by mapping specialists onto real Codex spawned-agent roles for delegated work.

Use when you need the Codex Copilot equivalent of Claude Copilot /memory: inspect recent cc memory entries, known references, and task progress.

Use when you need the Codex Copilot equivalent of Claude Copilot /orchestrate: plan stream-based work, validate dependencies, and coordinate explicit user-approved Codex subagent execution.

Use when a request needs specialist routing before implementation, including bugs, feature work, architecture changes, UX work, security-sensitive changes, or tc-backed delivery planning.

Use as the primary Codex Copilot entrypoint for new work. It classifies the request, chooses the right specialist workflow, creates tc-backed planning context when needed, and routes execution through codex-copilot agents similarly to Claude Copilot's /protocol command.

Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.

Use when you need the Codex Copilot equivalent of Claude Copilot /setup-project: wire a target repository to the shared Codex Copilot framework.

Use when you need the Codex Copilot equivalent of Claude Copilot /continue: resume paused or previous work from tc tasks, work products, memory, and stream context.

Use when you need the Codex Copilot equivalent of Claude Copilot /map: produce or refresh a concise codebase map for agent navigation.

Use when you need the Codex Copilot equivalent of Claude Copilot /pause: preserve current work state in tc and memory before context switching.

Use when you need the Codex Copilot equivalent of Claude Copilot /reflect: capture lessons, decisions, and improvement notes after a work session.

Use when you need the Codex Copilot equivalent of Claude Copilot /skills-approve: review available skills and decide which reusable skills should be trusted or used for a task.

Use when you need the Codex Copilot equivalent of Claude Copilot /extensions: inspect knowledge repositories, extension status, active skills, and project/global/base resolution.

Use when you need the Codex Copilot equivalent of Claude Copilot /knowledge-copilot: create, link, inspect, or onboard to a shared knowledge repository.

Use when you need the Codex Copilot equivalent of Claude Copilot /setup-copilot or /setup: install or verify shared Copilot tooling for Codex-native projects.

Use when you need the Codex Copilot equivalent of Claude Copilot /update-copilot: update the shared Codex Copilot framework and verify plugin, cc, and tc alignment.

Optional Knowledge Copilot specialist for setting up shared knowledge repositories, known references, memory structure, and team onboarding in Codex Copilot projects.

Use when setting up Codex Copilot knowledge synchronization between project memory, shared docs, known references, and optional pack activation.

QA Engineer for software quality. Use for bug reproduction, regression analysis, edge-case design, test strategy, writing or reviewing tests, verification plans, acceptance checks, and deciding whether implementation work actually satisfies the request.

Optional Creative Director specialist for brand strategy, creative direction, positioning, campaign concepts, and product narrative before copy or UI execution.

Optional financial and tax advisory specialist for founder, agency, and product-business planning; not a substitute for licensed professional advice.

Optional Customer Success specialist for onboarding, retention, support workflows, feedback loops, and customer-facing operational patterns.

Optional Copywriter specialist for messaging, microcopy, product language, landing-page copy, emails, and concise voice execution.

DevOps Engineer for CI, deployment, infrastructure, environment setup, observability, and operational safety.

Documentation specialist for README updates, onboarding material, API docs, setup guides, and durable technical explanations.

Industrial Designer for physical, hardware, connected-product, and physical-digital software experiences. Use for tangible product design, material honesty, product form, hardware/software touchpoints, lifecycle design, repairability, and Rams/Ive-style reduction before engineering or UI work.

Engineer for software implementation. Use for coding, bug fixes, refactors, tests, CLI/backend/frontend changes, integration work, and applying a framed technical plan while preserving existing repo conventions.

Service Designer for software product work. Use for end-to-end experience framing, service blueprints, journey stages, frontstage/backstage coordination, touchpoints, failure paths, and deciding what user problem a feature should solve before UX or engineering starts.

Security Engineer for authentication, authorization, secrets, trust boundaries, unsafe inputs, data exposure, and practical security review.

Universal Codex Copilot setup router. Use when you need to decide whether to run machine/framework setup, project setup, update, or verification.

Technical Architect for software systems. Use for architecture, decomposition, technical planning, tradeoff analysis, dependency mapping, PRD/task breakdowns, migration planning, interfaces, data flows, and implementation boundaries before coding.

UI Developer for software interfaces. Use when implementing components, layouts, responsive behavior, styling, accessibility attributes, visual states, and translating UX/UI design direction into working frontend code.

Structure and write ENAC alignment documents and Statements of Work using Confront, Co-Create, and Copilot structure. Use for alignment documents, SOWs, proposals, project scopes, and consulting deliverable narratives.

Manage ENAC Background IP inventory and carve-out language. Use for contracts, IP ownership clauses, methodology protection, prompt or agent IP, deliverables, and Background IP schedule updates.

Write ENAC case studies with challenge, approach, outcome, and proof-first storytelling. Use for client stories, success stories, testimonials, proof points, and marketing case narratives.