MDL game packages are designed to work well with Git and code agents. Keep the package as the reviewable source, use deterministic CLI checks, and treat hosted pushes as deliberate staging actions.
Agentic engineering works best when the source of truth is a normal repository with stable paths and text-first artifacts. MDL packages keep prompts, manifests, schema, openings, and published asset rules in files that can be reviewed directly.
mdl diff to inspect the change set against the hosted dev workspace.mdl push only when the diff matches your intent.Some packages have a dedicated agent skill that gives a code agent the package's local source map, common edit targets, and ownership boundaries. Use those skills for package authoring work, then keep the normal MDL review, hash, diff, and sync loop as the platform handoff.
For example, the Monte Lua package skill lives in the MDL checkout at .agents/skills/montelua-game-package/SKILL.md. It is for work inside ./montelua, including prompt files, manifests, structured-output schema, authored openings, game-owned assets, and bootstrap content that is synced into the hosted montelua workspace.
Reach for a package skill when the change belongs to the game package: narrative behavior, world rules, package metadata, schema enum values, openings, or game-owned assets. Use the MDL docs and CLI reference when the question is about package transport, hosted workspace behavior, authentication, diff output, release controls, domains, billing, monitoring, or runtime/platform semantics.
The boundary matters. Package files describe the game. MDL owns the engine, hosted runtime, sync APIs, public workspace, release workflow, and player-facing platform behavior. A package skill can help make local edits, but it should not be treated as permission to bypass hosted review or directly edit live hosted state.
A dedicated skill can guide local edits and verification, but mdl diff is still the check that compares the package inventory with the hosted dev container. Push only after reviewing both the Git diff and the MDL diff.
The package is the place for deterministic edits and code review. The hosted dev workspace is where those reviewed changes are staged for platform inspection. Live release should still require an explicit platform action.
assets.published globs accidentally