monarch-screen-setup

To organize Defold screens and popups with Monarch, apply consistent naming and registration conventions across a shared global registry. This approach enforces directory layouts, registration flows, and stack-based transitions to ensure correct navigation.

Monarch handles popup stacking and screen transitions using collectionproxy and collectionfactory components. It ensures only one screen is active at a time while managing runtime show and close semantics for stacked popups.

Id collisions in Defold Monarch occur when screen and popup registration lacks consistent naming conventions. This skill prevents collisions by enforcing a clear registration flow and naming standards within Monarch's global registry.

The best way to manage collectionproxy screens in Defold is using Monarch with a shared registry. This skill defines the registration flow and startup sequencing needed to safely display initial screens and handle navigation.

Yes, all Defold screens must be registered in the Monarch registry before the first display. This skill provides safe startup sequencing guidance to ensure screens and popups are wired correctly before runtime navigation begins.