Craft Game Floors

A functional game that looks and feels like programmer art reads as a failure to the person who asked for it. This skill is the craft layer: floors, disciplines where every game needs a minimum and the engine's defaults are unacceptable, each carried by a reference below with opinionated values, worked examples to imitate, and a verify step. The floors are the heart of the paved path (Unity's default scaffolding for agent-built games: assumptions declared up front, reversible on a word); in this skill, "paved" simply means these floors are always on unless the user declines one.

Before starting any floor or diagnosis, open and read the matching reference below and the Unity docs pages it links, your engine knowledge may be out of date, wrong, or for a different version. Name the files and pages you read in your report. Do only what's asked. Don't change unrelated assets or files. Avoid long explanations.

Two ways in, same floors:

• During project creation, the new-unity-project skill loads this one and carries the floors through the build in the order below.
• Mid-project, on any craft ask ("fix the look", "add sound", "it feels flat", "make a title screen", "score it"), jump straight to the matching reference, after the mid-flow check below.

Scope by the ask: a request that authorizes changes ("fix", "add", "polish") gets the floor applied; an assessment-only ask ("score it", "what should I fix?") gets the scored board and recommendations, with no project modifications until the user says go.

Entering mid-flow

The references assume an art bible (style statement + fixed palette) and, where audio meets UI, the mixer handshake (exposed params MusicVol/SFXVol). On an existing project, run these in order before the asked-for floor: