magento-php-specialist — Claude Code skill: install and overview
magento-php-specialist — a skill enforcing PSR-12 and Magento 2 standards for PHP development. Guides your agent to write typed code using framework patterns and strict checks.
MIT 263 installs ★ 33 updated 2026-01-24
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a claude-codeWhat magento-php-specialist does
This skill directs the agent to generate PHP code matching PSR-12 and vendor/magento/magento-coding-standard/Magento2. It requires declare(strict_types=1); in every file, method opening braces on their own lines, and strict comparison operators such as ===.
The instructions incorporate modern PHP features: match expressions, union types, and constructor property promotion with readonly. Architecture requirements focus on single responsibility, composition, repository patterns, factories, and plugins. Logging must use \Psr\Log\LoggerInterface.
Code relying on service locators will fail these checks, as the skill strictly mandates constructor dependency injection.
What it helps with
- write Magento 2 services with strict type coverage
- implement repository patterns and service contracts under PSR-12
- refactor switch statements into modern match expressions
- structure dependency injection without service locators
Example prompts for the agent
- Create a customer order service using constructor property promotion and strict types
- Generate a Magento 2 repository class following PSR-12 formatting
- Implement an around plugin for the product repository with full type hints
How to install magento-php-specialist
1Skills CLI (Vercel)
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a claude-code2Manually: put the files in place
~/.claude/skills/magento-php-specialist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/magento-php-specialist/
1Skills CLI (Vercel)
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a codex2Manually: put the files in place
.agents/skills/magento-php-specialist/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a cursor2Manually: put the files in place
.cursor/skills/magento-php-specialist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install maxnorm/magento2-agent-skills skills/magento-php-specialist2Manually: put the files in place
.github/skills/magento-php-specialist/SKILL.md1Skills CLI (Vercel)
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a gemini-cli2Platform CLI
gemini skills install https://github.com/maxnorm/magento2-agent-skills --path skills/magento-php-specialistManually: put the files in place
.devin/skills/magento-php-specialist/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about magento-php-specialist
How to install magento-php-specialist in Claude Code?
Run npx skills add maxnorm/magento2-agent-skills --skill magento-php-specialist -a claude-code. You can also store the file at ~/.claude/skills/magento-php-specialist/SKILL.md.
What does magento-php-specialist do?
It sets strict coding rules for Magento 2 PHP development, including complete type hinting, PSR-12 compliance, and official Magento design patterns.
What dependency injection approach does this skill enforce?
It requires constructor injection for all dependencies and explicitly forbids using service locators.
Source text
SKILL.md · MIT
---
name: magento-php-specialist
description: Advanced PHP development for Magento 2 following PSR-12 and Magento coding standards. Use when writing PHP code, implementing business logic, or ensuring code quality. Masters modern PHP features, object-oriented programming, design patterns, and Magento-specific PHP practices.
---
# Magento 2 PHP Specialist
Expert specialist in leveraging advanced PHP techniques and modern practices to create high-performance, maintainable Magento 2 applications following enterprise development standards.
## When to Use
- Writing PHP code for Magento 2
- Implementing business logic
- Ensuring code quality and standards
- Working with modern PHP features
- Implementing design patterns
## PHP Standards (STRICT ENFORCEMENT)
### PSR-12 Compliance
- **PSR-12**: Strictly adhere to PSR-12 coding standards
- **Magento2 Coding Standard**: Follow standards in `vendor/magento/magento-coding-standard/Magento2`
- **Strict Types**: `declare(strict_types=1);` required
- **EditorConfig**: Check project's `.editorconfig` for indentation (4 spaces), line endings (LF), encoding (UTF-8)
### Code Structure Requirements
- **Opening Braces**: Classes and methods must have opening braces on their own line (PSR-12)
- **Constructor Property Promotion**: Use with `readonly` modifier where appropriate
- **Type Hinting**: All parameters and return types must be type-hinted
- **Strict Comparisons**: Always use `===` and `!==` (never `==` or `!=`)
- **Constructor PHPDoc**: Must include `@param` annotation for each parameter
### Modern PHP Features
- **Constructor Property Promotion**: Use constructor property promotion
- **Readonly Properties**: Use `readonly` modifier where appropriate
- **Union Types**: Use union types for flexible type hints
- **Match Expressions**: Use match expressions instead of switch when appropriate
- **Named Arguments**: Use named arguments for clarity
### Code Example
```php
<?php
/**
* Copyright © 2025 CompanyName. All rights reserved.
*/
declare(strict_types=1);
namespace CompanyName\ModuleName\Model;
use CompanyName\ModuleName\Api\ConfigInterface;
use CompanyName\ModuleName\Api\RepositoryInterface;
class Service
{
/**
* @param RepositoryInterface $repository
* @param ConfigInterface $config
*/
public function __construct(
private readonly RepositoryInterface $repository,
private readonly ConfigInterface $config
) {
}
/**
* @param int $id
* @return EntityInterface|null
*/
public function getById(int $id): ?EntityInterface
{
if ($id <= 0) {
return null;
}
return $this->repository->getById($id);
}
}
```
## Best Practices
### Object-Oriented Programming
- **Composition Over Inheritance**: Prefer composition patterns
- **Dependency Injection**: Constructor injection only - avoid service locators
- **Single Responsibility**: One purpose per class/method
- **Interface Segregation**: Use small, focused interfaces
- **SOLID Principles**: Follow SOLID principles
### Code Quality
- **Type Safety**: 100% type coverage - parameters, return types, properties
- **Error Handling**: Comprehensive exception handling
- **Logging**: Use `\Psr\Log\LoggerInterface` for logging
- **Documentation**: Minimal PHPDoc with `@param`, `@return`, `@throws`
- **Testing**: Write unit tests for business logic
### Magento-Specific Patterns
- **Service Contracts**: Use service contracts for APIs
- **Repository Pattern**: Implement repository pattern for data access
- **Factory Pattern**: Use factories for object creation
- **Plugin Pattern**: Use plugins to extend functionality
- **Observer Pattern**: Use observers for event-driven architecture
## References
- [PSR-12 Coding Standard](https://www.php-fig.org/psr/psr-12/)
- [Adobe Commerce PHP Development](https://developer.adobe.com/commerce/php/development/)
- [Coding Standards](https://developer.adobe.com/commerce/php/coding-standards/)
Focus on writing clean, maintainable PHP code that follows Magento best practices.
© maxnorm · MIT · maxnorm/magento2-agent-skills