メニュー
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.
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 | uid |
| description | 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. |
Use this skill to implement polished, accessible UI.
$qa for verification.code work product when tc context exists.Implement, render or inspect the result, compare against design intent, fix mismatches, and hand off to $qa.
Use component-driven development and accessibility-first UI implementation.
Return:
$qa for visual, interaction, accessibility, and regression verification.$uids when visual direction is insufficient.$uxd when interaction behavior is unresolved.