php-pro — Claude Code skill: what it does, how to install
Enforces PHP 8.3+ standards across Laravel and Symfony projects with strict typing, PHPStan level 9 checks, and automated Pest tests.
npx skills add Jeffallan/claude-skills --skill php-pro -a claude-codeWhat php-pro does
This skill guides the assistant through modern PHP development under PSR-12 standards. It enforces a strict implementation sequence: domain entities and readonly DTOs come first, followed by service classes with constructor dependency injection, API endpoints, and automated tests.
Code validation is tied to strict checks. The workflow requires running vendor/bin/phpstan analyse --level=9 to resolve every error and executing phpunit or pest with at least 80% test coverage before finishing work.
The mandatory PHPStan level 9 rule means the model will reject untyped arguments, mixed types, and global state. The skill also adapts patterns for Laravel 11, Symfony 7, and asynchronous architectures with Swoole or ReactPHP.
What it helps with
- scaffold typed DTOs and value objects for PHP 8.3+
- build service classes with constructor dependency injection
- pass PHPStan static analysis at level 9 without errors
- write PHPUnit or Pest test suites enforcing 80%+ coverage
Example prompts for the agent
- Create a user registration service and DTO in Laravel with Pest tests
- Build a Symfony 7 API controller using constructor dependency injection
- Refactor this repository for PHPStan level 9 compliance and strict types
How to install php-pro
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill php-pro -a claude-code2Manually: put the files in place
~/.claude/skills/php-pro/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/php-pro/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill php-pro -a codex2Manually: put the files in place
.agents/skills/php-pro/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill php-pro -a cursor2Manually: put the files in place
.cursor/skills/php-pro/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jeffallan/claude-skills php-pro2Manually: put the files in place
.github/skills/php-pro/SKILL.md1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill php-pro -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jeffallan/claude-skills --path skills/php-proManually: put the files in place
.devin/skills/php-pro/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill php-pro -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set5
The whole set →Similar
Questions about php-pro
How to install php-pro in Claude Code?
Run npx skills add Jeffallan/claude-skills --skill php-pro -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/php-pro/SKILL.md.
What does the php-pro skill do?
It enforces strict typing, PSR-12 compliance, readonly DTOs, and dependency injection across Laravel, Symfony, or standalone PHP 8.3+ codebases.
What verification standards does php-pro require?
Implementations must pass vendor/bin/phpstan analyse --level=9 cleanly and achieve at least 80% test coverage using PHPUnit or Pest.
Source text
SKILL.md · MIT
---
name: php-pro
description: Use when building PHP applications with modern PHP 8.3+ features, Laravel, or Symfony frameworks. Invokes strict typing, PHPStan level 9, async patterns with Swoole, and PSR standards. Creates controllers, configures middleware, generates migrations, writes PHPUnit/Pest tests, defines typed DTOs and value objects, sets up dependency injection, and scaffolds REST/GraphQL APIs. Use when working with Eloquent, Doctrine, Composer, Psalm, ReactPHP, or any PHP API development.
license: MIT
metadata:
author: https://github.com/Jeffallan
company: https://synergetic.solutions
version: "1.1.0"
domain: language
triggers: PHP, Laravel, Symfony, Composer, PHPStan, PSR, PHP API, Eloquent, Doctrine
role: specialist
scope: implementation
output-format: code
related-skills: fullstack-guardian, fastapi-expert
---
# PHP Pro
Senior PHP developer with deep expertise in PHP 8.3+, Laravel, Symfony, and modern PHP patterns with strict typing and enterprise architecture.
## Core Workflow
1. **Analyze architecture** — Review framework, PHP version, dependencies, and patterns
2. **Design models** — Create typed domain models, value objects, DTOs
3. **Implement** — Write strict-typed code with PSR compliance, DI, repositories
4. **Secure** — Add validation, authentication, XSS/SQL injection protection
5. **Verify** — Run `vendor/bin/phpstan analyse --level=9`; fix all errors before proceeding. Run `vendor/bin/phpunit` or `vendor/bin/pest`; enforce 80%+ coverage. Only deliver when both pass clean.
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Modern PHP | `references/modern-php-features.md` | Readonly, enums, attributes, fibers, types |
| Laravel | `references/laravel-patterns.md` | Services, repositories, resources, jobs |
| Symfony | `references/symfony-patterns.md` | DI, events, commands, voters |
| Async PHP | `references/async-patterns.md` | Swoole, ReactPHP, fibers, streams |
| Testing | `references/testing-quality.md` | PHPUnit, PHPStan, Pest, mocking |
## Constraints
### MUST DO
- Declare strict types (`declare(strict_types=1)`)
- Use type hints for all properties, parameters, returns
- Follow PSR-12 coding standard
- Run PHPStan level 9 before delivery
- Use readonly properties where applicable
- Write PHPDoc blocks for complex logic
- Validate all user input with typed requests
- Use dependency injection over global state
### MUST NOT DO
- Skip type declarations (no mixed types)
- Store passwords in plain text (use bcrypt/argon2)
- Write SQL queries vulnerable to injection
- Mix business logic with controllers
- Hardcode configuration (use .env)
- Deploy without running tests and static analysis
- Use var_dump in production code
## Code Patterns
Every complete implementation delivers: a typed entity/DTO, a service class, and a test. Use these as the baseline structure.
### Readonly DTO / Value Object
```php
<?php
declare(strict_types=1);
namespace App\DTO;
final readonly class CreateUserDTO
{
public function __construct(
public string $name,
public string $email,
public string $password,
) {}
public static function fromArray(array $data): self
{
return new self(
name: $data['name'],
email: $data['email'],
password: $data['password'],
);
}
}
```
### Typed Service with Constructor DI
```php
<?php
declare(strict_types=1);
namespace App\Services;
use App\DTO\CreateUserDTO;
use App\Models\User;
use App\Repositories\UserRepositoryInterface;
use Illuminate\Support\Facades\Hash;
final class UserService
{
public function __construct(
private readonly UserRepositoryInterface $users,
) {}
public function create(CreateUserDTO $dto): User
{
return $this->users->create([
'name' => $dto->name,
'email' => $dto->email,
'password' => Hash::make($dto->password),
]);
}
}
```
### PHPUnit Test Structure
```php
<?php
declare(strict_types=1);
namespace Tests\Unit\Services;
use App\DTO\CreateUserDTO;
use App\Models\User;
use App\Repositories\UserRepositoryInterface;
use App\Services\UserService;
use PHPUnit\Framework\MockObject\MockObject;
use PHPUnit\Framework\TestCase;
final class UserServiceTest extends TestCase
{
private UserRepositoryInterface&MockObject $users;
private UserService $service;
protected function setUp(): void
{
parent::setUp();
$this->users = $this->createMock(UserRepositoryInterface::class);
$this->service = new UserService($this->users);
}
public function testCreateHashesPassword(): void
{
$dto = new CreateUserDTO('Alice', '[email protected]', '<test-password>');
$user = new User(['name' => 'Alice', 'email' => '[email protected]']);
$this->users
->expects($this->once())
->method('create')
->willReturn($user);
$result = $this->service->create($dto);
$this->assertSame('Alice', $result->name);
}
}
```
### Enum (PHP 8.1+)
```php
<?php
declare(strict_types=1);
namespace App\Enums;
enum UserStatus: string
{
case Active = 'active';
case Inactive = 'inactive';
case Banned = 'banned';
public function label(): string
{
return match($this) {
self::Active => 'Active',
self::Inactive => 'Inactive',
self::Banned => 'Banned',
};
}
}
```
## Output Templates
When implementing a feature, deliver in this order:
1. Domain models (entities, value objects, enums)
2. Service/repository classes
3. Controller/API endpoints
4. Test files (PHPUnit/Pest)
5. Brief explanation of architecture decisions
## Knowledge Reference
PHP 8.3+, Laravel 11, Symfony 7, Composer, PHPStan, Psalm, PHPUnit, Pest, Eloquent ORM, Doctrine, PSR standards, Swoole, ReactPHP, Redis, MySQL/PostgreSQL, REST/GraphQL APIs
Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
[Documentation](https://jeffallan.github.io/claude-skills/skills/language/php-pro/)
© https://github.com/Jeffallan · MIT · Jeffallan/claude-skills