laravel-patterns

Scaffold Laravel projects with layered controllers, services, models, and resources.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill laravel-patterns-richardnpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-patterns
Source: https://github.com/richardnpaul/everything-vscode-copilot/tree/main/.github/skills/laravel-patterns
Command: npx skills add https://github.com/richardnpaul/everything-vscode-copilot --skill laravel-patterns-richardnpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel project scaffolding and architectural guidance to build scalable, maintainable Laravel apps by providing clear layer boundaries, consistent patterns, and reusable components across controllers, services, models, and resources.

Core Features & Use Cases

  • Production-grade Laravel architecture patterns for organizing controllers, services, actions, and models.
  • Structured project layout guidance, routing strategies, route-model binding, and API Resource usage for robust web apps and APIs.
  • Practical examples covering migrations, form requests, caching, events, queues, and dependency injection to ensure maintainable codebases.

Quick Start

Scaffold a Laravel project using the recommended architecture pattern to implement a feature module with Controllers, Services, and Resources.

Frequently Asked Questions about laravel-patterns

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

FAQPage Schema
What's the best way to structure a scalable Laravel application architecture?

To structure a Laravel application, organize feature modules using Controllers for HTTP handling, Services for business logic, and API Resources for data transformation. Apply route-model binding and form requests to maintain consistent, scalable patterns across web apps and APIs.

How do I organize Laravel services and controllers for large APIs?

Yes, Laravel architecture patterns support queues, events, and caching by integrating them within service layers and actions. This ensures scalable resource handling and clear boundaries while managing asynchronous tasks and persistent data across your application.

Do I need dependency injection for Laravel service patterns?

You need dependency injection for Laravel service patterns to properly resolve and bind configurations across controllers and services. Using binding configurations ensures that layer boundaries remain intact and components stay reusable throughout the project structure.

When should I use API resources versus direct model returns in Laravel?

You should use API resources in Laravel when building scalable APIs that require clear layer boundaries and efficient resource handling. Returning models directly couples your database structure to your API output, whereas API resources provide a consistent transformation layer.