Optimize from evidence rather than guessing: 1. Enable `DB::enableQueryLog()` or use Debugbar and capture the slow SQL, bindings, count, and timing. 2. Add migrations for indexes matching the real join and filter columns. 3. Replace N+1 loops with eager aggregates such as `withCount()`/`withSum()`, `joinSub()`, `whereExists()`, or an `addSelect` subquery. 4. Cache stable, frequently read results with `Cache::remember()` and tags where the backend supports them. 5. Configure read/write connect...
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add HoangNguyen0403/agent-skills-standard --skill laravel-database-expert --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Laravel Database Expert?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-laravel-database-expert-agent-skills-standard)More formats (shields.io, HTML) on the badges page.
Optimize from evidence rather than guessing:
1. Enable `DB::enableQueryLog()` or use Debugbar and capture the slow SQL, bindings, count, and timing.
2. Add migrations for indexes matching the real join and filter columns.
3. Replace N+1 loops with eager aggregates such as `withCount()`/`withSum()`, `joinSub()`, `whereExists()`, or an `addSelect` subquery.
4. Cache stable, frequently read results with `Cache::remember()` and tags where the backend supports them.
5. Configure read/write connections in `config/database.php` when read replicas are needed.
Use bindings for every raw expression; never concatenate user input into SQL. Verify the resulting query plan and response latency, because an index or cache that does not match the access path can add cost without fixing the bottleneck.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
