Files
codex-game-studio/.agents/skills/cgs-ui-ux-review/SKILL.md
T
7e8846a7fb feat: add deterministic model tier routing (#14)
* feat: add deterministic model tier routing

Define Sol, Terra, and Luna policies with fixed fallbacks, explicit surface assignments, runtime precedence, and Luna escalation. Validate generated metadata and expose tier overrides across role, task, and orchestration commands.

* fix: infer model tiers from surface models

* fix: rebalance prompt model routing

* fix: decouple prompt effort routing

---------

Co-authored-by: MerlinH <merlinh221@gmail.com>
2026-07-10 18:49:20 +10:00

2.6 KiB

name, description, model, model_reasoning_effort, argument-hint, primary-agent, tool-policy, isolation, source-reference, source-hash, user-invocable
name description model model_reasoning_effort argument-hint primary-agent tool-policy isolation source-reference source-hash user-invocable
cgs-ui-ux-review Use for ui ux review tasks that review UI and UX implementation for clarity, accessibility, localization, controller support, and player comprehension; produce verification evidence, changed or proposed files, and handoff boundaries. gpt-5.6-terra medium Describe the ui-ux-review objective, target files/assets, constraints, and verification evidence. game-designer read/edit/shell/tests/git as needed within the repository write policy repository-root; no init-time generated prompt bodies .agents/skills/cgs-ui-ux-review/SKILL.md e24905e0e4f568351d7e4fd2698167a83acf2f6e681cbe15549d81527f2bec8b true

Codex Game Studio UI UX Review

Use this skill for ui ux review work in Template Game.

Objective

Review UI and UX implementation for clarity, accessibility, localization, controller support, and player comprehension.

Inputs

  • AGENTS.md
  • .codex/studio.json
  • task-relevant files named by the user or task record
  • design/gdd.md
  • docs/market-overview.md
  • .codex/workflows/ui-ux-review.md

Arguments

  • Objective or user request.
  • Target files, scenes, assets, or docs.
  • Constraints, deadlines, acceptance criteria, and verification command when known.

Procedure

  1. Clarify the requested review ui and ux implementation for clarity, accessibility, localization, controller support, and player comprehension. and identify the current project stage.
  2. Collect evidence for Friction, Comprehension, Accessibility.
  3. Draft or review the artifact in small sections, keeping player experience and scope visible.
  4. Produce the requested artifact or review with clear file paths and verification evidence.

Write Targets

  • design/

Output Contract

  • Summary
  • Friction
  • Comprehension
  • Accessibility
  • UX Verdict
  • Risks
  • Changed files or proposed files
  • Verification evidence
  • Next owner or decision

Quality Gates

  • Friction
  • Comprehension
  • Accessibility
  • UX Verdict
  • Scope remains bounded to the current task and project stage.
  • Report labels unverified assumptions separately from evidence.

Decision Gates

  • Continue only when the expected output can be verified or clearly labeled as a plan.
  • Escalate to producer or qa-playtester when scope, ownership, or acceptance evidence is ambiguous.
  • Stop before broad rewrites, generated prompt mirrors, or hidden lifecycle behavior.

Handoff

Report changed files, verification evidence, remaining risks, and the next owner or decision. Do not imply hidden hooks or autonomous background work.