laravel-patterns

Organize Laravel applications into layered architectures with service bindings and repositories.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/SOLEROM/cldlab --skill laravel-patterns-solerom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-patterns
Source: https://github.com/SOLEROM/cldlab/tree/main/ecc/ref_claude/skills/laravel-patterns
Command: npx skills add https://github.com/SOLEROM/cldlab --skill laravel-patterns-solerom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel projects often spiral into tangled codebases as they grow. This Skill provides a disciplined, scalable architecture pattern guide to structure routes, controllers, services, models, queues, events, and API resources for production apps.

Core Features & Use Cases

  • Clear layering: HTTP controllers, service/actions, and domain models to keep business logic separate from web concerns.
  • Robust API design: resources, pagination, and typed models to deliver consistent responses.
  • Production-grade organization: binding configuration, repositories, queues, and caching to support scalable apps.

Quick Start

Organize a Laravel project with clear layers (HTTP, services, and models), enable service container bindings, and adopt repository and resource patterns to enable maintainable growth.

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 for clean architecture and maintainability?

To build a Laravel application with clean architecture, enforce clear layering by separating HTTP controllers, service or action classes, and domain models. This isolates business logic from web concerns and supports maintainable growth.

What is the best way to design scalable APIs with Laravel Eloquent models?

Designing scalable APIs with Laravel involves using API resources, pagination, and typed Eloquent models to deliver consistent, resource-based responses. This approach keeps endpoints robust and maintainable.

When do I need to use repository and service patterns in Laravel?

You need repository and service patterns in Laravel when organizing production-grade apps that require scalable architectures. Applying these patterns alongside explicit service container bindings enables maintainable growth.

How do I organize queues, events, and caching in a production Laravel app?

Organize queues, events, and caching in a production Laravel app by applying a disciplined architecture pattern guide. Conventional project structure and explicit service bindings ensure these components support scalable applications.

Can I use this architecture approach for existing Laravel projects with tangled codebases?

Yes, you can apply this architecture approach to existing Laravel projects with tangled codebases. It provides a disciplined guide to refactor routing, controllers, and models into clear layers, separating business logic from web concerns.