Agent Guidelines Laravel Package

code-reviewing

Review staged changes, feature branches, or an explicitly selected diff for concrete defects, regressions, and production risks. Use for code review and pre-commit or pre-merge assessment; report findings without applying fixes.

claude-code

laravel-best-practices-overlay

Apply the maintainer's selected design defaults when planning, writing, or reviewing new Laravel/PHP implementations and Blade PDF or email templates, including new code within existing files. Complements Laravel Boost; does not authorize convention-only rewrites of legacy code.

claude-code

laravel-permissions

Design and implement permission-based access control in Laravel applications using spatie/laravel-permission, Laravel Policies, FormRequest authorization, Eloquent visibility scopes, thin controllers, and frontend abilities. Use when adding or changing roles, permissions, resource access, record visibility, permission-aware forms, or authorization-related UI.

claude-code

lets-code

Apply execution rules when the AI writes or modifies code, preserving requirements, documentation, testing, and developer control over Git history.

claude-code

specification-driven-development

Plan, implement, or review new application features and comprehensive changes against a human-defined specification written before implementation. Routine small fixes and styling changes do not require this workflow.

claude-code

vue-frontend-best-practices

Apply the maintainer's frontend design defaults when planning, writing, or reviewing new Vue components and pages, including presentation, display values, toolbars, notifications, and localization. Follow the project's installed Vue/Nuxt version; does not authorize legacy UI redesigns.

claude-code