laravel-patterns

Overview of laravel-patterns skill

What laravel-patterns is for

The laravel-patterns skill helps you design Laravel apps with cleaner boundaries: controllers stay thin, business logic moves into services or actions, and data access stays predictable through models, scopes, and resources. It is most useful for backend teams building production APIs or web apps that need maintainability more than quick one-off scaffolding.

Who should use it

Use the laravel-patterns skill if you are building or refactoring a Laravel codebase and want a practical architecture guide for routing, Eloquent, queues, events, caching, and API responses. It fits developers who already know Laravel basics but want better structure for growth, team handoff, and less controller sprawl.

What makes it worth installing

Unlike a generic prompt, laravel-patterns gives you a reusable Laravel-specific mental model: request enters through HTTP, rules and authorization are enforced early, domain work is coordinated in services/actions, and expensive work is pushed to jobs or cached paths. That makes it a strong laravel-patterns for Backend Development when you need consistent implementation choices, not just idea generation.

How to Use laravel-patterns skill

Install and load the skill

Run the laravel-patterns install step with the directory tool you use for skills, for example: npx skills add affaan-m/everything-claude-code --skill laravel-patterns. After installation, open the skill entry file first so you can align your prompt with its architecture rules before asking for code.

Start with the right input shape

The best laravel-patterns usage starts with a concrete target: feature, route, model, or bug. Give the skill the current Laravel version, your layer boundaries, and the outcome you want. Strong input looks like: “Design a Laravel 11 order export flow using controller, action, job, and resource layers; keep validation in form requests; cache the report list; avoid fat controllers.”

Read the files that change output quality

For this laravel-patterns guide, prioritize SKILL.md and any examples it links to, then inspect the parts of your app that map to the pattern you want to change: app/Http/Controllers, app/Actions, app/Services, app/Models, app/Http/Resources, and config/*. If your repo has different conventions, adapt the pattern to those conventions instead of forcing a new structure everywhere.

Use it in a practical workflow

A good workflow is: describe the feature, ask for the architecture plan, then request the concrete code split by file. The skill works best when you ask it to decide where validation, authorization, query logic, async work, and API transformation belong. That is the part most likely to improve output quality versus a normal prompt.

laravel-patterns skill FAQ

Is laravel-patterns only for new projects?

No. The laravel-patterns skill is especially useful for existing apps that have grown controller-heavy or inconsistent. It can also help with incremental refactors, such as moving logic into actions or adding resources without rewriting the entire app.

How is it different from a normal Laravel prompt?

A normal prompt may produce working code, but laravel-patterns gives you stronger architectural defaults. It is better when you want the prompt to respect Laravel conventions around routing, Eloquent, queues, events, caching, and API resources instead of improvising per request.

Is it beginner-friendly?

Yes, if you already understand basic Laravel concepts like routes, controllers, models, and requests. It is less ideal if you need a crash course from zero, because the skill assumes you can recognize where the pattern should fit inside a real app.

When should I not use it?

Skip laravel-patterns if your task is a tiny throwaway script, a one-file prototype, or work in a non-Laravel stack. It is also not the right fit if your repo deliberately avoids layered architecture and you do not want to introduce more structure.

How to Improve laravel-patterns skill

Give it architectural constraints up front

The biggest quality gain comes from stating what must stay thin, what must be async, and what must be cached. Mention your Laravel version, team conventions, test framework, and any restrictions like “no new packages,” “must keep existing routes,” or “use form requests for validation.”

Ask for boundaries, not just code

The common failure mode is asking for a feature without saying where each responsibility belongs. Better laravel-patterns usage asks for controller, request, action/service, model scope, job, and resource responsibilities separately, which helps the skill produce a cleaner split for laravel-patterns for Backend Development.

Iterate after the first draft

If the first answer is too generic, ask for a tighter version with your actual model names, relationships, and sample payloads. The best laravel-patterns guide workflow is to refine the architecture first, then request file-level code, then ask for edge cases like authorization, pagination, idempotency, or queue retries.