Extending Stone.js

Everything the framework ships, adapters, extensions, decorators, commands, is built with the same public seams you have. This section shows how to author each kind of building block, so a missing capability or runtime is a package you write, not a release you wait for.

#The one rule that makes it possible

The micro-kernel depends on three primitives and nothing else; capability attaches through blueprints and providers, never by the core reaching outward. That single constraint is what lets anyone, first-party or not, extend the framework without forking it.

#What you can author