Skip to content

Minecraft-Inspired Inventory Interface

Build an original block-survival inventory with dense drag-and-drop state, keyboard interaction, and responsive scaling.

Open exact prompt

Overview

Test interaction density and edge-case handling without copying protected game assets.

Capabilities tested

  • drag and drop
  • dense state
  • keyboard interaction
  • precision
  • tooltips

Required outcome

A responsive inventory supporting stack manipulation, crafting, equipment, and keyboard use.

Requirements

functional

  • Inventory grid and hotbar
  • Drag-and-drop item movement
  • Item stacks and stack splitting
  • Equipment slots and crafting
  • Tooltips

ux

  • Original item icons
  • Keyboard interaction
  • Responsive scaling

technical

  • State remains consistent across moves
  • No copied protected assets
  • Production build must succeed

Constraints

Allowed

  • Original pixel-style assets
  • Pointer and keyboard controls
  • Local application state

Forbidden

  • Copied Minecraft assets
  • Inert drag-and-drop visuals
  • Lost or duplicated item quantities

Acceptance criteria

  • Stacks preserve quantities through moves and splits
  • Crafting and equipment update inventory state
  • Keyboard alternatives are available
  • The interface scales for a narrow viewport

Evidence required

  • Production build output
  • Drag-and-drop recording
  • Keyboard-flow evidence
  • Known-bug list

Exact prompt

prompts/challenges/minecraft-inventory-ui.md
# BuildArena Challenge

Role: Senior frontend product engineer.

Project: Minecraft-Inspired Inventory Interface v1.0.0

Objective: Build an original block-survival inventory system with dense, consistent state and no protected copied assets.

Required outcome: Inventory grid, hotbar, drag and drop, item stacks, stack splitting, tooltips, equipment slots, crafting interface, keyboard interaction, original icons, and responsive scaling.

Build order: Inspect the environment; implement stack state; prove movement and split behavior; add equipment and crafting; add keyboard behavior and responsive scaling; run production validation.

Verification: Run package scripts and verify item counts, crafting, keyboard interaction, mobile layout, and console output.

Evidence to return: Commands, test results, interaction recording, known bugs, missing requirements, human intervention, final commit, and deployment URL only when authorized.