Laravel architecture

Follow Laravel conventions first. When the framework documents an idiomatic way to do something, use it — only deviate when there is a clear reason. The rules below either reinforce a Laravel convention or document a project-level layer that sits on top of it.

This skill covers the request-lifecycle layer: how a request flows from controller through Form Request to Action, plus the global helper functions used along the way. It also documents project-wide conventions for configuration, Artisan commands, and naming of framework-managed classes.

1. Controllers — invokable single-action

Each controller has exactly one __invoke() method. No resource controllers.

Directory layout per resource: