Обзор

Portable Codex skills and research notes for Minecraft Bedrock JSON UI. This repository is designed to be usable as a standalone GitHub project, not just as a local note dump. The goal is simple: - install the skills once - keep all important JSON UI references inside this repository - let Codex route itself to the right subtopic instead of loading everything every time Use this repository when you want Codex to work well on: - Bedrock JSON UI - HUD and chat driven UI - title and actionbar text protocols - server_form.json customization - chest or furnace based custom UIs - addon RP/BP integration - vanilla texture path lookup - schema validation and VSCode setup - JSON UI editing workflows and builder examples It is written in Minecraft Bedrock addon, RP/BP, Script API, and server-protocol terms, not generic web UI terms.

README

MCBE JSON UI Master AI

Portable Codex skills and research notes for Minecraft Bedrock JSON UI.

This repository is designed to be usable as a standalone GitHub project, not just as a local note dump.
The goal is simple:

install the skills once
keep all important JSON UI references inside this repository
let Codex route itself to the right subtopic instead of loading everything every time

What this repository is for

Use this repository when you want Codex to work well on:

Bedrock JSON UI
HUD and chat driven UI
title and actionbar text protocols
server_form.json customization
chest or furnace based custom UIs
addon RP/BP integration
vanilla texture path lookup
schema validation and VSCode setup
JSON UI editing workflows and builder examples

It is written in Minecraft Bedrock addon, RP/BP, Script API, and server-protocol terms, not generic web UI terms.

What is included

Skills

mcbe-json-ui-basics
mcbe-json-ui-master
mcbe-json-ui-foundations
mcbe-json-ui-logic
mcbe-json-ui-hud-and-chat
mcbe-json-ui-server-forms
mcbe-json-ui-patterns
mcbe-json-ui-visual-design
mcbe-json-ui-ir-authoring
mcbe-json-ui-tools-runner
mcbe-json-ui-reference
mcbe-json-ui-samples
mcbe-json-ui-debugging
mcbe-json-ui-addon-integration
mcbe-json-ui-vanilla-assets
mcbe-json-ui-research
mcbe-json-ui-schemas
mcbe-json-ui-tooling
mcbe-json-ui-vanilla-presets
mcbe-json-ui-self-bootstrap

Local pack references

references/source-packs/modern-cloud-ui-reference/
references/source-packs/farm-ui-variants/
references/source-packs/rpg-server-ui-reference/

Local utility mirrors

references/local-utils/json-ui-utils/
references/local-utils/integrated-sample/

External mirrored references

references/external/bedrock-wiki-json-ui/
references/external/json-ui-examples/
references/external/EasyUIBuilder/
references/external/Chest-UI/
references/external/bedrock-json-ui-editor/

Schema references

references/schemas/Blockception/
references/schemas/DJStompZone/

Source policy

This repository uses a strict source priority model:

included local working packs in references/source-packs/
official verified sample source bedrock-samples
community reference docs JSON UI pages
vanilla resource mirror for vanilla asset truth

For vanilla texture validation, the canonical upstream authority is:

See:

Quick start

1. Clone

git clone https://github.com/boredape874/mcbejsonuimasterAI.git
cd mcbejsonuimasterAI

2. Install the skills into Codex

.\scripts\install-skills.ps1

This copies every directory under skills/ into:

%USERPROFILE%\.codex\skills\

3. Optional: sync the upstream vanilla pack mirror

.\scripts\sync-ztech-vanilla.ps1

That creates:

references/upstreams/MCBVanillaResourcePack/

This mirror is intentionally not committed to Git because it is large and reproducible.

4. Optional: sync selected verified sample source `bedrock-samples` UI files

.\scripts\sync-bedrock-samples-ui.ps1

This updates:

references/official/bedrock-samples-ui/

5. Optional: sync the MCBE JSON UI resource archive

.\scripts\sync-mcbe-json-ui-resource.ps1

That creates:

references/upstreams/mcbe-json-ui-resource/

This mirror is intentionally not committed because it is large and searchable.

6. Optional: validate a JSON UI pack or reference mirror

.\scripts\validate-json-ui-pack.ps1 -PackPath references\source-packs\modern-cloud-ui-reference

For partial reference mirrors:

.\scripts\validate-json-ui-pack.ps1 -PackPath references\official\bedrock-samples-ui -AllowPartialUiDefs -AllowMissingTextures

7. AI tools layer (Node)

If your AI client uses AGENTS.md, it can self-bootstrap on first open. To prepare manually:

npm install
node tools/setup.mjs

Then, for any layout work:

npm run validate:sources
npm run source:scan
npm run catalog:build
npm run design:search -- button
npm run asset:search -- button --category textures/buttons
npm run asset:catalog
npm run asset:context -- button --state hover --json
npm run corpus:inventory -- --root "" --out workspace/corpus-local/archive
node tools/init-project.mjs --list-templates
node tools/init-project.mjs rpg_status --template rpg_hud
node tools/run.mjs workspace/rpg_status/ir.yaml
npm run preview -- workspace/rpg_status/ui.json workspace/rpg_status/solved.json
node tools/validate-pack.mjs  --report workspace/pack-report.json
npm run eval:offline
npm run check

For private development packs or a local asset library, copy config/sources.local.example.json to the Git-ignored config/sources.local.json, replace only the placeholders you use, and validate that local file explicitly. The public source config never contains those paths.

Available project templates are minimal, rpg_hud, and rpg_menu. The solve step uses the Go geometry solver when go is installed and falls back to the Node solver otherwise. Its build cache stays under .agent/cache/, so restricted environments do not need access to the user profile cache. For server-form or HUD repeated rows, model the area as collection_grid; for labels and images whose footprint is content-driven, use IR auto_size before hand-finishing bindings and textures.

corpus:inventory discovers a broad local example archive as neutral local-only sources and extracts UI controls, geometry, texture references, protocols, and recipe candidates without copying originals. source:scan reads registered UI entry files and directly referenced assets. asset:catalog connects the local asset index to observed JSON UI usage, roles, states, dimensions, alpha, palettes, and same-stem nine-slice evidence; asset:context converts that evidence into a source-redacted texture-generation brief. catalog:build, design:search, and asset:search provide the narrower recipe and fallback lookup paths. preview writes deterministic PC/touch state images, a contact sheet, coordinates, and unsupported-property evidence.

validate-pack.mjs parses JSON and JSONC UI files, checks _ui_defs.json, namespaces, control structure, collection bindings, and local or indexed vanilla texture references. eval:offline runs the fixed seven-example structural and visual suite. eval:live deliberately remains incomplete until real Bedrock screenshots and content-log evidence are supplied. npm run check combines the repository audit with the complete test suite.

See AGENTS.md, docs/41-ir-spec.md, docs/42-tools-reference.md.

How to use it with Codex

Recommended default

If the request is broad, use:

Use mcbe-json-ui-master.

If the request is beginner-oriented or first needs the mental model, use:

Use mcbe-json-ui-basics and mcbe-json-ui-master.

That skill routes into smaller topic files such as:

basics
foundations
logic
hud-chat
server-forms
patterns
debugging
addon
vanilla
research
schemas
tooling
best-practice-oriented pattern selection

For token efficiency, the master skill is designed to read one router, one topic index, and only the exact subtopic files needed for the request.

Typical prompts

General JSON UI work

Use mcbe-json-ui-master and fix this hud_screen.json layout.

Beginner explanation or onboarding

Use mcbe-json-ui-basics and explain how Bedrock JSON UI is loaded, what _ui_defs.json does, and how HUD files fit together.

`_ui_defs.json` or namespace problems

Use mcbe-json-ui-foundations and explain why this screen is not loading.

Title/actionbar/chat parsing

Use mcbe-json-ui-logic and mcbe-json-ui-hud-and-chat for this title-based HP bar.

Server forms

Use mcbe-json-ui-server-forms and convert this server form protocol into server_form.json routing.

Reusable UI patterns

Use mcbe-json-ui-patterns and build a chest-like menu with a progress bar.

Local utility adaptation

Use mcbe-json-ui-patterns and mcbe-json-ui-hud-and-chat, and adapt the local topbar chat notification utility into this pack.

Vanilla path lookup

Use mcbe-json-ui-vanilla-assets and verify the correct vanilla texture path for this icon.

Vanilla asset usage, not just path lookup

Use mcbe-json-ui-vanilla-assets and explain how to find the right Bedrock vanilla UI texture, item icon, or block icon path for this JSON UI control.

Schema setup

Use mcbe-json-ui-schemas and set up VSCode json.schemas for ui, _ui_defs, and _global_variables.

Tooling workflows

Use mcbe-json-ui-tooling and explain whether bedrock-json-ui-editor or EasyUIBuilder fits this task better.

Use with any AI (MCP-free)

Any AI client that can read files and run terminal commands works with this kit:

Cursor, Claude Code, Codex, GitHub Copilot, Continue, Aider, etc.
The AI reads AGENTS.md first, performs self-bootstrap if needed, then routes layout work through tools/*.mjs and bindings/animation work through the existing knowledge-layer skills.

Typical user flow:

1. git clone 
2. open the folder in your AI client
3. ask "build a centered confirmation modal with two symmetric buttons"
   -> AI authors workspace//ir.yaml, runs node tools/run.mjs, returns ui.json

For layout-only work the kit is deterministic: same IR -> same JSON UI.

Repository layout

skills/
- portable Codex skills
docs/
- concept maps, source priority, usage and research guides
references/
- source-packs/, official/, external/, local-utils/, schemas/, and optional upstreams/
templates/ir/
- deterministic minimal, compact RPG HUD, and asymmetric RPG menu layout starters
examples/prompts/
- copy-paste prompt examples for Codex
examples/tasks/
- task templates that pair a real objective with the right skill flow
examples/vscode/
- workspace settings templates for schema-aware editing
scripts/
- installation and sync helpers
AGENTS.md, .agent/, tools/, schemas/, data/, vanilla-index/, workspace/
- AI tools layer (Node CLI). See docs/41 through docs/45 and AGENTS.md.
- data/jsonui-spec.json (control/anchor/binding catalog, ported from gamezaSRC/JSON-UI-Web-Editor MIT) and data/presets-catalog.json (vanilla preset references) drive the validator and the IR extends field.

Ready-made examples

If you want something other people can use immediately after cloning, start here:

examples/prompts/README.md
examples/tasks/README.md
examples/v2/README.md — seven complete RP/BP design-system examples
data/design-recipes.public.json — checked-in redistribution-safe measured recipes

Prompt examples are for direct copy-paste. Task examples are for slightly longer guided work where the AI should inspect files, trace dependencies, and then patch the pack.

Is this enough to become a “JSON UI Master AI” in one shot?

Pragmatically: almost, yes.

What this repository now gives you:

portable skills
layered topic routing
beginner-to-advanced mental model docs
local working pack references
local utility mirrors for topbar, title bars, tablist, tooltip, and integrated sample screens
mirrored community reference docs JSON UI docs
mirrored external example repositories
schema references
vanilla asset authority flow
source-tiered measured recipes and a local UI asset search contract
PC/touch state previews, fixed offline evaluation, and public-release leak checks

What it does not magically guarantee:

perfect answers for every future Bedrock version without updates
runtime truth from schema files alone
correct behavior when a pack has hidden dependencies outside the copied files

So the right claim is:

this repository is now a strong portable base for an MCBE JSON UI specialist Codex, and it is structured so it can keep improving without collapsing into one giant unreadable skill

Current state

If you clone this repository and run:

.\scripts\install-skills.ps1

you get a working, installable MCBE JSON UI skill suite immediately.

The checked-in v2 examples and public catalog are statically validated. Bedrock runtime rendering, input, bindings, and content-log status remain separate evidence and are not claimed until eval:live receives real captures.

View this README on GitHub

Установка

npx skillfish add boredape874/mcbejsonuimasterai