docs: add mxbuild setup & mx tool skill

[engalar]

Summary

• Add mxbuild-setup.md skill to .claude/skills/mendix/ for end-user delivery via mxcli init
• Covers mxbuild download, mx check validation, and mx create-project usage
• Addresses common AI agent mistakes: incorrect mx create-project syntax, missing mxcli docker check wrapper

Test plan

• Baseline test: agent without skill uses wrong mx create-project syntax (mx create-project /path)
• With skill: agent correctly uses --app-name flag and cwd-based output
• With skill: agent recommends ./mxcli docker check over direct mx check
• With skill: agent uses end-user paths (./mxcli) not dev paths

🤖 Generated with Claude Code

[ako]

Review: Overlap with docker-workflow.md + factual concern

Overlap

Most of this content already exists in .claude/skills/mendix/docker-workflow.md:

• mxcli setup mxbuild with --version, -p, --dry-run variants (lines 78-88)
• mx create-project usage (lines 55-66)
• mxbuild cache locations (line 92)
• Troubleshooting: mxbuild not found, StudioPro.conf.hbs (lines 394-399)
• Runtime-to-mxbuild copying workaround (lines 96-105)

Factual concern

This skill says mx create-project "does NOT accept an output path argument", but docker-workflow.md already documents:

~/.mxcli/mxbuild/{version}/modeler/mx create-project --app-name MyApp --output-dir /path/to/my-app

One of these is wrong. Please verify whether --output-dir exists before merging.

What's worth keeping

• The "Common Workflow: Modify and Validate" 3-step recipe
• Emphasizing ./mxcli docker check over direct mx check for end-user context
• Blank project security caveat (no demo users)

Suggestion

Either trim this skill to only the non-overlapping content, or fold the useful bits into docker-workflow.md instead of creating a second skill that covers the same ground.

[engalar]

Investigation: --output-dir exists

Verified with mx v11.6.4:

$ ~/.mxcli/mxbuild/11.6.4/modeler/mx create-project --help

Usage: mx create-project [template-mpk-file]

Options:
  --app-name                    The name of the application.
  --output-dir                  Create the project in this directory.
  --language-code               Set the language code of the project.
  --sprintr-app-id              Set the App ID of Sprintr project.
  --use-mpr-format-v1           (Default: false) Use the MPR storage format version 1

So docker-workflow.md is correct — --output-dir is a valid flag. The new skill's claim that mx create-project "does NOT accept an output path argument" is wrong.

Agree with your suggestion to fold the non-overlapping content into docker-workflow.md rather than maintaining a second skill with mostly duplicate (and partially incorrect) information.

[github-actions]

AI Code Review

Critical Issues

• None

Moderate Issues

• None

Minor Issues

• Documentation inconsistency: The PR description states it adds a new skill file mxbuild-setup.md, but the diff only shows an edit to docker-workflow.md. If the PR is missing the new skill file, this is incomplete. However, since only one file diff was provided, we review what's visible.

What Looks Good

• The added caveat in docker-workflow.md is accurate: blank Mendix projects created via mx create-project indeed lack demo users, causing login failures until security is configured.
• The reference to manage-security.md is correct and helpful for users needing to set up demo users.
• The change is minimal, focused, and addresses a common point of confusion for newcomers.

Recommendation

Approve the visible change (the caveat addition to docker-workflow.md). However, verify that the PR also includes the promised mxbuild-setup.md skill file if the description is accurate. If the new skill file is missing, request its addition before merging. Based solely on the provided diff, the documentation improvement is sound.

---

Automated review via OpenRouter (Nemotron Super 120B) — workflow source