add-effect

To add a new transform effect, follow a comprehensive step-by-step checklist covering module creation, shader setup, post-effect integration, UI wiring, and build-system updates to ensure all components install correctly.

Integrating a post-process shader requires phase-driven workflow execution: creating the shader module, applying post-effect integration, wiring UI hooks, and registering lifecycle configuration across module and build phases.

UI wiring connects new transform effects to user interface controls, requiring you to register configuration parameters and preset support so the visual effect can be properly modulated and managed within the application.

Yes, updating the build system is required when adding a shader to register the new files, headers, and configuration parameters, ensuring the post-process effect compiles and integrates correctly across all pipeline phases.

The best way to scaffold files for a visual effect is using a modular checklist that systematically creates required code structures, headers, and build integrations in a single, repeatable process.

Transform effects fail to register when the phase-driven workflow is incomplete, often missing lifecycle configuration, build-system updates, or UI hooks required to connect the shader module to the post-process pipeline.