Laravel Patterns
Laravel architecture patterns: thin controllers, service layers, Eloquent done right, queues, events, caching, and API resources.
- What
- Laravel architecture patterns: thin controllers, service layers, Eloquent done right, queues, events, caching, and API resources.
- Cost
- Free
- Needs
- Use "Laravel Patterns" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a patterns skill for building Laravel applications that stay maintainable as they grow. Its core discipline is boundaries: thin controllers that delegate to service or action classes, Eloquent models with typed casts and scopes instead of query soup in controllers, explicit route bindings, and IO-heavy work pushed into queues with cached reads. It also covers events and listeners, API resources with pagination, and centralized configuration. The examples show the conventional Laravel layout (HTTP, services/actions, models) so new code lands where the next developer will look for it. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: pure guidance, nothing to install; assumes a working Laravel app and PHP basics; queue and cache sections assume you have workers and a cache driver configured. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Laravel Patterns" with your Muse. Prerequisites: a Laravel codebase to write or review (PHP project). Pure guidance skill, nothing to install. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/laravel-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Review this Laravel controller against these patterns: thin controllers, service layer, Eloquent usage." 3. For new features, ask: "Build this the Laravel way: thin controller, action class, typed Eloquent model, and an API resource." Tip: keep queue workers and cache drivers in mind; the skill assumes they exist. Safety: a skill is plain-text instructions; it runs nothing by itself. Never paste secrets into a chat, and review anything Muse proposes before it changes your code.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.