unity-scene-contracts

Define explicit Unity scene composition contracts covering required objects, bootstrap wiring, and validation rules.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-scene-contracts-ethanjpope
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-scene-contracts
Source: https://github.com/ethanJPope/Our-Main-Hackathon-Game/tree/main/.agents/skills/unity-skills/skills/scene-contracts
Command: npx skills add https://github.com/ethanJPope/Our-Main-Hackathon-Game --skill unity-scene-contracts-ethanjpope

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity scenes often rely on hidden runtime lookups like chains of Find calls, making dependencies implicit and fragile. This Skill makes scene setup explicit by documenting required objects, wiring, and bootstrap order before implementation. ## Core Features & Use Cases - Scene Object Contracts: Define required root objects, their components, and which references are assigned in the Inspector. - Bootstrap Planning: Identify bootstrap/installer objects, runtime-spawned objects, and the correct initialization sequence. - Validation & Risk Documentation: Record assumptions to validate early and surface hidden dependency risks. - Use Case: Before building a new game level, use this Skill to produce a scene contract listing every required manager object, its Inspector wiring, and the bootstrap order, so the team avoids runtime Find chains and missing-reference bugs. ## Quick Start Use the unity-scene-contracts skill to draft a scene contract for my main gameplay scene, including required root objects, Inspector wiring rules, and bootstrap sequence.

Frequently Asked Questions about unity-scene-contracts

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

FAQPage Schema
How do I document required objects in a Unity scene?

Create a scene contract listing every required root object, the components each must have, and which references are assigned in the Inspector. This makes scene dependencies explicit instead of relying on hidden runtime lookups.

How to plan Unity scene bootstrap and initialization order?

Identify which objects act as bootstrap or installer objects, keep them small and focused, and document the sequence in which they wire up other systems. Distinguish these from runtime-spawned objects in the contract.

Should I use GameObject.Find or explicit references in Unity?

Prefer explicit Inspector-assigned references over chains of runtime Find calls. Explicit wiring makes dependencies visible, catches missing references early, and reduces fragile name-based lookups.

What are hidden dependency risks in Unity scenes?

Hidden dependencies arise when objects locate each other at runtime through Find or singletons without documented contracts. Documenting assumptions and validating them early exposes these risks before they cause runtime failures.

When should I write a scene contract versus just building the scene?

Write a contract when scene setup involves multiple required objects, bootstrap ordering, or shared team ownership. For trivial single-object scenes, direct setup is usually sufficient.