laravel-modules

Centralize routes, Livewire, Filament, and config patterns for modular Laravel projects.

6|1|Updated Oct 15, 2023
One-click install
npx skills add https://github.com/mozex/laravel-modules --skill laravel-modules
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-modules
Source: https://github.com/mozex/laravel-modules/tree/main/resources/boost/skills/laravel-modules
Command: npx skills add https://github.com/mozex/laravel-modules --skill laravel-modules

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide delivers detailed implementation patterns for mozex/laravel-modules, helping teams structure and activate a robust, modular Laravel project for real-world apps.

Core Features & Use Cases

  • Advanced routing patterns: organize module routes with custom groups, registrars, and per-concern files.
  • Component architecture: manage Livewire, Filament resources/pages, and Blade components across modules with minimal coupling.
  • Config merging and overrides: merge module and application configs and enable host overrides for views and resources.
  • Tooling and testing integration: align module service providers, morph maps, and auto-discovery with PHPStan, Pest, and PHPUnit for scalable quality.

Quick Start

Use this skill when wiring modular Laravel features across routes, Livewire components, Filament resources, and Inertia frontends in a large multi-module project.

Frequently Asked Questions about laravel-modules

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

FAQPage Schema
How do I structure routes and service providers in a modular Laravel application?

Yes, you can manage Livewire and Filament components across modules by applying a component architecture with minimal coupling. This pattern centralizes component sharing and enables host overrides for views and resources within your modular Laravel project.

What is the best way to merge module configurations in a large Laravel project?

You can align a modular Laravel architecture with PHPStan, Pest, and PHPUnit by integrating auto-discovery and morph maps within module service providers. This setup provides scalable quality tooling and testing guidance for multi-module applications.

Does modular Laravel architecture work with Inertia frontends and Filament resources?

Yes, modular Laravel architecture works with Inertia frontends and Filament resources. The zero-config orchestration supports wiring modular features across routes, Filament resources, pages, and Inertia frontends in large multi-module projects.

What are the limitations of managing morph maps and policies in a modular Laravel architecture?

Limitations of managing morph maps and policies in a modular Laravel architecture include the complexity of maintaining minimal coupling across modules. Centralizing policy integration and morph maps requires careful service provider alignment to avoid auto-discovery conflicts.