Laravel Development Settings Laravel Package

Accessibility testing and WCAG compliance for Laravel Livewire + Blade applications. Use when building or reviewing Blade templates, Livewire components, forms, navigation, modals, or any user-facing HTML. Also trigger when the user mentions WCAG, screen readers, keyboard navigation, a11y, or accessible UI. Invoke proactively when creating any new user-facing component — accessibility should be built in from the start, not bolted on after. If a Blade or Livewire file is being created or significantly modified, this skill applies.

Architecture review for Laravel monolith applications using DDD-lite organization. Use when evaluating application structure, planning domain boundaries, reviewing separation of concerns, assessing scalability, planning feature architecture, or making technology decisions within a Laravel monolith. Also trigger when discussing Actions vs Services, domain organization, or how to structure a new feature.

Generate commit messages using Conventional Commits + Gitmoji format. Use this skill whenever creating, drafting, or suggesting git commit messages — including /commit commands, pre-commit hooks, bulk commits, and any context where a commit message is being composed. Always invoke this skill before writing a commit message.

Solve Laravel development problems with enforced clean code patterns, PHP code style, and linter compliance. Use when writing or modifying ANY PHP or Blade file: fix N+1 Eloquent queries, create middleware, build Livewire components, refactor controllers, design models with relationships and scopes, write Pest tests, create migrations, write artisan commands, fix Pint linter errors, or implement any Laravel-specific pattern. This skill applies to ALL PHP and Blade changes in Laravel projects — even small edits. Also trigger when discussing Laravel architecture, Eloquent design, or PHP conventions used in this project.

PostgreSQL query optimization and database design for Laravel Eloquent projects. Use when writing complex queries, optimizing slow Eloquent queries, designing migrations, debugging query performance, working with PostgreSQL-specific features (JSONB, arrays, CTEs, window functions), or analyzing execution plans.

Safe refactoring of Laravel PHP code following clean code principles. Use when reducing complexity in controllers, models, or services, extracting Actions from bloated classes, breaking up god models into Concerns traits, improving testability, or simplifying conditional logic. Also trigger when discussing code smells, technical debt reduction, or structural improvements in Laravel code.

Security auditing for Laravel applications handling PII and healthcare data (HIPAA). Use when reviewing authentication/authorization flows, auditing data handling practices, checking for OWASP vulnerabilities in Laravel code, reviewing middleware security, assessing PII/PHI exposure, or evaluating compliance posture of a Laravel application. Also trigger when reviewing any endpoint that reads or writes user data, even if PII isn't explicitly mentioned — most user-facing endpoints handle some form of personal data. Invoke proactively when creating new API endpoints, form handlers, or data export features.