unity-scene-contracts

Defines Unity scene composition contracts covering required objects, bootstrap logic, and reference wiring.

Updated Jun 21, 2026
One-click install
npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-scene-contracts-du-qwq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unity-scene-contracts
Source: https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications/tree/main/.agents/skills/unity-skills/skills/scene-contracts
Command: npx skills add https://github.com/du-qwq/Shader-Writing-Architecture-and-Specifications --skill unity-scene-contracts-du-qwq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity scenes often rely on hidden runtime lookups and implicit assumptions, making scene setup fragile and hard to document. This Skill makes scene composition explicit by defining contracts for required objects, components, and wiring. ## Core Features & Use Cases - Scene Object Contracts: Specify required root objects, their components, and which references are assigned in the Inspector. - Bootstrap Planning: Define bootstrap/installer objects, runtime-spawned objects, and the startup sequence. - Validation & Risk Documentation: Record wiring rules, validation checks, and hidden dependency risks such as chains of runtime Find calls. - Use Case: When a teammate asks what a scene must contain or how references should be connected, produce a documented contract covering objects, bootstrap order, and Inspector wiring instead of relying on tribal knowledge. ## Quick Start Ask the assistant to define the scene contract for your Unity scene, listing required objects, bootstrap sequence, and Inspector wiring rules.

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 what a Unity scene must contain?

Define a scene contract listing required root objects, the components each root needs, and which references are assigned in the Inspector. Also record which objects are bootstrap installers versus runtime-spawned so setup assumptions are explicit.

How to plan bootstrap logic in a Unity scene?

Identify which objects act as bootstrap or installer objects and keep them small and focused. Document the bootstrap sequence and which assumptions should be validated early during scene load.

Why should I avoid runtime Find calls in Unity scenes?

Chains of runtime Find calls create hidden dependencies that break silently when objects are renamed or reordered. Explicit Inspector wiring makes dependencies visible, validated at edit time, and easier to document.

Does this skill modify Unity scenes or scripts automatically?

No, it is documentation-only guidance. It produces scene object contracts, bootstrap sequences, wiring rules, and validation rules as written documentation, and loads freely under any operating mode.

When should I use scene contracts versus runtime dependency injection?

Use scene contracts when setup needs to be explicit and reviewable rather than discovered at runtime. Runtime injection suits dynamic content, but contracts are better for documenting fixed scene structure and wiring assumptions.