Mission control 3d visual regression
Skill MN755/Codex-Mission_Control/.codex/skills/mission-control-3d-visual-regression
An Open Source Platform For Building Projects With OpenAI's Codex, Claude CLI, And Other Coding LLMs Using Multi-Agent Swarms And Customizable Workflows. Runs On Windows, MacOS, And Linux.
npx -y skills add MN755/Codex-Mission_Control --skill mission-control-3d-visual-regressionAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Route 3D visual-regression and render-diff work through Mission Control with explicit evidence targets and scene-aware validation.
SKILL.md
1.9 KB, as published. Nobody here has run it
Mission Control 3D Visual Regression
Purpose
Use Mission Control to review 3D visual-regression work with explicit renders, tolerances, and evidence targets instead of the timeless engineering strategy known as “looks fine on my machine.”
The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.
Use when
- The repo needs render diffing, scene snapshots, or browser/engine visual checks.
- The user asks whether a 3D change broke output quality.
- Evidence matters more than developer confidence theater.
Workflow
- Confirm the repo has renderable spatial signals.
- Load the spatial feature catalog and choose the visual-regression bundle.
- Keep render generation, baseline selection, comparison, and evidence capture explicit.
- Surface blockers for missing renderers or browser harnesses.
Mission Control calls
Tools:
mission_control_get_spatial_feature_catalogmission_control_get_spatial_feature_bundlemission_control_get_workspace_tooling
Resources:
mission-control://projects/{project_id}/spatial/featuresmission-control://projects/{project_id}/spatial/features/{feature_id}mission-control://projects/{project_id}/workspace-tooling
Never do
- Do not claim visual regression exists if there is no baseline or diff evidence.
- Do not reduce scene validation to a single screenshot if the bundle expects multiple camera or output checks.
Failure and fallback
- If render infrastructure is missing, explain which evidence targets cannot be satisfied yet.
- If the repo is not actually renderable, route to a more relevant spatial bundle instead.
Example invocation
Use Mission Control to review the 3D visual-regression path and evidence requirements.