intent-mapping-architect

name	intent-mapping-architect
description	Translate designer-defined advanced mappings into recursive C# Builder statements.
argument-hint	[mapping type] [source model] [target model]

Intent Mapping Architect

[!TIP] Read more if you want to know about mapping managers, custom type resolvers, traversal pipelines, or API signatures:

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

Musts

1. Replacement Resolution: Configure replacements via SetFromReplacement(...)/SetToReplacement(...) and generate statements via MappingManager APIs (GenerateUpdateStatements(...) etc.).
2. Path Resolution: Resolve assignments via mapping element IDs and paths, never by property names.
3. Node Differentiation: Explicitly handle Terminal Mappings (leaf) vs Object Mappings (nested/collection).
4. Metadata Preservation: Custom mapping statements in recursive generation must implement IHasMapping.
5. Mapping Options: Honor designer model MappingOptions: Null-Safe (emit guards) and Validate All.
6. Custom Resolver Registration: Register custom IMappingTypeResolver implementations with explicit priority.
7. Inherit CSharpMappingBase: Inherit custom mappings from CSharpMappingBase to leverage recursive tree traversal.

Must Nots

1. Never hardcode property-to-property assignments.
2. Never bypass MappingManager-driven replacement resolution.
3. Never treat object/collection mappings as scalar terminals.
4. Never create mapping statement types that omit IHasMapping inside recursive mapping flow.
5. Never ignore MappingOptions Null-Safe and Validate All settings.
6. Never place transaction/retrieval/persistence orchestration in this skill (belongs to intent-domain-interactions-expert).