| name | nt-runtime-automation |
| description | Use when working with AI Studio runtime automation for a running game: DevAPI client/CLI, endpoints and command.describe discovery, frame.wait loops, ui.tree/ui.click, native iteration helpers, screenshots, recordings, pixel-health checks, UI readability evidence, or live-state capture matrices. Use for runtime proof collection and automation tooling, not for game design, task tracking, or general visual quality rules. |
NT Runtime Automation
Use this skill to collect runtime evidence or change the local runtime proof
helpers owned by ai_studio/runtime_automation/. The skill is the workflow
entrypoint; reusable Python clients, capture helpers, and proof tooling stay in
the reviewed AI Studio module.
Load Only What Applies
references/runtime-workflow-rules.md: launch/reuse rhythm, evidence paths,
native-first proof, and boundaries for game-specific smoke scripts.references/devapi-pattern.md: DevAPI discovery, command metadata, UI/input,
frame sync, and capture flow.references/visual-qa-checklist.md: only when the task asks for visible
runtime evidence; quality acceptance rules live in ai_studio/quality/.
Default Workflow
- Check
ai_studio/runtime_automation/README.md for module ownership and
commands.
- Find the project launch path and DevAPI port from the active game docs or
runbook.
- Discover the live runtime contract before acting: call
endpoints, then
command.describe for unfamiliar commands.
- Use the shared helpers:
ai_studio/runtime_automation/devapi_client.py,
devapi_cli.py, iterate.py, state_capture.py,
pixel_health.py, and ui_readability.py.
- Use observe -> act ->
frame.wait -> observe. Wrap interactive injection
(ui.click, input.*) in DevApiClient.player_gated() — an ungated click
with a live mouse lands in a non-primary slot, not slot 0. Capture
logs/screenshots only after the visual state is stable.
- Report concise evidence paths and failures. Do not claim runtime behavior
from code inspection alone when a running build is available.
Boundaries
- Runtime Automation owns local proof helpers, not engine DevAPI internals.
- Games own semantic commands and game-specific smoke scenarios.
ai_studio/quality/ owns acceptance rules such as player clarity or technical
behavior evidence.ai_studio/taskboard/ owns durable task state.- Keep release builds automation-free unless the project explicitly changes that
policy.
Validation
py -3.12 -m pytest ai_studio/runtime_automation
node ai_studio/architecture_map/validate_map.mjs
