godot-greybox

Build static Godot level blockouts with real scene nodes in .tscn files.

8|3|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-greybox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: godot-greybox
Source: https://github.com/arthur0n/xenodot-forge/tree/main/plugin/skills/godot-greybox
Command: npx skills add https://github.com/arthur0n/xenodot-forge --skill godot-greybox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the common mistake of building level geometry at runtime or leaving a scene as an empty box, so prototyping stays editable, measurable, and immediately visible in the Godot editor.

Core Features & Use Cases

  • Static in-scene blockouts: Creates real StaticBody3D, MeshInstance3D, CollisionShape3D, and Area3D nodes directly inside the saved level scene.
  • Level shape prototyping: Supports fast greyboxing for any level concept, including walls, props, hazards, and navigation setup.
  • Design validation: Enforces at least one elevation change and multiple distinguishable zones to avoid flat, unreadable spaces.
  • Use case: A level designer hands off a brief for a new arena or exploration space, and this Skill turns it into a selectable, editable Godot .tscn blockout.

Quick Start

Ask for a static greybox of the named level directly in levels/<name>.tscn using the provided design brief, with one floor, real editor-visible nodes, at least one elevation change, and two distinct zones.

Frequently Asked Questions about godot-greybox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create static Godot level blockouts directly in saved scene files?

Static Godot level blockouts are built by generating real editor-visible nodes like StaticBody3D and MeshInstance3D directly inside saved .tscn files, ensuring geometry stays editable and measurable for prototyping.

Why does my Godot level prototype lack readable zones and elevation changes?

Godot level prototypes often lack readable zones when designed as flat empty spaces, so enforcing at least one elevation change and multiple distinct zones during scene authoring prevents unreadable arena layouts.

What is the best way to prototype a Godot exploration space without runtime generators?

The best way to prototype a Godot exploration space without runtime generators is authoring static in-scene blockouts, placing real nodes for walls, hazards, and navigation directly into the saved level scene.

Can I use Area3D nodes for hazards when greyboxing a Godot level?

Yes, you can use Area3D nodes for hazards when greyboxing a Godot level, as static scene authoring supports adding real collision and area nodes directly to the blockout for immediate editor visibility.

Does Godot greyboxing require runtime-built geometry or raw Transform3D literals?

No, Godot greyboxing strictly avoids runtime-built geometry or raw Transform3D literals, relying instead on real scene nodes saved directly in the level file to maintain an editable and measurable design space.