Php Best Practices

by asyrafhussin1aa0ff717c10MIT86 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 6 weeks ago

PHP 8.x modern patterns, PSR standards, and SOLID principles. Use when reviewing PHP code, checking type safety, auditing code quality, or ensuring PHP best practices. Triggers on "review PHP", "check PHP code", "audit PHP", or "PHP best practices".

Instructions onlySoftware Development
AI-generated overview

Reference rules for reviewing PHP 8.x code against type safety, PSR standards, SOLID principles, error handling, performance and security.

What it does
Provides 51 rule files covering PHP 8.0-8.5 features, type system usage, PSR standards, SOLID principles, error handling, performance and security. It guides version detection via composer.json and php -v so advice matches the project's PHP version, and defines an output format for audit findings as file:line entries. It is instructions only and produces no files or scripts.
When to use it
Use when writing or reviewing PHP code, auditing code quality or type safety, or checking adherence to PSR standards and SOLID principles. It is also suited to advising on which modern PHP features are available for a given PHP version.
Requirements
No scripts or packages; the agent reads the bundled rule files. Version detection expects access to the project's composer.json and the PHP runtime version.

PHP Best Practices

Modern PHP 8.x patterns, PSR standards, type system best practices, and SOLID principles. Contains 51 rules for writing clean, maintainable PHP code.

Step 1: Detect PHP Version

Always check the project's PHP version before giving any advice. Features vary significantly across 8.0 - 8.5. Never suggest syntax that doesn't exist in the project's version.

Check composer.json for the required PHP version:

json
{ "require": { "php": "^8.1" } }   // -> 8.1 rules and below{ "require": { "php": "^8.3" } }   // -> 8.3 rules and below{ "require": { "php": ">=8.4" } }  // -> 8.4 rules and below

Also check the runtime version:

bash
php -v   # e.g. PHP 8.3.12

Feature Availability by Version

FeatureVersionRule Prefix
Union types, match, nullsafe, named args, constructor promotion, attributes8.0+type-, modern-
Enums, readonly properties, intersection types, first-class callables, never, fibers8.1+modern-
Readonly classes, DNF types, true/false/null standalone types8.2+modern-
Typed class constants, #[\Override], json_validate()8.3+modern-
Property hooks, asymmetric visibility, #[\Deprecated], new without parens8.4+modern-
Pipe operator `>`8.5+

Only suggest features available in the detected version. If the user asks about upgrading or newer features, mention what becomes available at each version.

When to Apply

Reference these guidelines when:

  • Writing or reviewing PHP code
  • Implementing classes and interfaces
  • Using PHP 8.x modern features
  • Ensuring type safety
  • Following PSR standards
  • Applying design patterns

Rule Categories by Priority

PriorityCategoryImpactPrefixRules
1Type SystemCRITICALtype-9
2Modern PHP FeaturesCRITICALmodern-16
3PSR StandardsHIGHpsr-6
4SOLID PrinciplesHIGHsolid-5
5Error HandlingHIGHerror-5
6PerformanceMEDIUMperf-5
7SecurityCRITICALsec-5

Quick Reference

1. Type System (CRITICAL) — 9 rules

  • type-strict-mode - Declare strict types in every file
  • type-return-types - Always declare return types
  • type-parameter-types - Type all parameters
  • type-property-types - Type class properties
  • type-union-types - Use union types effectively
  • type-intersection-types - Use intersection types
  • type-nullable-types - Handle nullable types properly
  • type-void-never - Use void/never for appropriate return types
  • type-mixed-avoid - Avoid mixed type when possible

2. Modern PHP Features (CRITICAL) — 16 rules

8.0+:

  • modern-constructor-promotion - Constructor property promotion
  • modern-match-expression - Match over switch
  • modern-named-arguments - Named arguments for clarity
  • modern-nullsafe-operator - Nullsafe operator (?->)
  • modern-attributes - Attributes for metadata

8.1+:

  • modern-enums - Enums instead of constants
  • modern-enums-methods - Enums with methods and interfaces
  • modern-readonly-properties - Readonly for immutable data
  • modern-first-class-callables - First-class callable syntax
  • modern-arrow-functions - Arrow functions (7.4+, pairs well with 8.1 features)

8.2+:

  • modern-readonly-classes - Readonly classes

8.3+:

  • modern-typed-constants - Typed class constants (const string NAME = 'foo')
  • modern-override-attribute - #[\Override] to catch parent method typos

8.4+:

  • modern-property-hooks - Property hooks replacing getters/setters
  • modern-asymmetric-visibility - public private(set) for controlled access

8.5+:

  • modern-pipe-operator - Pipe operator (|>) for functional chaining

3. PSR Standards (HIGH) — 6 rules

  • psr-4-autoloading - Follow PSR-4 autoloading
  • psr-12-coding-style - Follow PSR-12 coding style
  • psr-naming-classes - Class naming conventions
  • psr-naming-methods - Method naming conventions
  • psr-file-structure - One class per file
  • psr-namespace-usage - Proper namespace usage

4. SOLID Principles (HIGH) — 5 rules

  • solid-srp - Single Responsibility: one reason to change
  • solid-ocp - Open/Closed: extend, don't modify
  • solid-lsp - Liskov Substitution: subtypes must be substitutable
  • solid-isp - Interface Segregation: small, focused interfaces
  • solid-dip - Dependency Inversion: depend on abstractions

5. Error Handling (HIGH) — 5 rules

  • error-custom-exceptions - Create specific exceptions for different errors
  • error-exception-hierarchy - Organize exceptions into meaningful hierarchy
  • error-try-catch-specific - Catch specific exceptions, not generic \Exception
  • error-finally-cleanup - Use finally for guaranteed resource cleanup
  • error-never-suppress - Never use @ error suppression operator

6. Performance (MEDIUM) — 5 rules

  • perf-avoid-globals - Avoid global variables, use dependency injection
  • perf-lazy-loading - Defer expensive operations until needed
  • perf-array-functions - Use native array functions over manual loops
  • perf-string-functions - Use native string functions over regex
  • perf-generators - Use generators for large datasets

7. Security (CRITICAL) — 5 rules

  • sec-input-validation - Validate and sanitize all external input
  • sec-output-escaping - Escape output based on context (HTML, JS, URL)
  • sec-password-hashing - Use password_hash/verify, never MD5/SHA1
  • sec-sql-prepared - Use prepared statements for all SQL queries
  • sec-file-uploads - Validate file type, size, name; store outside web root

Essential Guidelines

For detailed examples and explanations, see the rule files:

  • type-strict-mode.md [blocked] - Strict types declaration
  • modern-constructor-promotion.md [blocked] - Constructor property promotion
  • modern-enums.md [blocked] - PHP 8.1+ enums with methods
  • solid-srp.md [blocked] - Single responsibility principle

Key Patterns (Quick Reference)

php
<?phpdeclare(strict_types=1);
// 8.0+ Constructor promotion + readonly (8.1+)class User{    public function __construct(        public readonly string $id,        private string $email,    ) {}}
// 8.1+ Enums with methodsenum Status: string{    case Active = 'active';    case Inactive = 'inactive';
    public function label(): string    {        return match($this) {            self::Active => 'Active',            self::Inactive => 'Inactive',        };    }}
// 8.0+ Match expression$result = match($status) {    'pending' => 'Waiting',    'active' => 'Running',    default => 'Unknown',};
// 8.0+ Nullsafe operator$country = $user?->getAddress()?->getCountry();
// 8.3+ Typed class constants + #[\Override]class PaymentService extends BaseService{    public const string GATEWAY = 'stripe';
    #[\Override]    public function process(): void { /* ... */ }}
// 8.4+ Property hooks + asymmetric visibilityclass Product{    public string $name { set => trim($value); }    public private(set) float $price;}
// 8.5+ Pipe operator$result = $input    |> trim(...)    |> strtolower(...)    |> htmlspecialchars(...);

Output Format

When auditing code, output findings in this format:

file:line - [category] Description of issue

Example:

src/Services/UserService.php:15 - [type] Missing return type declarationsrc/Models/Order.php:42 - [modern] Use match expression instead of switchsrc/Controllers/ApiController.php:28 - [solid] Class has multiple responsibilities

How to Use

Read individual rule files for detailed explanations:

rules/modern-constructor-promotion.mdrules/type-strict-mode.mdrules/solid-srp.md

Source and attribution

Source:asyrafhussin/agent-skillsinskills/php-best-practicesat commit1aa0ff7

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal