jpcaparas

Use API Resources with pagination and conditional fields; keep response shapes stable and cache-friendly

Evolve APIs safely using versioned DTOs/transformers, deprecations, and compatibility tests

Compose UIs with Blade components, slots, and layouts; keep templates pure and testable

Detect Sail/non‑Sail and print the right command pairs for your environment; verify dependencies and key services are reachable

Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness

Request effective code reviews—specify focus areas, provide context, ask for architectural feedback, reference Laravel conventions

Keep cyclomatic complexity low; flatten control flow, extract helpers, and prefer table-driven/strategy patterns over large switches

Replace hardcoded values with constants, enums, and configuration for maintainability; use PHP 8.1+ enums and config files

Reduce controller bloat using Form Requests for auth/validation, small Actions/Services with DTOs, and resource/single-action controllers

Create and register small, pure helper functions when they improve clarity; keep them organized and tested

Process large datasets efficiently using chunk(), chunkById(), lazy(), and cursor() to reduce memory consumption and improve performance

Write meaningful documentation that explains why not what; focus on complex business logic and self-documenting code