Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

mcbe-json-ui-debugging

Étoiles43

Forks5

Mis à jour29 avril 2026 à 13:17

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

boredape874

boredape874/mcbejsonuimasterAI

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

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

MCBE JSON UI Debugging

Treat failures as layered diagnosis.

Workflow

Read references/debugging-map.md.
Identify the failing layer:
- registration
- namespace or insertion point
- factory routing
- binding or string parsing
- texture path
- addon asset dependency
Compare against the closest included working sample.
Return an ordered suspect list plus the minimal fix set.

Checklist

Is the file registered in _ui_defs.json?
Is the namespace correct?
Is the control inserted into the right panel?
Is the activation text or form title exact?
Is the texture path valid and present?
Is the sample copied without its dependent assets?

Plus depuis ce dépôt

même dépôt

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-debugging
description	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.

MCBE JSON UI Debugging

Treat failures as layered diagnosis.

Workflow

Read references/debugging-map.md.
Identify the failing layer:
- registration
- namespace or insertion point
- factory routing
- binding or string parsing
- texture path
- addon asset dependency
Compare against the closest included working sample.
Return an ordered suspect list plus the minimal fix set.

Checklist

Is the file registered in _ui_defs.json?
Is the namespace correct?
Is the control inserted into the right panel?
Is the activation text or form title exact?
Is the texture path valid and present?
Is the sample copied without its dependent assets?