defold-native-extension-editing

Create Defold native extensions with standardized directory structures and entry points.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/zarkua/Defolancer --skill defold-native-extension-editing-zarkua
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defold-native-extension-editing
Source: https://github.com/zarkua/Defolancer/tree/main/.agents/skills/defold-native-extension-editing
Command: npx skills add https://github.com/zarkua/Defolancer --skill defold-native-extension-editing-zarkua

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize and simplify the creation and editing of Defold native extensions by defining a common directory layout, required files, and language entry points, so teams can ship reliable extensions faster.

Core Features & Use Cases

  • Standard extension layout with ext.manifest and optional directories (src/, include/, lib/, api/, res/) to organize code and resources.
  • Guidance for cross-language extensions, including C/C++ and JavaScript entry points, and platform considerations across multiple targets.
  • Use Case: Create a native extension to extend the Defold engine with new functionality and expose it to Lua via a defined API.

Quick Start

Create your extension folder with ext.manifest and populate src/, include/, and lib/ for your target platforms, then add a C++ or JavaScript entry point and register the extension.

Frequently Asked Questions about defold-native-extension-editing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the required directory structure for a Defold native extension?

A Defold native extension requires an ext.manifest file alongside optional src/, include/, lib/, api/, and res/ directories to organize C/C++ or JavaScript code and resources correctly.

How do I set up a native extension in Defold to expose C++ code to Lua?

To expose C++ to Lua, create an extension folder with ext.manifest, populate the src/ and include/ directories with your code, define a C++ entry point, and register the extension API.

Can I use JavaScript entry points when building Defold native extensions?

Yes, Defold native extensions support JavaScript entry points alongside C/C++, allowing you to define platform-specific code and integrate it within the standardized extension directory layout.

How do I organize cross-platform libraries for a Defold native extension?

Organize cross-platform libraries by placing compiled binaries into the lib/ directory and ensuring your ext.manifest correctly references platform targets for proper initialization and resource access.

Does a Defold native extension need an ext.manifest file to function?

Yes, the ext.manifest file is required as it defines the extension's metadata and structure, enabling the Defold engine to correctly initialize and load the native extension components.

When should I add res/ and api/ directories to my Defold extension layout?

Add the api/ directory to define Lua-facing APIs and the res/ directory to include necessary resources, ensuring your extension correctly initializes and exposes functionality to the engine.