Getting Started

minewright installs nothing on its own. The skills are instructions your agent reads, plus two standard-library Python scripts. Node packages, Mojang's Creator Tools, Bedrock Dedicated Server (which comes under the Minecraft EULA) and any Windows network exemption are left to you to approve.

What you need

• An agent that reads Agent Skills: Claude Code, GitHub Copilot (Copilot CLI and VS Code), Codex, Cursor, or another that looks in a skills folder.
• Python 3.9 or later for mw_check.py and bds_run.py. CI runs both on 3.9 and 3.14, on Linux, macOS and Windows.
• Node for your add-on's TypeScript build. The example add-on asks for Node 24 ("engines": { "node": ">=24" }), because its tests run .ts files directly through Node's type stripping. Creator Tools needs Node 22 or later.
• For live tests, a Windows or Linux x64 machine: Bedrock Dedicated Server ships for those two only. On macOS use a Linux VM or container.

Claude Code

Add the repository as a plugin marketplace and install from it:

/plugin marketplace add m4bwav/minewright
/plugin install minewright@minewright

Not tested in this wiki pass: the marketplace install itself. The manifests it reads (.claude-plugin/plugin.json and marketplace.json) are checked by tests/check_skills.py in CI.

Copilot, Codex, Cursor and other agents

Clone the repository somewhere stable and link each folder under skills/ into the agent's skills folder. On Windows a junction needs no admin rights:

git clone https://github.com/m4bwav/minewright
foreach ($s in Get-ChildItem minewright\skills -Directory) { New-Item -ItemType Junction -Path "$HOME\.agents\skills\$($s.Name)" -Target $s.FullName }

On macOS or Linux, a symbolic link per skill:

git clone https://github.com/m4bwav/minewright
for s in minewright/skills/*/; do ln -s "$PWD/$s" ~/.agents/skills/; done

Where each agent looks:

Agent	Skills folder
Claude Code	~/.claude/skills/
Copilot CLI, Codex and several others	~/.agents/skills/
VS Code Copilot	~/.copilot/skills/, and a repository's .github/skills/
Cursor	.cursor/skills/

Linking rather than copying keeps the skills current with git pull, and the skills update their own version numbers and API notes on a schedule (Research and freshness).

First use

Ask in plain words. Each skill's description lists the phrases it answers to, and names the sibling that owns the request next door:

You say	Skill that answers
"make a Minecraft add-on where...", "is this API current", "what should we playtest"	minewright-workflow
"start a Bedrock add-on", "what version of @minecraft/server", "build the mcaddon", "my add-on won't import"	minewright-project
"check my add-on", "why is my entity invisible", "missing texture"	minewright-checks
"test my add-on on a server", "run the self-test", "does it actually load"	minewright-server
"a timer on screen", "show the item in the middle of the screen", "JSON UI"	minewright-hud

A new add-on starts with a one-pager (docs/ONE-PAGER.md) that the agent shows you before it writes code. See Design and Script API.

With Mojang's Creator Tools

Creator Tools ships its own agent plugin, MCP server and skills for creating mobs, items and blocks and for validation. The two work side by side. When it is installed, minewright-workflow uses its create-* skills for content scaffolding, and mw_check.py --mct runs its validator as one more check.

Next

• Install an add-on on a device: Platforms and install.
• See the whole loop on a real add-on: The given.jar example.