laravel-11-12-app-guidelines

Laravel 11/12 best practices involve using Eloquent for data access, Form Requests for validation, and standard routing conventions to maintain a consistent project structure. You should also enforce code formatting with Pint to ensure consistency across your web development workflow.

To start a feature with Inertia and React, follow established patterns for component creation, routing, and styling. You can use the search-docs command to find specific guidance on implementing workflows like user authentication flows within your existing full-stack setup.

Yes, this workflow supports API-only projects alongside full-stack setups. It automatically detects your project stack and provides specific guidelines for using Docker Compose or Sail for container management during your Laravel development workflow.

Yes, you can use Tailwind v4 and Livewire. The guidelines support diverse frontend stacks including Blade, Vue, and Livewire, ensuring your component creation and styling follow the correct conventions for your specific Laravel configuration.

The best way to debug Laravel is by leveraging Boost MCP tools like search-docs, list-artisan-commands, and tinker. These tools help you search documentation, discover available commands, and run code interactively for efficient debugging.

You configure PHPUnit and Pint by following the enforced testing and formatting best practices provided in the guidelines. This ensures your Laravel 12 codebase maintains consistent styling and reliable test coverage throughout the development cycle.