Split the God class by responsibility: put validation in a validator, persistence behind a repository interface, notifications behind a notifier interface, and orchestration in a small application service. Inject those interfaces through the constructor. Keep each class focused, use typed methods, and let the orchestrator coordinate collaborators rather than owning every implementation detail.
Installs into .claude/skills of the current project.
Are you the author of Php Best Practices?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/hoangnguyen0403-php-best-practices-1e1e3877)
Split the God class by responsibility: put validation in a validator, persistence behind a repository interface, notifications behind a notifier interface, and orchestration in a small application service. Inject those interfaces through the constructor. Keep each class focused, use typed methods, and let the orchestrator coordinate collaborators rather than owning every implementation detail.
