skills/php/php-tooling/SKILL.md
Configure PHP ecosystem tooling, dependency management, and static analysis. Use when managing Composer dependencies, running PHPStan, or configuring PHP build tools.
npx skillsauth add hoangnguyen0403/agent-skills-standard php-toolingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
project/
├── composer.json
├── phpstan.neon
└── .php-cs-fixer.php
composer.lock for applications. Use composer audit and composer install in CI (not update) for locked versions.composer.json (e.g., "psr-4": {"App\\": "src/"} — ensure backslashes escaped). Run composer dump-autoload after changes.composer require --dev phpstan/phpstan. Create phpstan.neon with parameters: { paths: [src], level: 6 }. Run via vendor/bin/phpstan analyse.composer require --dev friendsofphp/php-cs-fixer. Configure in .php-cs-fixer.php with $config->setRules(['@PSR12' => true]). Use php-cs-fixer to enforce standards.PHP 8.1+ to leverage performance improvements (JIT, OpCache)."scripts": { in composer.json ("analyze": "phpstan analyse", "test": "phpunit", "check": ["@fix", "@analyze", "@test"]}). Run with composer check.Xdebug for local development only. Remove xdebug.so from prod config or set XDEBUG_MODE=off in production.php:8.x-fpm or php:8.x-cli base images.require: Use Composer PSR-4 autoloading only.composer.lock diff first.vendor/ in git: Exclude via .gitignore; use Composer.development
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
development
Standardize BRD and BRD-lite discovery for business goals, stakeholder impact, current-to-future state, and measurable value outcomes. Use when creating BRD, business case, project justification, ROI narrative, or AS-IS to TO-BE scope.
development
Implements a strict Red-Green-Refactor loop to ensure zero production code is written without a prior failing test. Use when: creating new features, fixing bugs, or expanding test coverage.
testing
Standardize PRD discovery and drafting for product scope, user outcomes, requirement IDs, and acceptance criteria. Use when creating PRD, product requirements, feature specification, or acceptance criteria plan.