菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
| name | protocol-router |
| description | 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 this skill to classify the request and choose the right specialist flow before coding.
| Request type | Start with |
|---|---|
| bug, regression, test failure | qa |
| backend feature, refactor, architecture, performance | ta |
| user-facing feature, workflow, product experience | sd or uxd |
| physical product, connected product, hardware/software touchpoint | ind |
| visual polish, design system, component styling | uids or uid |
| auth, permissions, secrets, trust boundaries | sec in addition to primary flow |
| docs, onboarding, references | doc |
| deploy, CI, env, infrastructure | do |
If the user did not explicitly ask for subagents, apply the specialist lens in the main session.
If the user explicitly asked for delegation or parallel work, you may spawn subagents after deciding:
tc PRD or task existsqa before closing implementation workRead ../protocol/references/generated-workflows.md for the catalog-derived
sequences. This router classifies requests; it does not maintain another copy
of the workflow graph.
Read references/routing-matrix.md when you need the full mapping.