菜单
Add a context menu item, new element, or association creation option to a foreign package, element, or association end. Covers packageExtension and elementExtension patterns.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 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 | add-designer-extension |
| description | Add a context menu item, new element, or association creation option to a foreign package, element, or association end. Covers packageExtension and elementExtension patterns. |
| argument-hint | [target element/package type name and what to add] |
[!TIP] Read more if you want to know about designer extensions, package/element extensions, mapping options, or context menu items:
- Conceptual Reference
- Workflow & Common Mistakes (To conserve tokens, avoid reading these files for simple or minor updates.)
Extend an existing element, package, or association end from a foreign module by adding new context menu options (e.g. child element/association creation or mapping options).
typeId via MCP find_designer_elements or generated C# SpecializationTypeId constants.Designer Settings to foreign designer GUID (Domain: 6ab29b31-27af-4f56-a67c-986d82097d63, Services: 81104ae6-2bc5-4bae-b05a-f987b0372d81).Type Reference Extension Settings (Mode = Inherit) and Extension Settings stereotypes.[context menu] child element.Association Creation Option to target end of association settings.get_designer_validation_errors and generated .designer.settings file.Mode = Inherit on Type Reference Extension Settings for element extensions..designer.settings directly (always change the Module Builder model).