Run any Skill in Manus with one click

mcbe-json-ui-basics

Stars43

Forks5

UpdatedApril 29, 2026 at 13:17

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

boredape874

boredape874/mcbejsonuimasterAI

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	mcbe-json-ui-basics
description	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.

MCBE JSON UI Basics

Use this skill when the task first needs the Bedrock mental model.

Workflow

Read references/basics-map.md.
Explain Bedrock JSON UI in resource-pack terms, not generic web UI terms.
Prefer practical rules over fake certainty.
State clearly when a rule is a hard requirement, a common pattern, or only a convenient authoring habit.

Hard rules

Do not claim Bedrock has one fixed screen size.
Do not describe JSON UI files as isolated from the rest of the resource pack.
Do not treat schema validation as proof that the UI will render correctly.
If the user moves from basics into a concrete implementation, route to mcbe-json-ui-master or the narrower specialized skill.

More from this repository

same repository

mcbe-json-ui-custom-toggles

boredape874/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.

2026-05-0143

mcbe-json-ui-hud-and-chat

boredape874/mcbejsonuimasterAI

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.

2026-05-0143

mcbe-json-ui-logic

boredape874/mcbejsonuimasterAI

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.

2026-05-0143

mcbe-json-ui-master

boredape874/mcbejsonuimasterAI

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.

2026-05-0143

mcbe-json-ui-patterns

boredape874/mcbejsonuimasterAI

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.

2026-05-0143

mcbe-json-ui-ir-authoring

boredape874/mcbejsonuimasterAI

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.

2026-04-3043

name	mcbe-json-ui-basics
description	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.

MCBE JSON UI Basics

Use this skill when the task first needs the Bedrock mental model.

Workflow

Read references/basics-map.md.
Explain Bedrock JSON UI in resource-pack terms, not generic web UI terms.
Prefer practical rules over fake certainty.
State clearly when a rule is a hard requirement, a common pattern, or only a convenient authoring habit.

Hard rules

Do not claim Bedrock has one fixed screen size.
Do not describe JSON UI files as isolated from the rest of the resource pack.
Do not treat schema validation as proof that the UI will render correctly.
If the user moves from basics into a concrete implementation, route to mcbe-json-ui-master or the narrower specialized skill.