extension-creator

To scaffold an AiderDesk extension, generate boilerplate code, default metadata, and documentation templates. The tool creates a default class and enforces the extension interface requirements for both single-file and folder-based extensions.

Single-file and folder-based AiderDesk extensions differ in project structure. Both receive generated boilerplate code, metadata, and config templates, but folder-based extensions also include UI component templates and in-repo registration instructions for project integration.

Yes, you can generate UI and config component templates for AiderDesk extensions. The scaffolding process provides these templates alongside default metadata to ensure consistency and enforce the required extension interface.

To register a new extension in an AiderDesk project repository, follow the in-repo registration instructions provided during scaffolding. The generated templates update references and documentation patterns to ensure proper project integration and consistency.

The best way to ensure your TypeScript extension meets AiderDesk interface requirements is to use an extension scaffold generator. It enforces the interface requirements automatically and provides default metadata compliant with the specified extension structure.

No, you do not need to manually write metadata for AiderDesk extension templates. The scaffolding process provides default metadata and documentation templates automatically, reducing manual setup and ensuring consistency across all generated extensions.