jpcaparas

Prevent N+1 queries by eager loading; enable lazy-loading protection in non-production; choose selective fields

Provide comprehensive context in prompts—files, errors, Laravel version, dependencies, and monorepo details—for accurate AI responses

Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely

Use reportable/renderable exceptions, structured logs, and channel strategy for observability and graceful failures

Store and serve files via Storage; set visibility, generate URLs, and handle streaming safely

Move validation and authorization into Form Requests; use rule objects, custom messages, and nested data handling to keep controllers slim

Operate Horizon with confidence—naming, tags, concurrency, failure handling, actionable metrics, and dashboards

Use the HTTP client with sensible timeouts, retries, and backoff; capture context and handle failures explicitly

Use interfaces and dependency injection to decouple code; bind implementations in the container

Build with i18n in mind from day one using Laravel translation helpers, JSON files, Blade integration, and locale management

Use Laravel-specific vocabulary—Eloquent patterns, Form Requests, API resources, jobs/queues—to get idiomatic framework code

Safe database change patterns; when to modify vs add migrations; always pair models with migrations and factories; seeding guidance