laravel-patterns

Guide Laravel developers in implementing scalable architecture patterns.

86|21|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/Jamkris/everything-gemini-code --skill laravel-patterns-jamkris
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-patterns
Source: https://github.com/Jamkris/everything-gemini-code/tree/main/skills/laravel-patterns
Command: npx skills add https://github.com/Jamkris/everything-gemini-code --skill laravel-patterns-jamkris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel-patterns solves the challenge of building scalable, maintainable Laravel applications by standardizing architecture patterns across controllers, services, models, and domain logic.

Core Features & Use Cases

  • Layered architecture: separates concerns between controllers, services, and models for clarity and testability.
  • Eloquent & routing patterns: guidance on models, relationships, scopes, and route organization for predictable behavior.
  • Queues, events, caching, and resources: practical patterns to handle background work and API responses at scale.

Quick Start

Structure your Laravel project with clear layer boundaries (HTTP/Controllers → Services/Actions → Models) and apply the recommended patterns to begin building a maintainable, scalable application.

Frequently Asked Questions about laravel-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Laravel application with a service layer for better maintainability?

To structure Laravel with a service layer, separate concerns across HTTP controllers, services or actions, and models. This layered architecture enforces boundaries, ensuring predictable behavior and making your application logic highly testable and scalable.

What are the best Laravel architecture patterns for organizing Eloquent models and routes?

The best Laravel architecture patterns for Eloquent and routing involve using typed models, relationship scopes, and organized route configurations. These patterns standardize data access and endpoint behavior, creating predictable domain logic across your web app or API.

When do I need a service layer in my Laravel application?

You need a service layer in Laravel when building scalable applications that require clear separation of concerns between controllers and models. It standardizes architecture, isolates domain logic, and improves testability for complex web apps and APIs.

How do I handle queues, events, and caching at scale in Laravel?

To handle queues, events, and caching at scale in Laravel, apply practical architecture patterns for background work and API responses. Structuring these components ensures efficient processing and scalable performance across your application.

Does this Laravel architecture approach work for both web apps and APIs?

Yes, this Laravel architecture approach works for both web apps and APIs. It guides developers in organizing controllers, services, models, and resources to enforce clean configuration and scalable domain logic across different application types.