Conversation
Prove gameplay changes by recording a Play session as a PolySpatial .qrec, driving the game with simulated input, and answering from the recorded per-frame scene state. Resolves annotation references (<recording>#<id>) left on recordings. The recording-analyst sub-agent measures strictly from the recording; the Codex equivalent ships as a toml under references/.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
skills/polyspatial-playtest: record a Play session as a PolySpatial.qrec, drive the game with simulated input, then answer from the recorded per-frame scene state instead of a screenshot. Also resolves annotation references (<recording>#<id>) that people leave on recordings from the Editor.agents/recording-analyst.md: a Claude Code sub-agent the skill delegates measuring to. It only runs thepolyspatial_*query commands and never reads project source, so its answer is a measurement.references/codex-recording-analyst.tomlis the Codex equivalent, since Codex plugins cannot ship agents.Why
A screenshot shows what one frame looked like; the recording shows what every entity was on every frame and can be queried after Play mode ends. The skill makes the agent measure from the recording first and read code second.
Requirements
A running Editor with com.unity.pipeline and the
polyspatial_*recording commands (unity command --query polyspatial), provided by the PolySpatial package's recording CLI (in review). When they are missing the skill says so and falls back toeditor_playpluscapture_game_view.Verified
Installed as a project-scoped plugin against a Feel sample scene. Given an annotation reference and "how many turns did this cupcake rotate", the agent resolved the reference, pulled the rotation timelines, and reported 0.15 turns in the annotated frame, 6.94 in the surrounding burst and 13.89 over the recording, noting that the spin lives on the parent entity.
Same skill content as Unity-Technologies/skills#72.