mendix-extension-boundarylisted

# Skill: Mendix Extension Boundary ## Intent Ensure Mendix-related requirements respect the boundary between generated code, Mendix model artifacts, Java actions, microflows, integrations, and platform deployment constraints. This skill prevents generic code generation from corrupting low-code platform structure. ## Use when Use this skill when a REQ touches Mendix applications, Mendix modules, Java actions, microflows, nanoflows, domain models, REST integrations, OData, custom widgets, marketplace modules, deployment packages, or on-prem Mendix runtime behavior. ## Do not use when Do not use this skill for unrelated JavaScript/Python/backend work that does not interact with Mendix artifacts or runtime constraints. ## Signals - The REQ mentions Mendix, Studio Pro, module, microflow, nanoflow, Java action, entity, domain model, custom widget, marketplace module, OData, published REST service, consumed REST service, deployment package, runtime, or on-prem installation. - Acceptance criteria involve low-code artifacts plus generated code. - TECH_CONSTRAINTS references enterprise/on-prem Mendix runtime. ## Required behavior - Treat Mendix model artifacts as governed platform assets, not arbitrary text files. - Keep generated custom code inside safe extension points. - Document which changes are intended for Studio Pro/manual import versus generated source. - Keep Java actions, widgets, and integration helpers compatible with the target Mendix runtime/version when known