laravel-architecture

Guide Laravel backend architecture with senior patterns for modules, services, and multi-tenancy.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/nikhil02032022/AICRM --skill laravel-architecture-nikhil02032022
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-architecture
Source: https://github.com/nikhil02032022/AICRM/tree/main/.github/skills/laravel-architecture
Command: npx skills add https://github.com/nikhil02032022/AICRM --skill laravel-architecture-nikhil02032022

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers often struggle to pick and apply Laravel patterns that deliver scalable, maintainable backends across multi-tenant environments.

Core Features & Use Cases

  • Pattern selection and binding strategies for actions, services, repositories, pipelines, and observers.
  • Eloquent optimizations and multi-tenancy controls to prevent N+1 queries and data leakage.
  • Security hardening and job topology guidance, plus integration with Horizon and Sanctum.
  • Use Case: Design a CRM module boundary with a clear service layer and isolated tenancy.

Quick Start

Execute a design review: map the current Laravel module boundaries to service providers, repositories, and pipelines and propose improvements in 1-2 pages

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 scalable Laravel backend for multi-tenant applications?

Structure scalable Laravel backends by mapping module boundaries to service providers, repositories, and pipelines. This approach isolates tenancy, enforces clear service layers, and prevents data leakage across multi-tenant environments.

What's the best way to prevent N+1 queries and data leakage in Eloquent?

Prevent Eloquent N+1 queries and data leakage by applying guarded Eloquent patterns and multi-tenancy controls. These optimizations enforce secure data access and efficient query execution across large Laravel applications.

How do I select and bind Laravel design patterns for actions and services?

Select and bind Laravel design patterns using scalable service-provider architecture. This guides the strategic application of actions, services, repositories, pipelines, and observers to ensure maintainable backend structures.

When do I need readonly DTOs and enums in Laravel architecture?

Use readonly DTOs and enums in Laravel architecture when enforcing PHP 8.2+ features. They provide strict data integrity and scalable service-provider bindings for complex backend processing workflows.

Can I integrate Horizon and Sanctum for Laravel job topology and security?

Integrate Horizon and Sanctum to manage Laravel job topology and security hardening. This combination secures API authentication while optimizing background job processing across large applications.

How do I perform a Laravel module boundary design review?

Perform a Laravel design review by mapping current module boundaries to service providers, repositories, and pipelines. Propose structural improvements in a concise 1-2 page summary to enhance scalability.