Files
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.5 KiB

model, model_reasoning_effort, primary-agent, linked-skills, phase, risk, argument-hint, source-reference, source-hash, output-artifacts
model model_reasoning_effort primary-agent linked-skills phase risk argument-hint source-reference source-hash output-artifacts
gpt-5.6-terra medium ui-ux-designer
cgs-ux-design
cgs-team-ui
plan high Provide a UX design request with player journey, screens or flows, accessibility constraints, relevant files, owner or handoff needs, and verification evidence. .codex/workflows/ux-design.md cccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc
plan
changed-files
verification-evidence
handoff

UX Design Workflow

Purpose

Design player journeys, HUD, menus, interaction states, onboarding, accessibility hooks, and implementation-ready UX artifacts.

Inputs

  • AGENTS.md
  • .codex/studio.json
  • .codex/workflows/ux-design.md
  • GDD, UX notes, control manifest, accessibility notes, or screenshots

Role

UI UX Designer (ui-ux-designer) owns this workflow.

Taxonomy

Category: localization-accessibility CCGS adaptation coverage:

  • UX design
  • player journey and interface specification CLI aliases:
  • ux-design

Outputs

  • UX flows, screen states, interaction states, and edge cases.
  • Accessibility and localization considerations.
  • Implementation handoff with required UI artifacts and verification checks.

Validation

  • Player goals and friction points are explicit.
  • Accessibility and input constraints are included.
  • Implementation-ready states and acceptance criteria are named.

Phase Gates

  • Confirm project state, owner role, write policy, and selected context.
  • Name required artifacts and acceptance criteria before implementation or review work.
  • Do not advance to handoff until evidence is recorded or a blocker is explicit.

Required Artifacts

  • Summary of the workflow result.
  • Files, assets, tasks, docs, release notes, or tests changed or proposed.
  • Verification evidence and unresolved risks.

Context Contract

  • Load AGENTS.md, .codex/studio.json, this workflow, the primary agent, linked skills, and only task-relevant project files.
  • Avoid broad context unless the user explicitly approves it.

Output Contract

  • Decision or change summary.
  • Step-by-step work performed or planned.
  • Evidence, blockers, warnings, and next owner.

Stop Conditions

  • Required project state, approval, target files, or verification path is missing.
  • The task crosses into another role without an explicit handoff.
  • The workflow would require generated prompt mirrors or hidden automation.

Handoff

Report changed files, validation evidence, residual risks, and the next owner only when ownership changes.