Verify In Runtime
Description
# Verify a Fix in the Running App A contributor workflow for proving a fix in a **real Mendix app in a real browser**, rather than at the BSON or parser layer. This is the outermost verification tier. It is slow (~5 min the first time, ~2 min after) and it is not needed for most fixes — read *When This Is Required* before reaching for it. ## When This Is Required Use the layer where the symptom actually lives: | Symptom lives in | Sufficient proof | |------------------|------------------| |
Installation
Installs to ~/.claude/skills/mendixlabs-mxcli-verify-in-runtime/SKILL.md
mkdir -p ~/.claude/skills/mendixlabs-mxcli-verify-in-runtime && curl -fsSL https://raw.githubusercontent.com/mendixlabs/mxcli/HEAD/.claude/skills/verify-in-runtime.md -o ~/.claude/skills/mendixlabs-mxcli-verify-in-runtime/SKILL.md Restart Claude Code, or start a new session, for it to be picked up.
Full documentation available on GitHub
View Source RepositoryRelated Skills
Awesome Go
A curated list of awesome Go frameworks, libraries and software
Development next.js
| The React Framework | 138360 | 1503 | 1 |
Development sharing-skills
skill for guidance.
Development root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger.
Development Template Skill
Minimal skeleton for a new skill project structure.
Development Third-party Notices
THE FOLLOWING SETS FORTH ATTRIBUTION NOTICES FOR THIRD PARTY SOFTWARE THAT MAY BE CONTAINED IN PORTIONS OF THI
Development