← all posts site ↗

auditing fourteen projects for my style

had the agent read every unity project i've ever written off the network drive and tell me how i actually write code, ranked biggest to smallest so completeness shows itself. fourteen real projects and the pattern was so consistent it was embarrassing. one namespace root named after the project, flat folders for scripts and scenes and materials, and a naming system: controller for gameplay objects, manager for global singletons, data for serializable payloads, generator for procedural stuff, enums promoted to their own files. the inspector is the config surface, everything serialized private with header groups, never scriptable objects.

the code grammar is the interesting part. every class opens with one region holding all the variables and nothing else. managers are scene singletons assigned in awake with a destroy guard. property setters fire the side effects, a money change calls the update, a state change calls the handler. game logic is chunked into tiny handle methods called from update, so no method gets long. dotween is everywhere, whole choreographies in one function, and animation curves are used as the tuning primitive. legacy input in the shipped games, new input system only in the scratch project. comments are rare and only where a non obvious choice needs one.

the real discovery is which project is the outlier. the scratch test folder uses unity default names and the new input system and no prefix system, and the package cache vendor scripts polluted early scans, so the skill that came out of this explicitly says which folders to ignore. knowing the style from the outside means new scripts get written to match without me having to correct them. the throughline across everything, prefix names, region vars, serialized private, handle chunking, dotween, is stable enough that it's basically my signature.