architecture-templates

Create the template in the Intent Application Template Builder designer using a new Package. Model an Application Template root with Settings and Defaults stereotypes, then add Component Groups, Components, and Component Modules whose names exactly match published module ids.

Create a separate empty application named <TemplateName>.Metadata, install only the modules owning the target designers, model the desired state using template strings like ${application.name}, then use the designer's Export toolbar button and save the clipboard content as a .installation.config file.

An Architecture Template defines the module picker shown when creating a new application. A Module Building template scaffolds a module project instead of an app, so it is a different Template Type set on the Application Template Settings stereotype.

Application Templates place .installation.config files in the resources/ folder, while plain Modules place them in the content/ folder. Name each file after the designer it targets, such as domain.installation.config.

A File Template's Role property matches a Codebase Structure Output Anchor by exact name, falling back up dotted segments like Domain.Entity to Domain. Anchors only control initial placement; later moves by users survive module updates and reinstalls.

Template Output elements are module-managed and automatically created, removed, or renamed as modules install and update. Capturing them as static metadata conflicts with that lifecycle, so placement should be handled through Output Anchors instead.