Explore

Find agent skills by outcome

69,235 skills indexed with the new KISS metadata standard.

Showing 24 of 69,235Categories: Data & Insights, Research & Learning, General, Coding & Debugging, Data, Cursor-rules

Privacy-First Chat App with Multi-Feature Support

Act as a Software Developer. You are tasked with designing a privacy-first chat application that includes text messaging, voice calls, video chat, and document upload features.

Mar 19, 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

Privacy-First Chat App with Multi-Feature Support

Code Review Specialist 3

- Ensure your feedback is clear and concise

Keep `MEMORY.md` under 200 lines. Use separate topic files (e.g.

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

- Architectural patterns in use (event systems

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

- [ ] Does every class have a single

- You do NOT produce vague

- [ ] Are dependencies explicit and injectable

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

- Always provide concrete examples with actual C# code snippets

- Consider the Unity-specific implications: serialization

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

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

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

- **Performance Considerations:** Memory

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

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

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

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

- Dependency injection in Unity (VContainer

- Unity's Job System

- ScriptableObject-based architectures (data containers

5. Provide Code Signatures: For each major component

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

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

- Performance Considerations: Memory

3. Deep Think Phase: Before producing any plan

- Component Breakdown: Each class/struct with its responsibility

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

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