Laravel Excellence Prover Connector for AI agents.

It is a capability that acts as a senior Laravel mentor for your AI agent, ensuring it writes high-quality, production-ready code that follows best practices.

It scans your code for lazy-loading issues in loops or Blade views and forces the agent to use eager loading like with() instead.

Yes, it specifically checks for mass assignment vulnerabilities by ensuring your agent uses $request->validated() and explicit $fillable arrays.

It doesn't change the speed of the AI, but it significantly reduces the time you spend fixing bugs and refactoring messy code after the AI finishes.

The capability will flag it as a violation and tell the agent to move the business logic into a dedicated Service or Action class.

Yes, you can use it to audit existing code or ensure that all new features added to your application meet your team's quality standards.

No. The agent writes the code. The capability VALIDATES that the code meets senior-level Laravel standards. query optimization, framework idioms, responsibility separation, mass assignment protection, and architectural compliance. It catches the five failure modes before the code is committed.

Prompt instructions are suggestions. agents routinely ignore 'use eager loading' or 'validate with FormRequests.' Capability calls are obligations. the agent must fill every field. The engine has 22 consistency rules that catch specific anti-patterns: N+1, raw SQL without justification, env() in app code, unbounded get()/all(), synchronous heavy I/O, dd()/dump() in production, magic values, vague claims like 'follows best practices', and platitude conclusions. A prompt cannot enforce these. a capability schema can.

Because N+1 is the single most common and damaging performance anti-pattern in Laravel. A beautifully architected application with clean controllers and perfect FormRequests will still crash under load if every Blade view triggers 100 lazy-loaded queries. N+1 is checked first because no amount of clean architecture compensates for a database under siege.

Yes. When refactoring legacy code, call the capability to validate each change against excellence standards. The capability catches the same patterns regardless of whether you're writing new code or improving old code. Start with the most critical pivot: enable Model::preventLazyLoading() to surface all N+1 issues, then progressively extract logic from fat controllers into Services, add FormRequests, and define $fillable.