菜单
Use when rendered UI behavior, layout, interaction states, responsive behavior, accessibility, customer language, or user-facing state changes. Do not use for pure backend, docs, or non-rendered refactors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | ui-evidence |
| description | Use when rendered UI behavior, layout, interaction states, responsive behavior, accessibility, customer language, or user-facing state changes. Do not use for pure backend, docs, or non-rendered refactors. |
UI evidence is an overlay on implementation validation, not a replacement.
Return:
Do not say a UI is improved without visual or runtime evidence.
Explicit GPT-5.6 native-first router for auditing, designing, installing, or validating Codex skill combinations, global skill setup, routing fixtures, and harness behavior. Use when the user explicitly invokes $codex-skill-router or asks to change or inspect Codex skills, routing, AGENTS guidance, or global harness configuration. Do not use for ordinary coding, review, debugging, research, or UI work merely because the task is complex.
Use when work introduces or changes shared nouns, states, IDs, ownership, authority, or customer-facing vocabulary.
Use when changing harness gates, routing rules, skills, or automation behavior and benchmark/eval evidence is needed to avoid slowing normal coding performance. Do not use for ordinary app code changes.
Use when a request is early, ambiguous, or lacks a codebase-backed shared language; interview the user to expose assumptions before planning.
Use when a codebase, docs, ADRs, tests, prior reviews, or team traces exist; align new work with existing shared language before implementation.
Use first for normal or high-risk natural-language work to choose task mode, tier, grill path, spec layers, team-rule scan, and required gates before implementation.
