51 rules for writing clean, type-safe, modern PHP 8.x code aligned with PSR standards and SOLID principles.
Works with
Covers 7 rule categories: type system, modern PHP features (8.0–8.5), PSR standards, SOLID principles, error handling, performance, and security
Version-aware guidance that detects PHP version from composer.json and runtime, recommending only features available in the target version
Organized by priority: type safety and security are critical; modern features and SOLID principl
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionphp-best-practicesExecute the skills CLI command in your project's root directory to begin installation:
Fetches php-best-practices from asyrafhussin/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate php-best-practices. Access via /php-best-practices in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
5
total installs
5
this week
24
GitHub stars
0
upvotes
Run in your terminal
5
installs
5
this week
24
stars
Modern PHP 8.x patterns, PSR standards, type system best practices, and SOLID principles. Contains 51 rules for writing clean, maintainable PHP code.
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:
{ "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:
php -v # e.g. PHP 8.3.12
| Feature | Version | Rule Prefix |
|---|---|---|
| Union types, match, nullsafe, named args, constructor promotion, attributes | 8.0+ | type-, modern- |
| Enums, readonly properties, intersection types, first-class callables, never, fibers | 8.1+ | modern- |
| Readonly classes, DNF types, true/false/null standalone types | 8.2+ | modern- |
Typed class constants, #[\Override], json_validate() |
8.3+ | modern- |
Property hooks, asymmetric visibility, #[\Deprecated], new without parens |
8.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.
Reference these guidelines when:
| Priority | Category | Impact | Prefix | Rules |
|---|---|---|---|---|
| 1 | Type System | CRITICAL | type- |
9 |
| 2 | Modern PHP Features | CRITICAL | modern- |
16 |
| 3 | PSR Standards | HIGH | psr- |
6 |
| 4 | SOLID Principles | HIGH | solid- |
5 |
| 5 | Error Handling | HIGH | error- |
5 |
| 6 | Performance | MEDIUM | perf- |
5 |
| 7 | Security | CRITICAL | sec- |
5 |
type-strict-mode - Declare strict types in every filetype-return-types - Always declare return typestype-parameter-types - Type all parameterstype-property-types - Type class propertiestype-union-types - Use union types effectivelytype-intersection-types - Use intersection typestype-nullable-types - Handle nullable types properlytype-void-never - Use void/never for appropriate return typestype-mixed-avoid - Avoid mixed type when possible8.0+:
modern-constructor-promotion - Constructor property promotionmodern-match-expression - Match over switchmodern-named-arguments - Named arguments for claritymodern-nullsafe-operator - Nullsafe operator (?->)modern-attributes - Attributes for metadata8.1+:
modern-enums - Enums instead of constantsmodern-enums-methods - Enums with methods and interfacesmodern-readonly-properties - Readonly for immutable datamodern-first-class-callables - First-class callable syntaxmodern-arrow-functions - Arrow functions (7.4+, pairs well with 8.1 features)8.2+:
modern-readonly-classes - Readonly classes8.3+:
modern-typed-constants - Typed class constants (const string NAME = 'foo')modern-override-attribute - #[\Override] to catch parent method typos8.4+:
modern-property-hooks - Property hooks replacing getters/settersmodern-asymmetric-visibility - public private(set) for controlled access8.5+:
modern-pipe-operator - Pipe operator (|>) for functional chainingpsr-4-autoloading - Follow PSR-4 autoloadingpsr-12-coding-style - Follow PSR-12 coding stylepsr-naming-classes - Class naming conventionspsr-naming-methods - Method naming conventionspsr-file-structure - One class per filepsr-namespace-usage - Proper namespace usagesolid-srp - Single Responsibility: one reason to changesolid-ocp - Open/Closed: extend, don't modifysolid-lsp - Liskov Substitution: subtypes must be substitutablesolid-isp - Interface Segregation: small, focused interfacessolid-dip - Dependency Inversion: depend on abstractionserror-custom-exceptions - Create specific exceptions for different errorserror-exception-hierarchy - Organize exceptions into meaningful hierarchyerror-try-catch-specific - Catch specific exceptions, not generic \Exceptionerror-finally-cleanup - Use finally for guaranteed resource cleanuperror-never-suppress - Never use @ error suppression operatorperf-avoid-globals - Avoid global variables, use dependency injectionperf-lazy-loading - Defer expensive operations until neededperf-array-functions - Use native array functions over manual loopsperf-string-functions - Use native string functions over regexperf-generators - Use generators for large datasetssec-input-validation - Validate and sanitize all external inputsec-output-escaping - Escape output based on context (HTML, JS, URL)sec-password-hashing - Use password_hash/verify, never MD5/SHA1sec-sql-prepared - Use prepared statements for all SQL queriessec-file-uploads - Validate file type, size, name; store outside web rootFor detailed examples and explanations, see the rule files:
<?php
declare(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 methods
enum 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 visibility
class Product
{
public string $name { set => trim($value); }
public private(set) float $price;
}
// 8.5+ Pipe operator
$result = $input
|> trim(...)
|> strtolower(...)
|> htmlspecialchars(...);
When auditing code, output findings in this format:
file:line - [category] Description of issue
Example:
src/Services/UserService.php:15 - [type] Missing return type declaration
src/Models/Order.php:42 - [modern] Use match expression instead of switch
src/Controllers/ApiController.php:28 - [solid] Class has multiple responsiMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
asyrafhussin/agent-skills
asyrafhussin/agent-skills
kadajett/agent-nestjs-skills
jwynia/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
Useful defaults in php-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
php-best-practices is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for php-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend php-best-practices for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: php-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in php-best-practices — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for php-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
php-best-practices reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: php-best-practices is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for php-best-practices matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 41