laravel-expert

Review Laravel 11/12+ code for architecture, security, and PSR compliance.

Updated May 11, 2026

Search Tags:#architecture #refactoring #api #php #backend #laravel

Ready to run

npx skills add https://github.com/irizqi/agent-skills --skill laravel-expert-irizqi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel-expert
Source: https://github.com/irizqi/agent-skills/tree/main/skills/laravel-expert
Command: npx skills add https://github.com/irizqi/agent-skills --skill laravel-expert-irizqi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of maintaining high-quality, scalable, and secure Laravel codebases by enforcing modern architectural standards and best practices.

Core Features & Use Cases

Architectural Guidance: Enforces clean code principles like thin controllers, service-oriented architecture, and proper dependency injection.
Code Quality & Security: Provides expert-level reviews for database interactions, authentication, and API development to prevent common vulnerabilities.
Use Case: Use this skill when refactoring a legacy controller into a service-based architecture or when designing a new API endpoint that requires robust validation and secure authorization.

Quick Start

Use the laravel-expert skill to review my current controller implementation and suggest a refactored version using service classes and form requests.

Frequently Asked Questions about laravel-expert

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

FAQPage Schema

How do I refactor a legacy Laravel controller into a service-oriented architecture?▼

To refactor a legacy Laravel controller into a service-oriented architecture, move business logic into dedicated service classes, keep controllers thin, and apply proper dependency injection for PSR-compliant, testable PHP code.

What is the best way to structure a secure Laravel API endpoint?▼

The best way to structure a secure Laravel API endpoint is to use form requests for robust validation, implement secure authorization, and optimize database interactions to prevent common vulnerabilities during API development.

Does this approach support modern Laravel 11 and 12+ applications?▼

Yes, this approach supports modern Laravel 11 and 12+ applications by enforcing current framework conventions, ensuring database optimization, and providing expert architectural guidance for maintainable backend code.

How do I enforce clean code and dependency injection in PHP backend development?▼

To enforce clean code and dependency injection in PHP backend development, apply service-layer structuring, use thin controllers, and ensure your codebase follows PSR-compliant, testable standards for production-ready applications.

When do I need service-layer structuring for my Laravel codebase?▼

You need service-layer structuring for your Laravel codebase when maintaining high-quality, scalable, and secure applications, or when moving complex business logic out of controllers to ensure long-term maintainability.

What are the limitations of using thin controllers for complex backend logic?▼

Thin controllers alone cannot handle complex backend logic effectively; without service-oriented architecture, they become bloated and difficult to test, making database optimization and secure authorization harder to maintain.