docs

SkillDocs & knowledge

Write and maintain Node3D package READMEs, API text, usage snippets, package roles, platform/install notes, and source-backed consumer documentation.

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 docs skill

What this skill tells your AI

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

Consumer-facing package documentation.

Inspect the package public entrypoint plus the source/examples/tests that prove the documented behavior.
Derive snippets from real package imports and runnable examples; do not invent APIs.
Keep docs concise and package-specific.
Keep deps-* provenance/license notes and native install/platform notes where consumer-relevant.
If wording changes a public API/platform/install claim, set Contract Gate YES even when no source code changes.

Load .agents/references/documentation-examples.md for README structure, package-family emphasis, or snippet/example rules.

Load the behavioral owner skill as secondary only when verifying or modifying its implementation contract.

Advanced