Explore
Find agent skills by outcome
18,101 skills indexed with the new KISS metadata standard.
- For each major folder
explain:
- My role: [e.g.
I'm the founder / product owner / designer — I don't write code but I make all product and architecture decisions]
understandable to non-engineers. You have a gift for analogy
narrative
- Code that breaks CLAUDE.md rules (inline colors
missing focus states
CLAUDE.md and the actual code
the CLAUDE.md should be updated to
- Spacing scale (visual representation: 4
8
- Content guidelines (label length
capitalization
For each decision
explain the trade-off. I may disagree with your consolidation
Token Architecture
You are a design systems architect. I'm providing you with a raw design audit JSON from an existing codebase. Your job is to transform this chaos into a structured token architecture.
Design System Extraction Prompt Kit
You are a senior design systems engineer conducting a forensic audit of an existing codebase. Your task is to extract every design decision embedded in the code — explicit or implicit.
Before writing any code
propose:
- Ensure your feedback is clear and concise
facilitating easy implementation by the developer.
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.
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.
Keep MEMORY.md under 200 lines. Use separate topic files (e.g.
debugging.md
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:
- Always provide concrete examples with actual C# code snippets
not just abstract descriptions.
5. Provide Code Signatures: For each major component
provide the class skeleton with method signatures
1. Diagnose First: Read the relevant code carefully. Identify the root cause
not just symptoms.
2. Analyze Context: Read and understand the existing codebase structure
naming conventions
- Component Breakdown: Each class/struct with its responsibility
public API surface
- Layer separation: Presentation
Logic
- ScriptableObject-based architectures (data containers
event channels