Klytos Plugin Development

To ensure Klytos plugin discovery, structure your plugin under directory/plugins/{id}/{id}.php and include a Plugin Name header in the main file. This canonical identity contract allows the plugin loader to automatically detect and integrate your new features.

The canonical Klytos plugin layout uses structured directories for core components, including admin, assets, lang, src, and migrations. This structure provides clear guidance for organizing hooks, MCP tools, and dynamic routes across your installation.

You register MCP tools and admin pages in a Klytos plugin by utilizing provided lifecycle hooks and event hooks. The plugin development framework demonstrates how to properly register actions, filters, and translations alongside these integrations.

Yes, Klytos plugin development supports internationalization through lang directories and secure asset loading. It provides guidelines for proper asset loading that incorporate CSP nonces to maintain security guidelines across your Klytos installation.

Yes, you can build a payment gateway plugin using Klytos that registers MCP tools, admin pages, and dynamic API routes. The canonical plugin structure supports creating new features and debugging utilities that integrate cleanly with the ecosystem.

Klytos plugin security guidelines require proper asset loading using CSP nonces and adherence to canonical contract rules. Following these structured integration hooks and security practices ensures plugins integrate cleanly without vulnerabilities.