Livewire Patterns

Apply Livewire rules only when the project uses Livewire. Detect the installed version and existing component conventions before changing components.

Component Boundaries

Keep Livewire components focused on one interactive surface. Move reusable business workflows into Actions or Services when logic grows beyond component state and UI orchestration.

A component may:

• hold UI state;
• validate user input;
• call Actions/Services;
• dispatch browser or Livewire events;
• render a focused view.

A component should not: