oni-ai-tests

name	oni-ai-tests
description	Prompt pack for manual ONI live E2E validation using explicit OS screenshots and liveness checks around every desktop input action.

ONI AI Tests Skill

Goal

Run live ONI end-to-end validation as the direct driver, with deterministic evidence for every action.

Hard Rules

• Do not use one-shot driver scripts or step-runner scripts.
• Execute each step as explicit shell commands.
• Use OS-level screenshots via screencapture, not API-only evidence.
• Before each input action: take screenshot + check liveness.
• After each input action: take screenshot + check liveness.
• Exactly one input action per step.

Step Template (must follow every time)

1. screencapture -x <step_pre_png>
2. curl -sS http://127.0.0.1:8766/health
3. uv run oni-input <single_action>
4. screencapture -x <step_post_png>
5. curl -sS http://127.0.0.1:8766/health

Suggested Session Layout

• Session directory: /tmp/oni-ai-tests/<session-id>/
• Naming:
  • 001_pre.png, 001_post.png
  • 002_pre.png, 002_post.png
  • ...

Input Actions

• uv run oni-input click --x <x> --y <y> --button left
• uv run oni-input drag --x1 <x1> --y1 <y1> --x2 <x2> --y2 <y2> --duration 0.4
• uv run oni-input press --key <key> --count 1
• uv run oni-input type --text "<text>"
• uv run oni-input hotkey <k1> <k2> ...

Liveness Requirements

• GET /health must return HTTP 200.
• If liveness fails, stop and resolve game/mod state before next step.
• If screenshot fails, stop and resolve macOS Screen Recording permission before next step.

Prompt Snippet

Use this prompt when running live sessions:

You are executing ONI live E2E manually. For every single desktop input action, do: pre OS screenshot, pre liveness check, one input action, post OS screenshot, post liveness check. Never skip evidence gates and never batch multiple inputs in one step.