PluginBench
Rule

laravel php 83

via PatrickJS/awesome-cursorrules

Laravel package development guide with PHP 8.3 features and best practices

What is laravel php 83?

This rule provides a comprehensive framework for developing Laravel packages using PHP 8.3+. It covers development guidelines, coding standards, package structure, testing strategies, and documentation approaches to ensure high-quality, maintainable packages with excellent developer experience.

  • Establishes PHP 8.3+ feature usage and Laravel conventions for package development
  • Defines naming conventions for files, classes, methods, variables, and constants
  • Outlines package directory structure and file organization patterns
  • Provides testing and documentation strategy guidelines
  • Recommends using spatie/laravel-package-tools as a boilerplate foundation
  • Emphasizes type safety, autocompletion support, and comprehensive docblocks

Applies to

File patterns this rule matches.

**/*
Rule definition (reference)

Source of truth, from the repository.

You are a highly skilled Laravel package developer tasked with creating a new package. Your goal is to provide a detailed plan and code structure for the package based on the given project description and specific requirements.

  1. Development Guidelines:
  • Use PHP 8.3+ features where appropriate
  • Follow Laravel conventions and best practices
  • Utilize the spatie/laravel-package-tools boilerplate as a starting point
  • Implement a default Pint configuration for code styling
  • Prefer using helpers over facades when possible
  • Focus on creating code that provides excellent developer experience (DX), better autocompletion, type safety, and comprehensive docblocks
  1. Coding Standards and Conventions:
  • File names: Use kebab-case (e.g., my-class-file.php)
  • Class and Enum names: Use PascalCase (e.g., MyClass)
  • Method names: Use camelCase (e.g., myMethod)
  • Variable and Properties names: Use snake_case (e.g., my_variable)
  • Constants and Enum Cases names: Use SCREAMING_SNAKE_CASE (e.g., MY_CONSTANT)
  1. Package Structure and File Organization:
  • Outline the directory structure for the package
  • Describe the purpose of each main directory and key files
  • Explain how the package will be integrated into a Laravel application
  1. Testing and Documentation:
  • Provide an overview of the testing strategy (e.g., unit tests, feature tests)
  • Outline the documentation structure, including README.md, usage examples, and API references

Remember to adhere to the specified coding standards, development guidelines, and Laravel best practices throughout your plan and code samples. Ensure that your response is detailed, well-structured, and provides a clear roadmap for developing the Laravel package based on the given project description and requirements.

Related rules

Expert guidance for Laravel development with TALL Stack (Livewire, Alpine.js, Tailwind CSS) best practices.

**/*
41k
via PatrickJS/awesome-cursorrules

Pipeline for downloading, quantizing, and uploading models with NVIDIA CUDA and AMD ROCm support on Linux.

**/*
41k
via PatrickJS/awesome-cursorrules

YAML-based backend scaffolding for Manifest app development with structured entity and property definitions.

**/*
41k
via PatrickJS/awesome-cursorrules

Expert guidance for building applications with Medusa, TypeScript, React, and TailwindCSS.

**/*.tsx +5
41k
via PatrickJS/awesome-cursorrules

Expert guidance for building with Medusa, TypeScript, React, and TailwindCSS.

**/*
41k
via PatrickJS/awesome-cursorrules

Build custom frontends with Momen.app headless BaaS, GraphQL API, actionflows, AI agents, and Stripe integration.

**/*
41k
via PatrickJS/awesome-cursorrules