laravel-optimization

To audit a Laravel module for performance bottlenecks like N+1 queries, the skill scans a specified module path under app_modules or packages. It detects antipatterns such as unbounded gets, missing caches, and fat controllers to generate a concrete, phased optimization plan.

The best way to plan Laravel optimization safely is by generating a self-contained, agent-ready plan that includes a Phase 0 baseline gate. This skill assesses performance issues and delegates planning to enforce strict validation rules, ensuring a single failing test acts as a hard stop.

Finding missing caches and unbounded gets in Laravel application code requires auditing the specific module path. This skill surfaces these common performance antipatterns alongside sync observers and route closures, then delegates to feature-planning to produce an actionable optimization plan.

Yes, you can use this Laravel performance audit on composer packages. The skill applies to module paths under app_modules or packages, allowing it to effectively audit both application code and package code for performance issues like N+1 queries and missing caches.

No, this Laravel optimization skill does not execute code fixes or optimizations. It focuses entirely on assessment and planning, generating a self-contained, phased optimization plan that delegates to the feature-planning skill to enable safe, auditable improvements.

A Laravel optimization plan has a hard stop at Phase 0 if a single baseline test fails. This strict validation rule is enforced during the planning phase to prevent unsafe modifications, ensuring the current codebase is stable before applying any phased optimizations.