polyphase_dev

To generate engine code following Polyphase conventions, draft a targeted code change plan that triggers a patch in the next commit. This enforces repository rules like RTTI/factory registration, asset versioning, editor guards, and VS project integration.

Debugging Polyphase Engine subsystems is handled through comprehensive workflows that navigate engine components efficiently. This approach ensures senior developers can isolate issues across subsystems while maintaining strict repository conventions and pattern-driven development.

Integrating a new subsystem with the Polyphase plugin API requires architecture guidance for subsystem integration. The Skill provides structured navigation across all Polyphase components to ensure proper VS project integration and asset versioning.

Manual VS project integration configuration is not needed during Polyphase Engine development. The Skill automatically enforces VS project integration alongside RTTI/factory registration and editor guards when you generate code or draft architecture changes.

Polyphase code generation fails factory registration checks when repository conventions are not met. The Skill enforces RTTI and factory registration patterns during code generation to ensure all generated components align with the engine's architectural requirements.