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