minecraft-modding-workbench
Minecraft Modding Workbench
Support fast, version-aware Minecraft modding. Treat the minecraft-modding
MCP server as the primary source of truth, then turn verified findings into
working code and assets.
Scope
- Supports Fabric, NeoForge, and Architectury.
- Requires the
minecraft-moddingMCP server from@adhisang/minecraft-modding-mcp. - Prefer project-aware MCP calls when a workspace exists. Reuse the repository root as
projectPath. - Use the high-level v3 entry tools first:
inspect-minecraft,analyze-symbol,compare-minecraft,validate-project,analyze-mod, andmanage-cache. - Covers Forge-style access transformers through
validate-project(taskaccess-transformer) for NeoForge, in addition to Fabric-style access wideners. - Use the NBT helpers (
nbt-to-json,json-to-nbt,nbt-apply-json-patch) when working with level.dat, chunk, playerdata, or command-driven NBT. Stay in typed JSON while editing and re-encode once at the end.
Default Behavior
- Produce runnable feature slices, not generic advice.
- Infer loader, version, mappings, modid, package, Java version, and project conventions from the workspace before asking questions.
More from adhi-jp/agent-skills
review-scope-guard
Use when Codex or code/plan review findings need Definition-of-Done scope triage, especially to separate must-fix issues from minimal hygiene, out-of-scope hardening, repeated noise, or self-induced refinements. Also use when codex-review-cycle invokes scope guard between validity checking and summary render. Do not use for single-shot lint or unrelated changes.
34codex-review-cycle
Use when the user explicitly asks to run an iterative Codex review cycle on a non-empty git diff, including working-tree changes, current branch vs base, explicit commit/tag/branch refs, code diffs, or Markdown planning documents. Do not use for one-shot reviews, auto-hardening, background checks, plan drafting, or empty review targets.
34writing-style-guide
Use when generating or editing user-facing prose, including docs, comments, READMEs, changelogs, commit messages, PR descriptions, and chat replies.
32review-fix-cascade-guard
Use when applying user-selected review findings after scope triage, especially inside codex-review-cycle or after a standalone Codex adversarial review, and a line-scoped fix may create follow-on valid findings. Do not use for ordinary edits, plan drafting, single-shot lint, no-review contexts, or generic refactor checklists.
19vibe-planning
>
17vibe-plan-execution
Use when the user asks to execute, implement, continue, or apply an existing implementation plan, specification, acceptance criteria, task plan, or vibe-planning output. Do not use for plan creation or coding requests with no concrete plan to bind.
17