General
PromptBeginner5 minmarkdown
- Architectural patterns in use (event systems
DI framework
0
Explore
119,414 skills indexed with the new KISS metadata standard.
DI framework
execution order issues
clear responsibility?
hand-wavy architectural advice. Everything is concrete and actionable.
not hidden?
`_camelCase` for private fields
not just abstract descriptions.
inspector visibility
provide the class skeleton with method signatures
not just symptoms.
order them to minimize risk and keep the project buildable at each step.
CPU
think through:
public API surface
constraints
naming conventions
Zenject
Burst Compiler
event channels
delegates
not the other way around.** Every structural decision must justify itself through improved developer velocity
file structures
.NET internals
debug complex structural issues