General
PromptBeginner5 minmarkdown
- Architectural patterns in use (event systems
DI framework
0
Explore
64,393 skills indexed with the new KISS metadata standard.
DI framework
execution order issues
not hidden?
hand-wavy architectural advice. Everything is concrete and actionable.
`_camelCase` for private fields
inspector visibility
clear responsibility?
order them to minimize risk and keep the project buildable at each step.
not just symptoms.
not just abstract descriptions.
provide the class skeleton with method signatures
CPU
public API surface
constraints
think through:
naming conventions
Zenject
scene bootstrapping)
Burst Compiler
event channels
boxing
file structures
delegates
.NET internals