القائمة
Design and validate Orryx UI configuration as explicit bukkit, dragoncore, germplugin, or arcartx variants. Use for backend-specific schemas, placeholders, ordered arrays, skill icons, GUI and client assets, capability gaps, and safe non-lossy adaptation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Orryx Minecraft 技能插件配置创作套件。用于生成或审查 Orryx 游戏技能、Kether 脚本、职业、经验曲线、法力精力成长、中转站、战斗状态机、控制器、选择器和多客户端 UI；也用于创建完整职业套件、检查跨文件引用和安全落盘。触发词包括 Orryx、技能配置、职业配置、经验曲线、Station、中转站、Status、Controller、Kether、选择器、DragonCore、GermPlugin。
Design deterministic Orryx ability YAML for Passive, Direct, DirectAim, Pressing, and PressingAim skills. Use when creating or reviewing ability type fields, Description/Variables/Actions consistency, passive Station companions, charging behavior, targeting compatibility, and cross-file requirements based on real Orryx examples.
Build and review Orryx combat status plus client controller pairs. Use for Condition, States, running transitions, Connection, Check and Invincible intervals, Animation mappings, general attacks, blocks, dodges, attack speed, and controller asset consistency.
Validate Orryx configuration packs without writing or reloading them. Use for basename-derived IDs, cross-file skill/job/experience/status/station references, skill Sort ordering, DirectAim and PressingAim Minecraft 1.12.2 compatibility, and reload-safety review. Produces deterministic diagnostics through the shared orryx_toolkit validator component.
Create and validate Orryx job-kit YAML using basename IDs, display Name/Icon separation, skill and experience references, attributes, mana/spirit/upgrade-point actions, and conservative second-job scaffolding. Use when assembling a job from existing abilities and curves without inventing unsupported ParentJob semantics.
Author and review Orryx Kether Actions for skill, station, state, job, and experience contexts. Use when a request needs context-aware variables, selectors, triggers, event access, deterministic script artifacts, or main-thread safety warnings. Treats the generated Actions Schema as an action vocabulary rather than a complete YAML schema.
| name | orryx-ui-adapter-skill |
| description | Design and validate Orryx UI configuration as explicit bukkit, dragoncore, germplugin, or arcartx variants. Use for backend-specific schemas, placeholders, ordered arrays, skill icons, GUI and client assets, capability gaps, and safe non-lossy adaptation. |
| license | MIT |
| activation | {"command":"/orryx-ui-adapter-skill","intents":["create or review an Orryx UI configuration","adapt a UI to a specific supported backend","validate placeholders, slots, icons, and UI assets"]} |
| metadata | {"author":"NarraFork","version":"1.1.0","created":"2026-07-13T00:00:00.000Z","last_reviewed":"2026-07-13T00:00:00.000Z","review_interval_days":90} |
| provenance | {"repository":"Orryx","sources":["module/ui","src/main/resources/ui","example/Orryx/ui"],"generated_for":"orryx-creation-suite"} |
为 Orryx UI 生成或审查明确的判别联合（discriminated variant）。输入必须选择 bukkit、dragoncore、germplugin 或 arcartx；每个后端有独立 schema、占位符传输、数组顺序和客户端资产契约，不能把它们当作同一份 YAML 的皮肤。
所有请求先规范化为 variant：
bukkit：原版 Inventory UI，核心是 title、Skills/BindSkills/Space/Previous/Next 的 Slots、物品材质、名称与 Lore。dragoncore：依赖 DragonCore GUI 文件、同步占位符、<br> 编码的有序数组、图标路径和客户端资源。germplugin：依赖 Germ GUI part/index 名、动态复制的按钮/纹理、{skill} 图标替换、布局间距和事件回调。arcartx：依赖 ArcartX UI/网络变量结构、icon 字段和对应客户端界面资产。UI.use 的别名可以归一化（DRAGON、GERM、AX），但输出 variant 使用四个规范值之一。
keyTime、KeySort、ActionType、JoinOpenHud 只有在后端实现支持时输出。<br> 列表必须逐索引对齐。skill.getIcon() 的结果是后端资源引用，不保证是 Bukkit Material；每个 variant 都要验证图标命名空间与资产是否存在。适配不是字段替换：
例如 Bukkit slot 数组不能自动推导 Germ 动态 canvas 布局；DragonCore <br> placeholder 不能盲目变成 ArcartX map；Germ part 名也不能假设存在于 DragonCore GUI。
py -3 scripts/run_pipeline.py --input assets/request.example.json --output ui-report.json。输出固定组件 ui，包含规范 variant、后端专属 artifacts、placeholder/array contract、asset dependencies、errors、warnings 和转换损失。缺少 variant、混合后端字段、数组错位、未知 placeholder 或缺失必需资产必须是 error。
详细字段见 references/contract.md，依据见 references/source-evidence.md。