laravel-patterns

Outline scalable Laravel application patterns for routing, controllers, services, and data access.

1|Updated Jan 30, 2021
One-click install
npx skills add https://github.com/fideguch/my_dotfiles --skill laravel-patterns-fideguch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-patterns
Source: https://github.com/fideguch/my_dotfiles/tree/main/claude/skills/laravel-patterns
Command: npx skills add https://github.com/fideguch/my_dotfiles --skill laravel-patterns-fideguch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured blueprint for building production-ready Laravel applications by defining clear layering, routing, controllers, services, and data access patterns.

Core Features & Use Cases

  • Layered architecture: Controllers, Services, and Models collaborating to separate concerns.
  • Eloquent ORM usage with relationships, scopes, and repositories for clean data access.
  • Use Case: Build a scalable API with resources, queues, and caching for high-traffic apps.

Quick Start

Set up a conventional Laravel layout (Controllers, Services, Resources) and begin wiring routes to actions.

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 scalable Laravel application with controllers and services?

Structure scalable Laravel applications by separating concerns into HTTP controllers, services, and models. This layered architecture keeps routing, data access, and business logic cleanly organized for production-ready apps.

What is the best way to organize Eloquent usage and data access in Laravel?

Organize Eloquent data access by using model relationships, scopes, and repositories. This pattern ensures clean data retrieval and separates database logic from your HTTP controllers and services.

Can I use Laravel service bindings and actions for complex routing?

Yes, you can wire routes directly to actions and use service bindings for dependency injection. This conventional Laravel project structure specifies clear patterns for organizing complex application workflows.

Does this Laravel architecture pattern support high-traffic APIs with queues and caching?

This architecture pattern applies directly to building scalable APIs with resources, queues, and caching. It is designed for high-traffic apps needing organized layering and efficient data processing.

When should I implement a layered architecture in my Laravel project?

Implement a layered architecture when your Laravel project needs organized separation between HTTP controllers, services, and models. It provides a structured blueprint essential for production-ready, maintainable applications.