laravel-architecture

Guide Laravel architecture decisions with actions, DTOs, and builders.

Updated Aug 23, 2026

Search Tags:#architecture #patterns #laravel #best-practices #dto #actions #project-structure

Ready to run

npx skills add https://github.com/aarongmx/FacturacionLoop --skill laravel-architecture-aarongmx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel-architecture
Source: https://github.com/aarongmx/FacturacionLoop/tree/main/.ai/skills/laravel-architecture
Command: npx skills add https://github.com/aarongmx/FacturacionLoop --skill laravel-architecture-aarongmx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides high-level guidance for Laravel architecture, helping teams decide patterns, organize code, and enforce best practices across large projects.

Core Features & Use Cases

Core Concepts: philosophy, principles, and decision trees that steer project structure and pattern selection (Actions, DTOs, Custom Query Builders, and Services).
Decision Guidance: when to use actions vs form requests, DTOs, value objects, and services; how to structure directories and naming conventions for scalable apps.
Quick Reference: directory structure templates and governance for Laravel modules, with guidance on HTTP/Web vs API structures.

Quick Start

Outline a Laravel project structure following the Action pattern and DTO-based design.

Frequently Asked Questions about laravel-architecture

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

FAQPage Schema

How do I structure a Laravel project using actions and DTOs for better maintainability?▼

To structure a Laravel project using actions and DTOs, implement clear separation of concerns with strict typing and dedicated directory templates. This enforces pattern-based guidance for scalable, maintainable applications.

When should I use Laravel actions vs form requests in my application architecture?▼

Use Laravel actions vs form requests based on architectural decision trees that enforce clear separation of concerns. Actions handle core business logic execution, while form requests manage validation, ensuring strict typing and scalable project structure.

What is the best way to organize directories and naming conventions for scalable Laravel apps?▼

The best way to organize directories for scalable Laravel apps is by applying pattern-based governance and clear separation of concerns. Use directory structure templates to separate HTTP/Web and API modules, enforcing strict naming conventions.

How do DTOs and value objects improve Laravel architecture and project structure?▼

DTOs and value objects improve Laravel architecture by enforcing strict typing and clear separation of concerns. They encapsulate data transfer logic, guiding pattern-based decisions that keep large project structures maintainable and scalable.

Does this architectural guidance apply to both Laravel HTTP/Web and API structures?▼

Yes, this Laravel architectural guidance applies to both HTTP/Web and API structures. It provides specific directory structure templates and governance to ensure pattern-based guidance and clear separation of concerns across different application types.

When should I not use the Action pattern in my Laravel project?▼

You should reconsider the Action pattern when architectural decision trees indicate simpler form requests or services suffice. Overusing actions without strict typing and clear separation of concerns can unnecessarily complicate smaller Laravel project structures.