Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
GitHub Copilot
Gemini CLI+20 moreClaude CodeCursorCodex CLIGitHub CopilotGemini CLI
OpenClaw
Manus
Grok+17 agentsLaravel 12 Production Audit
It is designed to help Laravel developers, freelancers, agencies, students, and SaaS developers review an application before deployment.
$5.99
Laravel 12 Production Audit
Example session with this skill installed
I'm getting a 'Target class [App\Http\Controllers\OrderController] does not exist' error when I try to visit /orders. I've checked the file and it is definitely in the folder.
- Read your context and instructions
- Compiled the laravel 12 production
I have analyzed your routing configuration and the controller file structure. The error occurs because of a namespace mismatch between your route declaration and the file's actual location.
🐛 Bug Found
Severity:
High
Problem:
The application cannot resolve the OrderController when the /orders route is accessed.
Root Cause:
The controller file is located in app/Http/Controllers/OrderController.php, but the namespace inside the file is incorrectly set to namespace App\Controllers; instead of namespace App\Http\Controllers;.
Affected File:
app/Http/Controllers/OrderController.php
🔧 Fix
Open app/Http/Controllers/OrderController.php and update the namespace on line 3:
<?php
namespace App\Http\Controllers;
use App\Http\Controllers\Controller;
use Illuminate\Http\Request;
class OrderController extends Controller
{
// ... rest of the code
}
🧪 Test
- Open your browser and navigate to
/orders. - Expected result: The page loads the index view without the "Target class does not exist" error.
💡 Why This Happened
Laravel's autoloader relies on PSR-4 standards. If the namespace defined inside the PHP file does not match the actual folder structure, the RouteServiceProvider cannot locate the class, even if the file exists on the disk.
Next steps
- Run
composer dump-autoloadto ensure the class map is refreshed. - Verify your
web.phpuses the full class string or a proper use statement for the controller.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
Laravel 12 Production Audit
Laravel 12 Production Audit is a professional AI Skill designed to review Laravel applications before deployment.
It performs a structured production-readiness audit across security, performance, database usage, authentication, authorization, validation, configuration, APIs, file uploads, queues, caching, logging, dependencies, frontend assets, and deployment configuration.
Instead of simply listing random code problems, the Skill prioritizes findings by severity and explains:
• What is wrong • Where the problem is • Why it matters • How to fix it • How to verify the fix
AUDIT AREAS
✓ Production configuration ✓ Security review ✓ Authentication ✓ Authorization ✓ Routes ✓ Controllers ✓ Models & Eloquent ✓ Database & migrations ✓ N+1 query detection ✓ Performance review ✓ Validation ✓ Blade & frontend ✓ API security ✓ File uploads ✓ Queues & jobs ✓ Caching ✓ Logging & error handling ✓ Composer dependencies ✓ Vite/frontend configuration ✓ Deployment readiness
SEVERITY LEVELS
CRITICAL HIGH MEDIUM LOW INFO
The final report includes a production-readiness summary, must-fix issues, recommended improvements, and a practical deployment checklist.
IMPORTANT
This Skill uses evidence from the project being inspected. It does not invent vulnerabilities, files, routes, or test results.
It is designed to help Laravel developers, freelancers, agencies, students, and SaaS developers review an application before deployment.
Compatible with Laravel projects using common Laravel development workflows.
What it does
- Analyzes exact error messages to isolate the root cause across the Laravel stack.
- Inspects routing, controllers, models, and migrations to ensure architectural consistency.
- Identifies common Laravel pitfalls like mass assignment errors, 419 Page Expired (CSRF), and BindingResolutionExceptions.
- Provides a severity assessment (Critical to Low) to help prioritize tech debt and hotfixes.
- Generates precise code fixes with step-by-step verification instructions.
Frameworks & tools
PHP, Laravel, Eloquent ORM, Blade, Vite, Composer, and Artisan.
Why this beats prompting it yourself
Generic LLMs often hallucinate methods or suggest outdated Laravel 5 syntax. This skill follows a strict inspection workflow (Understand, Inspect, Diagnose, Fix) that forces the agent to verify file existence and class relationships before proposing a change, preventing "blind fixes" that break other components.
Use cases
- Fixing broken authentication flows or policy-based authorization failures.
- Debugging complex Eloquent relationship queries and N+1 performance issues.
- Resolving Vite manifest errors and asset compilation problems in the frontend.
- Tracing 404/405 routing errors to specific middleware or method mismatches.
Known limitations
Requires access to project files to be effective. Cannot access external databases to verify live production data.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean today
- Passed all security checks, Safe to install