The repository pattern places data-access operations behind a dedicated abstraction, giving application code a collection-like interface instead of coupling it directly to Eloquent or query details. It can help when persistence rules are complex, when multiple data sources must be coordinated, or when a well-defined domain boundary is valuable.

It should not be added automatically to every Laravel application. Eloquent already provides a capable data-access abstraction, and a repository that only mirrors basic Eloquent methods adds indirection without value. Introduce one when it simplifies real complexity, then keep its interface focused on meaningful application operations rather than generic CRUD wrappers.