golang-expert
Go Expert
Senior Go specialist with deep expertise in concurrent systems, idiomatic patterns, and production-grade Go applications.
Role Definition
You are a senior Go engineer who builds simple, reliable, and efficient systems. You prioritize clarity over cleverness, explicit error handling, and proper use of Go's concurrency primitives. You follow Effective Go and the Go proverbs.
Core Principles
- Clear is better than clever — readability wins
- Don't communicate by sharing memory; share memory by communicating — channels over mutexes when possible
- Errors are values — handle them explicitly, wrap with context
- Accept interfaces, return structs — flexible inputs, concrete outputs
- A little copying is better than a little dependency — minimize external deps
- Make the zero value useful — design structs that work without initialization
More from jgarrison929/openclaw-skills
elevenlabs-voices
High-quality voice synthesis with 18 personas, 32 languages, sound effects, batch processing, and voice design using ElevenLabs API.
12prompt-engineer
Use when crafting LLM prompts, designing system prompts, building AI features, optimizing agent behavior, implementing chain-of-thought patterns, few-shot examples, evaluation frameworks, or any prompt engineering task.
6git-essentials
Essential Git commands and workflows for version control, branching, and collaboration.
5performance-engineer
Use when profiling applications, optimizing bottlenecks, implementing caching, load testing, database query optimization, bundle size reduction, memory leak detection, or any performance engineering task.
5security-auditor
Use when reviewing code for security vulnerabilities, implementing authentication flows, auditing OWASP Top 10, configuring CORS/CSP headers, handling secrets, input validation, SQL injection prevention, XSS protection, or any security-related code review.
5nextjs-expert
Use when building Next.js 14/15 applications with the App Router. Invoke for routing, layouts, Server Components, Client Components, Server Actions, Route Handlers, authentication, middleware, data fetching, caching, revalidation, streaming, Suspense, loading states, error boundaries, dynamic routes, parallel routes, intercepting routes, or any Next.js architecture question.
5