Implements a requested Pixel Creator feature or behavior while respecting existing architecture, tests, documentation, and ADR contracts. Use for concrete implementation work after the relevant architecture has been understood.
Analyzes the existing Pixel Creator architecture before architecture-sensitive changes. Use when a task may affect Core, Runtime, Scene, Object, ResourceId, identity, components, transforms, the reactive Property System, rendering boundaries, serialization,…
Reviews existing Pixel Creator changes for correctness, architectural regressions, contract violations, unnecessary complexity, test coverage, and unintended side effects. Use when reviewing a diff, recent implementation, branch, or proposed change.
Runs and interprets Pixel Creator tests after implementation or when diagnosing a regression. Use when verification, test failures, regression analysis, or test-suite status is the primary task.