boredape874/mcbejsonuimasterai/mcbe-json-ui-vanilla-presets

MCBE JSON UI — Vanilla Presets

Use this skill when:

Evidence first, skill second

Research the real evidence before applying anything written in this skill, and say which step answered:

1. The target pack itself: its _ui_defs.json, manifests, the files the request names, and the current Content Log.
2. Pinned official vanilla evidence: references/official/bedrock-samples-ui at the revision in references/official/bedrock-samples-ui.lock.json, node tools/vanilla-name-check.mjs <name> for any control, #binding, $variable, button id, renderer or screen file, the full local mirror under references/upstreams/bedrock-samples when present, and docs/83-vanilla-ui-1.26.50-diff.md for names that moved or disappeared.
3. Registered upstream sources and their cards: node tools/design-library.mjs sources --source ID and node tools/design-library.mjs patterns --source ID for the official docs, Wiki snapshots, schemas and sample addons pinned in config/design-research-lock.json (commit-pinned raw URLs for every file), then the repository docs/.
4. Only when steps 1–3 do not answer: this skill's own references. Label such guidance "inferred from skill guidance", never "confirmed".

A name, offset, selector or rule found in steps 1–3 overrides this skill. Older third-party references and example packs stay valid pattern evidence; do not delete or rewrite them because a vanilla name moved. Without this repository checkout, follow the same order with the official samples and docs you can reach and report which steps were unavailable.

• The screen is a dialog, server form, settings panel, or inventory-style modal
• The user wants the vanilla look (titlebar, OK/Cancel, light/dark content rows)
• You'd otherwise have to author dozens of nested panel/button controls by hand

Contract

• Input: intended vanilla screen role, target profile, content controls, and required variables/bindings.
• Output: selected preset reference, required variables, IR extends usage, and validation artifacts.
• Success: the preset exists in the catalog, emitted references resolve, layout constraints remain explicit, and unknown variables are not invented.

If data/skill-tool-profiles.json exists, read only the mcbe-json-ui-vanilla-presets entry. Use registered catalog or compile commands only after confirming their implementations are present.

Source of truth

• data/presets-catalog.json — every preset reference the kit knows about, with the matching $variable keys and a fits_kind hint.
• data/jsonui-spec.json — full property/anchor/binding catalog (do not invent property names).

Authoring rule

In the IR, set extends: on the element. Layout (anchor, pos, size) is still solved deterministically; the compiler emits:

{ "frame@common_dialogs.main_panel_no_buttons": {
    "size": [560, 320],
    "anchor_from": "center",
    "anchor_to": "center",
    "offset": [-280, -160],
    "variables": { "$title_panel": "common_dialogs.standard_title_label", "...": "..." },
    "bindings": [{ "binding_name": "#title_text" }]
} }

Selection guide

Example

See examples/ir/preset_modal.yaml. Run:

node tools/run.mjs workspace/<name>/ir.yaml

The validator (tools/validate.mjs) checks the emitted nodes against data/jsonui-spec.json and warns on unknown anchors, font sizes, layer overflows, and malformed bindings.