What problem does it solve?
This Skill solves the common problem of developers incorrectly placing business logic in the wrong layer of OrangeHRM's three-tier backend, leading to messy, hard-to-maintain code that violates project conventions.
Core Features & Use Cases
- Logic Placement Guidance: Clear rules for what belongs in a service vs a DAO or entity decorator, eliminating guesswork when implementing new features.
- Standard Pattern Reference: Canonical patterns for service registration, lazy-getter dependency composition, and service trait access used across the entire OrangeHRM codebase.
- Use Case: When building a new employee onboarding feature, use this Skill to correctly implement multi-step save logic in a service, register it in your plugin configuration, and access it from API endpoints without breaking existing conventions.
Quick Start
Use the services skill to implement the business logic for a new employee onboarding feature, register it correctly in your plugin configuration, and access it from API endpoints following OrangeHRM's service layer conventions.