Laravel Best Practices Laravel Package

Record and maintain Architecture Decision Records in docs/adr/ using Nygard's Context, Decision, Consequences format plus an index. Use when writing or updating an ADR, superseding a decision, recording a hard-to-reverse architecture or product-architecture choice, or when a design session settles one.

Apply Laravel and PHP best-practice opinions when writing, reviewing, or refactoring PHP or Blade code. Complements Laravel Boost with control flow, Eloquent and money handling, architecture, domain naming, operational safety, Blade views, display formatting, toolbars, flash messages, and localisation. Follow existing project conventions and load only the topic rules relevant to the task. Excludes non-Laravel work and session workflow planning.

Scope substantial AI coding tasks, choose proportionate verification, recover stalled work, and hand off unfinished tasks. Use at the start of substantial implementation or when resuming work across sessions. Skip simple questions, trivial edits, and follow-ups within an already scoped task. Respects the host application's planning, permissions, effort controls, and task state.

Use this skill whenever you are about to fix a bug, regression, or any reported defect in a Laravel application. The skill enforces a strict red-green-refactor loop with the failing test written before the fix.