Verified:GitHub

unity-scene-contracts

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

2|Updated May 18, 2026

Search Tags:#game development #unity #documentation #bootstrap #dependency wiring #scene setup #inspector references

One-click install

npx skills add https://github.com/pcone-mm/NewFPG --skill unity-scene-contracts-pcone-mm

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: unity-scene-contracts
Source: https://github.com/pcone-mm/NewFPG/tree/main/.agents/skills/unity-skills/skills/scene-contracts
Command: npx skills add https://github.com/pcone-mm/NewFPG --skill unity-scene-contracts-pcone-mm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unity scenes often rely on hidden runtime lookups and implicit assumptions, making setup fragile and hard to document. This Skill makes scene composition explicit by defining what objects, components, and wiring a scene must contain. ## Core Features & Use Cases - Scene Object Contracts: Specify 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 such as chains of runtime Find calls. - Use Case: When a teammate asks "what does this scene need" or "how are references wired", produce a contract document covering required objects, Inspector wiring rules, and bootstrap order. ## Quick Start Ask the assistant to define the scene contract for your Unity scene, listing required root objects, components, 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

When should I use scene contracts versus runtime dependency injection?▼

Use scene contracts when setup needs to be explicit and reviewable, especially for team documentation. Runtime injection suits dynamic content, but contracts help validate assumptions early and expose hidden dependency risks.