Gracefully close Mendix Studio Pro + its children (runtime, MxBuild, Java helpers) and clean up orphan toolchain from a previous crash. Sends WMCLOSE first; reports counts of what was closed. Default project: TestOSApp3 testbed; default port: 8082.
Fresh-context reviewer for a proposed Mendix design. Audits against the /mx-discover inventory for naming collisions, anti-patterns, missing tests, security, marketplace overlap, migration risk. Read-only.
Mendix-specialized domain inventory. Auto-uses mendix-expert subagent. Refuses to proceed to design until in-scope entities, microflows, and module overlaps are on the table. Born from the NextBestAction rewrite.
Generate copy-paste-ready Studio Pro instruction sheets when a human-in-loop step is required. Exact paths, classes, widgets, bindings -- no vague guidance. Auto-runs verification (mx-doctor + impact + playwright) after the human replies "done".
Blast-radius analysis for a Mendix entity/attribute/microflow/page. Read-only. Answers "what breaks if I rename or change X?" before the change. Wraps mxcli refs/callers/impact.
GATED WRITE. Clone a Mendix page to a new name + optional entity rebinding via the mxcli MDL round-trip. Routes through the shadow-write engine (7 safety pillars). Pre-classifies the source as SIMPLE / COMPLEX / UNCLONEABLE; refuses UNCLONEABLE, requires --allow-lossy on COMPLEX. Auto-emits a /mx-handoff sheet for…
GATED WRITE. Scaffold a new Mendix microflow with the 8 safety pillars. Pre-tag, clean-tree check, Studio Pro lock check, version check, pre/post mx check, auto-restore on fail.
Drive Playwright against the testbed (port 8082). MANDATORY testbed-fingerprint guard (URL :8082 + "Test Project" ribbon) before any other assertion -- safety gate against driving the live project.
Resolve the Mendix Studio Pro version of a project, inventory installed Studio Pro / mx / mxcli binaries, and report mismatches. Read-only.
★not rated 3▲
+1 4mo agoA30 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: