Loading...
Loading...
Found 21 Skills
Use when Go interfaces including interface design, duck typing, and composition patterns. Use when designing Go APIs and abstractions.
Optimize decision-making speed by managing choice quantity. Use when designing navigation, menus, feature sets, onboarding flows, or any interface where users must choose between options.
UX laws and cognitive psychology principles for designing better interfaces
Apply the Doherty Threshold — keep system response times under 400ms to maintain user flow and perceived performance.
Apply Miller's Law — chunk information into groups of ~4 to work within working memory limits.
Apply Hick's Law to reduce decision time by limiting the number of simultaneous choices presented to users.
WHEN: User is writing Go code, asking about Go patterns, reviewing Go code, asking "what's the best way to...", "how should I structure...", "is this idiomatic?", or any question about error handling, concurrency, interfaces, packages, testing patterns, or code organization in Go. Also activate when user is debugging Go code, refactoring Go, or working in a Go project (go.mod present) and asks general coding questions. Trigger this skill liberally for ANY Go-related development work. WHEN NOT: Non-Go languages, questions entirely unrelated to programming
SOLID design principles for .NET. Use when designing classes, interfaces, and object relationships. Ensures maintainable, testable, and extensible code.
Use interfaces and dependency injection to decouple code; bind implementations in the container