screen-reference

Generates and validates full-screen visual reference images for Godot scene direction.

531|45|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill screen-reference
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: screen-reference
Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/assets/screen-reference
Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill screen-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game teams need a stable full-screen visual anchor to guide scene direction and evaluate visual output, but ad-hoc image generation produces inconsistent, unvalidated results that cannot be audited or reused in a production pipeline.

Core Features & Use Cases

  • Provider-driven image generation: Produces non-pixel-art full-screen references through configured providers (native, codex, gemini, openai) with role-preserving reference image attachments.
  • Deterministic production pipeline: Records prompt, raw source, and provider/finalize reports at fixed paths, then resizes and center-crops the source to the exact target canvas with aspect validation.
  • Use Case: A designer needs a 1920x1080 visual reference for a game's main battle screen. The Skill builds a prompt naming the game, camera viewpoint, HUD safe regions, and style, generates the image via the selected provider, finalizes it to the exact canvas, and validates the PNG output.

Quick Start

Ask the agent to generate a 1920x1080 screen reference for your game's main menu scene using the screen-reference asset type with your chosen image provider.

Frequently Asked Questions about screen-reference

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

FAQPage Schema
How do I generate a full-screen visual reference for a Godot game scene?

Invoke the Skill with an asset request where asset_type is screen-reference and spec declares the target size and aspect ratio. It builds a prompt covering camera, layout, and style, calls the configured image provider, and finalizes the result to the exact canvas.

Which image providers does screen-reference support?

It supports native, codex, gemini, and openai providers as binding selections. Each provider follows its documented generation path, and the Skill never silently switches providers; an unsupported or failing provider causes a STOP.

Does the screen reference become a runtime Godot asset?

No. The output is reference-only with no godot_artifact and no runtime handoff. It is never compiled to Texture2D or AtlasTexture and is registered as source_ready by the asset manager.

Can I supply reference images to guide the generation?

Yes. The optional references field accepts role-tagged image paths that are resolved, hashed, and attached to the provider request. If an input is unreadable or the provider cannot attach it, the Skill stops before producing output.

Why does screen-reference generation stop before writing output?

It stops when a reference input is unreadable, the provider fails, attachment evidence is missing, or aspect/finalization validation fails. These gates ensure only auditable, correctly sized references reach the catalog.