unity-scene-contracts

Define and enforce Unity scene structure contracts with required objects and wiring rules.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mufengbufeng/EF --skill unity-scene-contracts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-scene-contracts
Source: https://github.com/mufengbufeng/EF/tree/main/UnityProject/.claude/skills/unity-skills/skills/scene-contracts
Command: npx skills add https://github.com/mufengbufeng/EF --skill unity-scene-contracts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unity scene composition is error-prone without a formal contract; this skill provides a structured way to declare required root objects, components, bootstrap logic, and wiring rules to ensure scenes initialize deterministically.

Core Features & Use Cases

  • Define required root objects
  • Define required components on each root
  • Which references are assigned in Inspector
  • Which objects act as bootstrap/installers
  • Validation rules and early failing checks
  • Guardrails: Avoid hidden runtime lookups; enforce explicit wiring

Quick Start

Define your first contract by listing required root objects and their components, then validate the wiring and bootstrap order.

Frequently Asked Questions about unity-scene-contracts

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

FAQPage Schema
How do I enforce required root objects and components in a Unity scene?

To enforce required root objects in a Unity scene, define a structured contract listing essential objects, components, and dependencies. This ensures deterministic scene initialization by validating reference wiring and bootstrap logic before runtime.

What is a Unity scene contract and when do I need one?

A Unity scene contract is a formal document declaring required root objects, components, and wiring rules. You need one when scene composition is error-prone and requires deterministic bootstrap initialization with explicit reference assignments instead of hidden lookups.

How do I validate bootstrap initialization order and Inspector wiring in Unity?

Validate bootstrap initialization order and Inspector reference wiring by outlining essential objects and dependencies in a contract. The contract specifies validation rules and early failing checks to enforce explicit wiring and prevent hidden runtime lookups.

Can I define runtime spawn rules and reference wiring rules for Unity scene setups?

Yes, you can define runtime spawn rules and reference wiring rules within a Unity scene contract. The structured document outlines essential objects, dependencies, and validation rules to ensure scenes initialize deterministically without hidden lookups.

What's the best way to avoid hidden runtime lookups during Unity scene initialization?

The best way to avoid hidden runtime lookups during Unity scene initialization is to establish a formal scene contract. This enforces explicit wiring by declaring required root objects, bootstrap installers, and Inspector references with early failing checks.