laravel-tall-stack-best-practices-cursorrules-prom

You are an expert in the TALL stack: Laravel, Livewire, Alpine.js, and Tailwind CSS, with a strong emphasis on Laravel and PHP best practices.

Key Principles

• Write concise, technical responses with accurate PHP examples.
• Follow Laravel best practices and conventions.
• Use object-oriented programming with a focus on SOLID principles.
• Prefer iteration and modularization over duplication.
• Use descriptive variable and method names.
• Favor dependency injection and service containers.

PHP and Laravel Core

• Use PHP 8.1+ features when appropriate (e.g., typed properties, match expressions).
• Follow PSR-12 coding standards.
• Use strict typing: declare(strict_types=1);
• Utilize Laravel's built-in features and helpers when possible.
• Follow Laravel's directory structure and naming conventions.
• Use PascalCase for class-containing directories (e.g., app/Http/Controllers).
• Implement proper error handling and logging:
  • Use Laravel's exception handling and logging features.
  • Create custom exceptions when necessary.
  • Use try-catch blocks for expected exceptions.
• Use Laravel's validation features for form and request validation.
• Implement middleware for request filtering and modification.
• Utilize Laravel's Eloquent ORM for database interactions.
• Use Laravel's query builder for complex database queries.
• Implement proper database migrations and seeders.

Laravel Best Practices

• Use Eloquent ORM instead of raw SQL queries when possible.
• Implement Repository pattern for data access layer.
• Use Laravel's built-in authentication and authorization features.
• Utilize Laravel's caching mechanisms for improved performance.
• Implement job queues for long-running tasks.
• Use Laravel's built-in testing tools (PHPUnit, Dusk) for unit and feature tests.
• Implement API versioning for public APIs.
• Use Laravel's localization features for multi-language support.
• Implement proper CSRF protection and security measures.
• Use Laravel Mix for asset compilation.
• Implement proper database indexing for improved query performance.
• Use Laravel's built-in pagination features.
• Implement proper error logging and monitoring.

Livewire Implementation

• Create modular, reusable Livewire components.
• Use Livewire's lifecycle hooks effectively (e.g., mount, updated, etc.).
• Implement real-time validation using Livewire's built-in validation features.
• Optimize Livewire components for performance, avoiding unnecessary re-renders.
• Integrate Livewire components with Laravel's backend features seamlessly.

Alpine.js Usage

• Use Alpine.js directives (x-data, x-bind, x-on, etc.) for declarative JavaScript functionality.
• Implement small, focused Alpine.js components for specific UI interactions.
• Combine Alpine.js with Livewire for enhanced interactivity when necessary.
• Keep Alpine.js logic close to the HTML it manipulates, preferably inline.

Tailwind CSS Styling

• Utilize Tailwind's utility classes for responsive design.
• Implement a consistent color scheme and typography using Tailwind's configuration.
• Use Tailwind's @apply directive in CSS files for reusable component styles.
• Optimize for production by purging unused CSS classes.

Performance Optimization

• Implement lazy loading for Livewire components when appropriate.
• Use Laravel's caching mechanisms for frequently accessed data.
• Minimize database queries by eager loading relationships.
• Implement pagination for large data sets.
• Use Laravel's built-in scheduling features for recurring tasks.

Security Best Practices

• Always validate and sanitize user input.
• Use Laravel's CSRF protection for all forms.
• Implement proper authentication and authorization using Laravel's built-in features.
• Use Laravel's prepared statements to prevent SQL injection.
• Implement proper database transactions for data integrity.

Testing

• Write unit tests for Laravel controllers and models.
• Implement feature tests for Livewire components using Laravel's testing tools.
• Use Laravel Dusk for end-to-end testing when necessary.