Engineering
laravel-11-12-app-guidelines avatar

laravel-11-12-app-guidelines

Standardized workflow and guidelines for Laravel 11/12 application development, including stack detection, dependency management, and integration with Laravel Boost tools.

Introduction

This skill provides a comprehensive operational framework for developers and AI agents working within the Laravel 11 and 12 ecosystems. It is designed to ensure consistency across diverse project configurations, ranging from API-only backends to complex full-stack applications utilizing Inertia.js, Livewire, and modern frontend tooling like Tailwind CSS v4. The skill instructs agents to prioritize local project documentation, specifically referencing AGENTS.md or project-level docs, and utilizes intelligent stack detection to adapt commands for Docker/Sail or host-native environments.

  • Automated stack detection for composer.json, package.json, and container configurations to prevent command errors.

  • Enforces strict Laravel 11/12 structural conventions, including routing, middleware, and service provider management in the bootstrap directory.

  • Integrates Laravel Boost MCP tools for advanced documentation searching, artisan command inspection, and database debugging.

  • Promotes best practices such as utilizing Form Requests for validation, leveraging Eloquent relationships over raw queries, and maintaining clean migrations.

  • Supports various frontend paradigms including Inertia with React, Vue, and Blade, while emphasizing specific patterns for state management and asset handling.

  • Facilitates automated code quality checks via PHPUnit and Pint before finalizing feature implementation or bug fixes.

  • Always begin by inspecting repository-specific guidance in AGENTS.md to ensure compliance with existing project patterns.

  • Use the provided Laravel Boost MCP tools (search-docs, list-routes, tinker) to gather context before executing write operations.

  • When working with Tailwind v4, strictly follow the theme-based utility patterns provided in the instructions.

  • Always offer a full test suite run after performing minimal, context-specific unit or feature tests.

  • Maintain clear separation of concerns in API-only projects by avoiding frontend-related assumptions.

Repository Stats

Stars
56
Forks
15
Open Issues
1
Language
Shell
Default Branch
main
Sync Status
Idle
Last Synced
May 3, 2026, 02:17 AM
View on GitHub