Laravel Project Patterns

Use this skill before editing Laravel project backend application code, local project tooling, Inertia React/Blade, React Email templates, or choosing tests. The references cover Laravel application code, routes, config, localization, bootstrap/public entrypoints, seeders, root tooling, resources/js Inertia React, resources/views Blade shells, resources/react-email mail templates, schema-backed code, migrations, Eloquent models, factories, resources, actions, console commands, middleware, listeners, policies, support classes, and Pest tests across unit, integration, feature, and architecture suites, with Browser guidance only when a real browser suite is introduced.

This skill is derived from the live repository. When repository evidence disagrees with a generic Laravel habit, the repository wins. Read the exact files in the touched path first, then load the matching reference here, then compare with the nearest sibling module before writing code or tests. For controller-test work, start at references/tests/Feature/Http/Controllers/README.md; it is the central map for action order, web/API transport differences, nested Workspace boundaries, validation datasets, redirects/toasts, and public-id contracts.

Examples in this skill and its references are canonical synthetic examples. They merge compatible patterns observed across modules and intentionally use placeholder names such as Workspace, ParentRecord, ChildRecord, LeafRecord, RelatedRecord, Actor, ExampleInput, and ExampleResource. Do not replace those examples with real module/entity names.

First Pass