NativePHP Plugin Structure FAQs

Name: NativePHP Plugin Structure
Author: NativePHP

Question 1

How does this skill improve my development workflow?

Accepted Answer

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.

Question 2

When should I use this skill with Claude Code?

Accepted Answer

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.

Question 3

How does this skill handle the nativephp.json manifest?

Accepted Answer

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.

Question 4

What does the NativePHP Plugin Structure skill do?

Accepted Answer

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.

Question 5

Does this skill help with cross-platform mobile support?

Accepted Answer

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.

NativePHP Plugin Structure

NativePHP Plugin Structure

Características Principales

Casos de Uso

Características Principales

Casos de Uso