phoenix-liveview-essentials

Phoenix LiveView lifecycle management requires following strict patterns for mount/3, handle_params/3, and two-phase rendering to prevent common static vs connected render mistakes. This Skill enforces non-negotiable rules ensuring consistent @impl usage, safe assigns, and error handling across these phases.

To handle PubSub safely in Elixir LiveView, you must subscribe only when the socket is connected and handle broadcasts with proper event and info flow guidance. This ensures safe navigation of PubSub and timers without causing memory leaks or race conditions.

Yes, Phoenix LiveView requires explicit @impl usage for event handlers to satisfy lifecycle discipline and prevent subtle bugs. This Skill enforces mandatory patterns for handle_event, handle_info, and other callbacks to standardize module implementations.

To prevent rendering bugs during LiveView mount and handle_params, apply lifecycle clarity rules that separate static and connected rendering phases. This Skill enforces proper component composition, temporary assigns, and avoids heavy work in every phase to ensure safe rendering.

Your Phoenix LiveView might crash because subscriptions are not restricted to connected sockets or broadcasts are handled without proper error handling. This Skill provides PubSub and presence best practices, including safe broadcast navigation and timer management, to prevent these failures.