What problem does it solve? Teams and AI agents working on a Laravel codebase often guess at project conventions, producing inconsistent code when the app has already committed to specific patterns (e.g., inline validation vs Form Requests, Action classes vs fat controllers). This Skill systematically analyzes how the application is actually written and records those conventions as durable, path-scoped rules in .ai/rules so every agent and teammate follows the same style. ## Core Features & Use Cases - Systematic convention sweep: Works through a ~49-dimension checklist covering validation, controllers, authorization, Eloquent models, architecture, frontend, database, testing, and API responses, with grep hints per dimension. - Architecture mapping: Maps non-default app/ directories (Actions, Services, DTOs, Queries, domain modules) and records structural patterns and deliberate absences (e.g., no repository layer). - Conflict and evidence handling: Requires at least 3 consistent examples per convention, reports genuinely mixed patterns as conflicts instead of picking a winner, and skips framework defaults and tool-owned formatting (Pint, Rector). - Rule recording: Records approved conventions via the Boost record-rule MCP tool, scoped to precise globs, with a manual fallback when rules are disabled. - Use Case: After inheriting a Laravel app, run the sweep to discover it uses invokable controllers, spatie/laravel-data DTOs, and legacy magic accessors, then record those as rules so future generated code matches the existing style. ## Quick Start Ask the agent to analyze this Laravel project's conventions and record them as rules in .ai/rules.
