backend-parity

Audits, ports, and validates OpenGL and Metal render backends for feature parity.

8|Updated Oct 11, 2023
One-click install
npx skills add https://github.com/jakildev/IrredenEngine --skill backend-parity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend-parity
Source: https://github.com/jakildev/IrredenEngine/tree/main/.claude/skills/backend-parity
Command: npx skills add https://github.com/jakildev/IrredenEngine --skill backend-parity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain feature parity between the OpenGL (Linux/Windows) and Metal (macOS) render backends by scanning for deviations, porting missing side implementations, and validating parity before PRs.

Core Features & Use Cases

  • Detect drift between backends, port missing shaders, C++ render code, and wiring to ensure feature parity.
  • Support bidirectional parity work (OpenGL -> Metal and Metal -> OpenGL) with a clean build and smoke test on the lagging backend.
  • Drive parity through a structured workflow: audit, port, build, smoke-test, and PR handoff.

Quick Start

Identify the lagging backend, port the missing components, build the lagging preset, and smoke-test for parity.

Frequently Asked Questions about backend-parity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I maintain feature parity between OpenGL and Metal render backends?

Maintain feature parity between OpenGL and Metal render backends by scanning for deviations, porting missing shaders or C++ render code, and validating builds across macOS, Linux, and Windows through a structured audit, build, and smoke test workflow.

What causes render drift between graphics backends, and how do I detect it?

Detect render drift between graphics backends by auditing the lagging preset for missing shaders, C++ render code, and wiring components against the leading backend to identify feature deviations across macOS, Linux, and Windows.

Do I need a clean working tree and gh authentication to port graphics backends?

Porting graphics backends for parity requires a clean working tree, a configured lagging preset, and gh authentication to validate builds and smoke tests on the target backend before PR handoff.

Can I port OpenGL render code to Metal and vice versa bidirectionally?

Port render code bidirectionally between OpenGL and Metal backends by identifying the lagging backend, porting missing components, building the lagging preset, and smoke-testing to ensure feature parity before PR handoff.

What is the best way to validate graphics backend parity before a pull request?

Validate graphics backend parity before a PR by building the lagging preset, running a smoke test on the target backend, and ensuring both OpenGL and Metal render implementations pass feature parity checks across macOS, Linux, and Windows.