mcbejsonuimasterAI

Design, debug, and implement custom Minecraft Bedrock JSON UI toggles, toggle animation illusions, hover/focus visuals, toggle-state factories, and button-event alternatives. Use when working with common.toggle, common_toggles, ui_template_toggles.json, local button/toggle templates, focus border colors, hover animation, or toggle-driven UI animation in Bedrock JSON UI.

Build, analyze, and debug Bedrock HUD and chat driven UI. Use when Codex must work on `hud_screen.json`, `chat_screen.json`, scoreboard injection, title overlays, actionbar driven UI, bottom chat panels, hidden chat protocol messages, Java-style locate chat helpers, clickable chat command shortcuts, desktop/touch HUD menus, chunk or minimap overlays, or message-protocol-based HUD behavior in Minecraft Bedrock JSON UI.

Explain and implement Bedrock JSON UI logic rules. Use when Codex must analyze bindings, preserved text, string slicing, printf-style `%.s` text formatting, fixed-width payloads, first-line extraction, chat locate-message parsing, actionbar or title driven protocols, visibility expressions, value extraction, and condition-based UI behavior in Minecraft Bedrock JSON UI.

Comprehensive Minecraft Bedrock JSON UI master skill. Use when Codex must handle Bedrock JSON UI end to end across basics and mental models, pack structure, HUD, chat, chat command helpers such as Java-style locate parsing, title or actionbar driven UI, server form customization, bindings and string parsing logic, reusable patterns, large UI toolkit architecture, desktop/touch HUD splits, quick-container utilities, addon integration, debugging, vanilla texture path lookup, source selection across local sample packs, local utility mirrors, official sample screens, community reference docs, and vanilla resource mirror, or schema and tooling workflows such as JSON UI editors, builders, and schema-based validation.

Reuse proven Bedrock JSON UI patterns from included sample packs and local utility mirrors. Use when Codex must build or adapt animated progress bars, topbar notifications, scoreboards, chest or pocket containers, quick-container utilities, desktop/touch HUD menus, reusable presets, custom chat panels, static start-screen backgrounds, tablist overlays, text-slicing snippets, or similar recurring Minecraft Bedrock JSON UI patterns.

Use when the user asks for layout, positioning, alignment, symmetry, equal spacing, or pixel-correct sizing of Bedrock JSON UI elements. Translates the user's intent (prompt or annotated image) into the IR YAML described in docs/41-ir-spec.md and schemas/ir.schema.json. Pairs with mcbe-json-ui-tools-runner to compile the IR into JSON UI.

Use to execute the kit's deterministic Node CLI under tools/* (ir-validate, solve, compile, validate, run, build-vanilla-index, init-project, render, diff). Knows the call order, expected exit codes, output files, and how to react to failures by editing the IR rather than the compiled JSON UI.

Analyze and implement Bedrock JSON UI server form customization. Use when Codex must modify `server_form.json`, long or custom form routing, chest or furnace form substitution, title-prefix based form detection, custom server form button grids, image rows inside forms, polished form shells, or multi-form factory patterns in Minecraft Bedrock JSON UI.

Validate and reason about Minecraft Bedrock JSON UI using schema sources. Use when Codex must compare or use Blockception, DJStompZone, or Bugrock JSON UI schema files, configure VSCode `json.schemas`, inspect schema coverage for `ui`, `_ui_defs`, `_global_variables`, or sprite UI metadata, or explain what schema validation can and cannot guarantee for Bedrock JSON UI.

Analyze Minecraft Bedrock JSON UI as part of a full addon or resource-pack stack. Use when Codex must connect UI files to custom textures, fonts, blocks, entities, attachables, animations, or broader addon asset structure rather than treating JSON UI as isolated files.

Explain the fundamentals of Minecraft Bedrock JSON UI in practical addon terms. Use when Codex must teach or reason about what a resource pack is, how JSON UI files are loaded, what `_ui_defs.json` and screen files do, how screens differ from templates, how Bedrock layout works across device sizes, or when a task is beginner-oriented and needs a correct mental model before implementation.

Diagnose Bedrock JSON UI failures. Use when Codex must find why a screen does not render, a server form does not replace, a HUD panel stays hidden, a binding-derived value is wrong, a chat or actionbar protocol is misparsed, or a texture path or pack dependency breaks Minecraft Bedrock JSON UI behavior.

Explain and apply the core structure of Minecraft Bedrock JSON UI. Use when Codex needs to reason about `_ui_defs.json`, namespace layout, screen registration, modifications, factories, panel insertion, and the resource-pack file structure behind Bedrock JSON UI.

Research and route Minecraft Bedrock JSON UI questions to the right authority. Use when Codex must decide whether to rely on local sample packs, official sample screens, community reference docs JSON UI pages, or vanilla resource mirror, and when answers need explicit confirmation vs inference labeling.

Use when an AI agent opens this repository for the first time, or when tools/* commands fail. Runs the AGENTS.md self-bootstrap protocol (Node check, npm install, workspace + state, optional vanilla-index) via tools/setup.mjs and tools/doctor.mjs without modifying the user's system.

Use tools and tool-generated references for Minecraft Bedrock JSON UI work. Use when Codex must reason about visual JSON UI editing, builder-generated UI examples, chest-like form tooling, AUX ID generation, vanilla JSON UI dumping, dynamic-form-library-style form libraries, or practical authoring workflows from bedrock-json-ui-editor, builder-sample, container-form-sample, bedrock-auxgen, JSON-UI-Dumper, and dynamic-form-library.

Verify and use vanilla Minecraft Bedrock texture and icon paths for JSON UI. Use when Codex must confirm `textures/ui/*`, item icon atlas entries, block icon atlas entries, vanilla screen file names, or explain how to find and apply the correct vanilla asset source without hallucinating nonexistent paths. Use vanilla resource mirror as the upstream asset authority.

Use when the user asks for a screen that should reuse vanilla MCBE preset frames (modals, dialogs, form bodies, content buttons, scrolling panels). Pairs the IR `extends` field with `data/presets-catalog.json` to emit `id@common_dialogs.main_panel_no_buttons` style references with correct `$variables` instead of hand-rolling the entire skeleton.