Implement Dokan backend PHP classes with namespace mapping and PSR-4 autoloading.
npx skills add https://github.com/getdokan/dokan --skill dokan-backend-dev
Please help me install this Agent Skill. Skill: dokan-backend-dev Source: https://github.com/getdokan/dokan/tree/main/.claude/skills/dokan-backend-dev Command: npx skills add https://github.com/getdokan/dokan --skill dokan-backend-dev
Dokan backend development requires consistent architecture, naming, and REST integration across modules. This skill provides a centralized guide that standardizes how to implement backend PHP code for Dokan plugins.
Follow the conventions to add a new backend PHP class under the Dokan namespace, implement a Manager, and expose REST endpoints according to the guide.
High-intent search queries and answers about installing and using this skill.
To create a new Dokan backend PHP class, place it under the Dokan namespace using PSR-4 autoloading, implement a Manager pattern, and register it via a service provider to align with project architecture and pass reviews.
Dokan REST controllers require strict namespace mapping and PSR-4 autoloading compliance, ensuring the class file path directly matches its namespace structure to maintain predictable, project-aligned backend code.
You add custom Dokan REST endpoints by structuring a new REST controller class according to Dokan conventions, mapping the namespace correctly, and exposing endpoints through the project's standardized provider registration system.
Yes, Dokan backend hooks and services must follow specific coding standards, utilizing manager patterns and provider registration to ensure predictable, maintainable growth across the plugin architecture.
The Dokan Manager pattern standardizes backend module architecture by encapsulating service logic within namespaced classes, ensuring new features integrate predictably with existing hooks and REST endpoints.
Writing unit tests for Dokan backend PHP code requires following project-aligned coding standards, ensuring new classes, services, and hooks meet the specified architectural conventions for predictable testability.
bobmatnycGuide WordPress plugin development with PHP 8.3, OOP, and Composer.
getdokanReview Dokan PHP code and pull requests for coding standards and security.
getdokanGuide Dokan frontend UI development with React, TypeScript, Vue, Tailwind, and Webpack.
j7-devReference WordPress and PHP coding standards for security and naming conventions.
