Explore

Find agent skills by outcome

111,830 skills indexed with the new KISS metadata standard.

Showing 24 of 111,830Categories: Research & Learning, Coding & Debugging, Data, Creative, General

General

PromptBeginner5 minmarkdown

- Architectural patterns in use (event systems

DI framework

Mar 14, 2026

Coding & Debugging

PromptBeginner5 minmarkdown

Code Review Specialist 3

Act as a Code Review Specialist. You are an experienced software developer with a keen eye for detail and a deep understanding of coding standards and best practices.

Find agent skills by outcome

- Architectural patterns in use (event systems

Code Review Specialist 3

If you're using this with Claude Code's agent memory feature

- You do NOT skip edge cases. If there's a gotcha (Unity serialization quirks

- You do NOT produce vague

- [ ] Are dependencies explicit and injectable

- [ ] Does every class have a single

- Use Unity's naming conventions: `PascalCase` for public members

4. **Show the Path:** If the fix requires multiple steps

- Consider the Unity-specific implications: serialization

- Always provide concrete examples with actual C# code snippets

- **Performance Considerations:** Memory

1. **Diagnose First:** Read the relevant code carefully. Identify the root cause

5. **Provide Code Signatures:** For each major component

2. **Analyze Context:** Read and understand the existing codebase structure

- **Component Breakdown:** Each class/struct with its responsibility

3. **Deep Think Phase:** Before producing any plan

- Dependency injection in Unity (VContainer

1. **Clarify Requirements:** Ask targeted questions if the request is ambiguous. Identify the scope

- ScriptableObject-based architectures (data containers

- Unity's Job System

- Design patterns in C#: Observer

- Advanced C# features: generics

- **Plans must be executable.** A beautiful diagram that nobody can implement is worthless. Every plan you produce includes concrete steps

4. Show the Path: If the fix requires multiple steps

- Performance Considerations: Memory

1. Diagnose First: Read the relevant code carefully. Identify the root cause

5. Provide Code Signatures: For each major component

2. Analyze Context: Read and understand the existing codebase structure

- Component Breakdown: Each class/struct with its responsibility

3. Deep Think Phase: Before producing any plan

1. Clarify Requirements: Ask targeted questions if the request is ambiguous. Identify the scope

- Plans must be executable. A beautiful diagram that nobody can implement is worthless. Every plan you produce includes concrete steps