mirror of
https://github.com/merlinhu1/codex-game-studio.git
synced 2026-08-25 07:54:34 +02:00
7e8846a7fb
* 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>
2.2 KiB
2.2 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-standards-gameplay | Use for standards gameplay tasks that mechanics, tuning, data-driven values, engine idioms, and player-facing acceptance checks; produce verification evidence, changed or proposed files, and handoff boundaries. | gpt-5.6-luna | low | Describe the standards-gameplay objective, target files/assets, constraints, and verification evidence. | producer | read/edit/shell/tests/git as needed within the repository write policy | repository-root; no init-time generated prompt bodies | .agents/skills/cgs-standards-gameplay/SKILL.md | 8f4a5521503528f90ec5445e328bb4d23150b5ebd74fecb22fb7449f9a26165e | true |
Codex Game Studio Gameplay Standards
Use this skill for gameplay standards work in Template Game.
Objective
mechanics, tuning, data-driven values, engine idioms, and player-facing acceptance checks
Inputs
- AGENTS.md
- .codex/studio.json
- task-relevant source, tests, docs, or assets
Arguments
- Objective or user request.
- Target files, scenes, assets, or docs.
- Constraints, deadlines, acceptance criteria, and verification command when known.
Procedure
- Read the requested files and identify the gameplay standards rule being applied.
- Check mechanics, tuning, data-driven values, engine idioms, and player-facing acceptance checks.
- Report violations with file paths, impact, and the smallest safe fix.
Output Contract
- Rule applied
- Files checked
- Violations
- Verification
Quality Gates
- Data Driven Values
- Engine Boundary
- Playable Check
- 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.