Archi Online Scripts and Extensions

Build artifacts against Archi Online's supported wrapper APIs, preserve undo/read-only/session behavior, and prove the result with the bundled checker plus the repository tests that own the changed surface.

Choose the artifact

1. Use an .ajs script for user-triggered model automation in the Scripting panel.
2. Use a source extension for browser-local commands, menus, toolbar buttons, panels, events, or recurring workflows that the user wants to edit in the Extensions panel.
3. Use an extension package when the artifact must be portable or needs bundled JSON, documentation, or image assets. Package it as a .archi-ext ZIP with a schema-v2 manifest.

Read references/scripting.md for scripts. Read references/extensions.md for source extensions or packages. Read both when an extension mutates or inspects the model.

When working inside the archi-online repository, treat the current repository as authoritative and inspect these before implementation: