Menu
Translate designer-defined advanced mappings into recursive C# Builder statements.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
The accumulated strategic playbook for building Intent.Modules.NET modules — the judgment calls a veteran module builder makes, distinct from the mechanical process. Covers module decomposition (root/bridging/common), template vs factory-extension choice, file cardinality, managed modes, design-time configuration (setting vs stereotype), convention-vs-explicit, and two-phase verification. LOAD THIS at every design decision point: during kickoff, pattern research, ecosystem analysis, reference-app building, and the increment loop. Referenced by all module-building chain skills.
Use after tech-pattern-researcher produces a Pattern Document and before module-ecosystem-analyst. Scaffolds a real Intent-managed Clean Architecture application with standard modules installed, runs the Software Factory to get the actual generated output, then hand-crafts the technology-specific files on top of that real output. Proves the code shapes compile and the handler is hit at runtime. The running app becomes the ground truth that module-ecosystem-analyst reads to understand what the ecosystem already generates. TRIGGER: mandatory after Pattern Document, before ecosystem analysis — never skip. BLOCK on this skill until the reference app is green.
Use after module-kickoff produces a Requirements Summary. Researches the technology in isolation, maps it to Clean Architecture, and defines exactly what the module must generate. TRIGGER: when a Requirements Summary is in hand and the next step is understanding how to implement it. Produces a Pattern Document — the input to reference-app-builder.
Convert C# template files to Fluent CSharpFile builder API.
Intent Architect MCP workflow: designer operations, element discovery, model modification, Software Factory execution, compilation verification, and cross-module integration patterns. If you find yourself wanting to edit `.xml`, `.config`, `.settings` files inside an `intent` metadata folder directly, perform the change via the IA MCP. This workflow is designed to keep models as the single source of truth — direct file edits are a last resort for truly exceptional cases.
Use after module-ecosystem-analyst produces an Attack Plan. Uses the Intent Architect Module Builder designer via MCP to scaffold the new module: creates the package, templates, factory extensions, and NuGet declarations, then runs Software Factory to generate the code scaffold. TRIGGER: when an Attack Plan is in hand and the next step is scaffolding the module structure. Produces a compiled module skeleton ready for implementation.
| name | intent-mapping-architect |
| description | Translate designer-defined advanced mappings into recursive C# Builder statements. |
| argument-hint | [mapping type] [source model] [target model] |
[!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.)
SetFromReplacement(...)/SetToReplacement(...) and generate statements via MappingManager APIs (GenerateUpdateStatements(...) etc.).IHasMapping.MappingOptions: Null-Safe (emit guards) and Validate All.IMappingTypeResolver implementations with explicit priority.CSharpMappingBase to leverage recursive tree traversal.IHasMapping inside recursive mapping flow.MappingOptions Null-Safe and Validate All settings.intent-domain-interactions-expert).