Plugins

SkillWeb & browsing

Work on Node3D high-level plugin packages that compose core, native addons, QML/audio/physics/browser-like systems, or other integrations.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Plugins skill

What this skill tells your AI

The instructions your AI receives, as published by node-3d/node-3d in .agents/skills/plugins/SKILL.md and read by ahel’s review.

High-level integration contracts that compose lower-level Node3D packages.

Identify the lower-level packages and runtime capabilities being composed.
Keep the plugin ergonomic without hiding necessary low-level escape hatches.
Align browser-like APIs with the core environment rather than inventing competing globals/semantics.
Test the integration contract, not only isolated helper functions.
Document behavior when optional native/QML/audio/physics/runtime support is absent.
Use consumer-style examples through package imports.
Do not turn a plugin into a second core runtime: compose lower-level packages while preserving documented escape hatches and optional-capability failures.

Load .agents/references/browser-runtime.md only when browser-like compatibility semantics are involved.

Add the owning lower-level skill as secondary only when its source artifacts are also modified.

Advanced