Skip to content

m4bwav/minewright

v0.1.1MIT

Evergreen skills for building Minecraft Bedrock add-ons with AI coding agents: design rules and Script API patterns that hold up, project layout and packaging with current module versions, one-command static checks, live self-tests on Bedrock Dedicated Server, and HUD work with a vanilla fallback. Each skill re-researches its subject on a schedule and carries the evals that prove it triggers and acts.

minewright-checks

Check a Minecraft Bedrock add-on without the game before saying a change is done: one script (mw_check.py) checks that every pack JSON parses (comments allowed), the manifests (format_version 2, unique UUIDs, versions, dependencies, script entry, beta modules flagged), identifiers (one namespace, client entities, textures, geometry, render controllers exist), entity components valid for their format_version, then tsc, ESLint, npm test and optional Creator Tools validation, in one JSON report. Use whenever the user asks to 'check my add-on', 'validate the behavior pack', 'why is my entity invisible', 'missing texture', 'does my manifest look right', 'lint the Minecraft scripts', 'run the tests', 'checks were skipped, is it verified', after the agent edits pack JSON or Script API code, or says 'refresh minewright-checks'. Running the add-on on a real server is minewright-server; project setup and packaging are minewright-project.

Read SKILL.md at the source

Pinned to revision 0b851682a051, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.