laravel-telescopelisted

## Constraints - If the current project uses Laravel, also apply `@rules/laravel/laravel.mdc`, `@rules/laravel/architecture.mdc`, `@rules/laravel/filament.mdc`, and `@rules/laravel/livewire.mdc` --- ## Purpose Use this skill when you need to investigate a specific Laravel Telescope request, read its runtime data, find the same request directly in the Telescope database tables, and propose actionable optimizations. The goal is practical diagnosis from real telemetry, not generic performance advice. --- ## When to use Use this skill when the task asks for any of the following: - analyze output from a Telescope URL - inspect one concrete Telescope request in detail - map a Telescope UI request to DB records - verify request behavior from `telescope_entries` and related tables - propose optimization opportunities based on observed request/query/job/cache/log data --- ## When not to use Do not use this skill when: - the project does not use Laravel Telescope - no Telescope URL, request id, or filter context is available - the user only wants generic Laravel performance tips without Telescope evidence If Telescope UI or DB access is missing, continue with static analysis and clearly state limitations. --- ## Expected inputs The skill can work with: - Telescope URL (preferred) - request UUID / entry UUID - environment access (local, staging, production read-only) - DB credentials for Telescope storage - logs or screenshots exported from Telescope The skill should p