intent-domain-interactions-expert

name	intent-domain-interactions-expert
description	Translate modelled designer interactions into C# handler bodies.
argument-hint	[handler template id or role] [interaction kind]

Intent Domain Interactions Expert

[!TIP] Read more if you want to know about built-in interaction strategies, strategy registration, mapping code snippets, or execution phases:

• Interactions Cheatsheet (To conserve tokens, avoid reading this file for simple or minor updates.)

Musts

1. Implement IInteractionStrategy: Expose IsMatch(IElement interaction) and ImplementInteraction(...).
2. Early Registration: Register strategies in factory extensions' OnBeforeTemplateRegistrations (never inside constructors).
3. Cheap Match: Keep IsMatch cheap and side-effect-free (check typed target end models).
4. Phased Statements: Emit statements via method.AddStatement(...) with explicit ExecutionPhases (e.g. BusinessLogic, Return).
5. Mapping Resolution: Use method.GetMappingManager() and add resolvers up-front inside ImplementInteraction.
6. Register Type Sources: Call template.AddTypeSource(...) for templates producing referenced types.

Must Nots

1. Never register a strategy from inside a template constructor.
2. Never hardcode the handler's method name or signature inside the strategy.
3. Never call template.CSharpFile.AfterBuild from inside a strategy.
4. Never branch on stereotype string names inside IsMatch (use typed predicates).
5. Never call method.AddStatement(...) without a phase when multiple strategies attach to the same handler.
6. Never modify the handler's class structure (e.g. constructor/fields) directly from a strategy; use @class.InjectService(...) instead.