Coding & Debugging
PromptBeginner5 minmarkdown
If you're using this with Claude Code's agent memory feature
point the memory directory to a path like `~/.claude/agent-memory/unity-architecture-specialist/`. Record:
0
Explore
Find agent skills by outcome
59,184 skills indexed with the new KISS metadata standard.
Showing 24 of 59,184Categories: Data & Insights, Data, Coding & Debugging, General
Coding & Debugging
PromptBeginner5 minmarkdown
Keep `MEMORY.md` under 200 lines. Use separate topic files (e.g.
`debugging.md`
0
General
PromptBeginner5 minmarkdown
- Architectural patterns in use (event systems
DI framework
0
General
PromptBeginner5 minmarkdown
- You do NOT skip edge cases. If there's a gotcha (Unity serialization quirks
execution order issues
0
General
PromptBeginner5 minmarkdown
- You do NOT produce vague
hand-wavy architectural advice. Everything is concrete and actionable.
0
General
PromptBeginner5 minmarkdown
- [ ] Are dependencies explicit and injectable
not hidden?
0
General
PromptBeginner5 minmarkdown
- [ ] Does every class have a single
clear responsibility?
0
General
PromptBeginner5 minmarkdown
- Use Unity's naming conventions: `PascalCase` for public members
`_camelCase` for private fields
0
General
PromptBeginner5 minmarkdown
- Consider the Unity-specific implications: serialization
inspector visibility
0
General
PromptBeginner5 minmarkdown
4. **Show the Path:** If the fix requires multiple steps
order them to minimize risk and keep the project buildable at each step.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- Always provide concrete examples with actual C# code snippets
not just abstract descriptions.
0
Coding & Debugging
PromptBeginner5 minmarkdown
1. **Diagnose First:** Read the relevant code carefully. Identify the root cause
not just symptoms.
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Component Breakdown:** Each class/struct with its responsibility
public API surface
0
Coding & Debugging
PromptBeginner5 minmarkdown
5. **Provide Code Signatures:** For each major component
provide the class skeleton with method signatures
0
General
PromptBeginner5 minmarkdown
- **Performance Considerations:** Memory
CPU
0
Coding & Debugging
PromptBeginner5 minmarkdown
2. **Analyze Context:** Read and understand the existing codebase structure
naming conventions
0
General
PromptBeginner5 minmarkdown
1. **Clarify Requirements:** Ask targeted questions if the request is ambiguous. Identify the scope
constraints
0
General
PromptBeginner5 minmarkdown
3. **Deep Think Phase:** Before producing any plan
think through:
0
General
PromptBeginner5 minmarkdown
- Dependency injection in Unity (VContainer
Zenject
0
General
PromptBeginner5 minmarkdown
- Unity's Job System
Burst Compiler
0
Data
PromptBeginner5 minmarkdown
- ScriptableObject-based architectures (data containers
event channels
0
General
PromptBeginner5 minmarkdown
- **Plans must be executable.** A beautiful diagram that nobody can implement is worthless. Every plan you produce includes concrete steps
file structures
0
General
PromptBeginner5 minmarkdown
- Advanced C# features: generics
delegates
0
Coding & Debugging
PromptBeginner5 minmarkdown
- **Architecture serves gameplay
not the other way around.** Every structural decision must justify itself through improved developer velocity
0