laravel-conventions

Standardize Laravel backend conventions for routing, actions, form requests, policies, and Inertia.

9|1|Updated Jun 16, 2026
One-click install
npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill laravel-conventions-aratkruglik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-conventions
Source: https://github.com/AratKruglik/antigravity-sdlc/tree/main/plugins/laravel-plugin/skills/laravel-conventions
Command: npx skills add https://github.com/AratKruglik/antigravity-sdlc --skill laravel-conventions-aratkruglik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Laravel projects often suffer from divergent patterns across routes, controllers, requests, and policies. This skill consolidates the standard conventions to ensure uniform architecture and easier onboarding.

Core Features & Use Cases

  • Action pattern: prefer single-action invokable classes for business logic.
  • Form Requests: centralize validation and authorization checks.
  • Policies and Roles: consistent authorization semantics across models.
  • Routing and Inertia: standard routing practices and data passing with Inertia integration for Laravel + Vue projects.
  • Use Case: When starting a Laravel + Inertia project, apply these conventions to keep codebase predictable and maintainable.

Quick Start

Follow the Laravel conventions to structure new backend features with explicit routes, validated requests, and policy-based access controls.

Frequently Asked Questions about laravel-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are the standard Laravel backend conventions for routing and controllers?

Standard Laravel backend conventions enforce explicit route definitions and prefer single-action invokable classes for business logic to ensure uniform architecture and easier onboarding.

How do I structure validation and authorization in Laravel form requests and policies?

Laravel conventions centralize validation within form requests and implement consistent authorization semantics across models using policies, keeping controllers lean and standardizing access control.

Does this convention set support Inertia integration for Laravel and Vue projects?

Yes, these Laravel conventions include standard routing practices and proper data passing specifically for Inertia integration within Laravel and Vue projects to maintain predictable codebases.

What is the best way to standardize Laravel code structure for new feature development?

The best way to standardize Laravel code structure is applying explicit routes, typed models, form request validation, and policy-based access controls during feature development and code reviews.

When do I need typed models and policy-based authorization in Laravel?

You need typed models and policy-based authorization in Laravel to maintain consistent access control semantics across models and prevent divergent patterns when scaling application features.