NativePHP Plugin Structure
Defines the required architecture and configuration standards for building NativePHP plugins that bridge PHP with native mobile functionality.
The source repository doesn't declare a license. Check its terms before reusing the code.
Key features
- Detailed nativephp.json manifest configuration for iOS and Android
- Bridge function mapping between PHP and native Kotlin/Swift code
- Standardized directory layout blueprints for cross-platform support
- Build-time lifecycle hook implementation for asset management
- Laravel service provider and facade implementation patterns
Use cases
- Bootstrapping a new NativePHP plugin with the correct file structure
- Configuring native platform permissions and Gradle/CocoaPods dependencies
- Implementing native-to-PHP event dispatching for mobile interactions
FAQ
How does this skill improve my development workflow?
It automates the generation of complex boilerplate code, such as Laravel service providers, facades, and native bridge mappings. This reduces manual configuration errors and allows Claude to generate production-ready plugin packages much faster.
When should I use this skill with Claude Code?
Use this skill whenever you are developing a plugin to extend NativePHP with custom native features, such as camera integration, biometric authentication, or specialized mobile SDKs. It is essential when you need to map PHP methods to native Kotlin or Swift functions.
How does this skill handle the nativephp.json manifest?
It provides precise templates for the manifest file, including bridge_function mappings, Android-specific permissions and dependencies, iOS usage descriptions (Info.plist), and build-time lifecycle hooks like copy_assets.
What does the NativePHP Plugin Structure skill do?
This skill equips Claude with the specific architectural blueprints and configuration standards needed to build NativePHP plugins. it covers everything from directory layouts and composer.json requirements to the critical nativephp.json manifest that bridges PHP with native mobile code.
Does this skill help with cross-platform mobile support?
Yes. It defines the standardized directory structure for both resources/android (Kotlin) and resources/ios (Swift), ensuring that your plugin can provide consistent functionality across both mobile platforms while maintaining a clean Laravel-friendly PHP API.