Use when: "Python", "Go", "Golang", "Rust", "Java", "TypeScript", "shell script", "bash", "async/await", "goroutines", "ownership", "virtual threads", "type system", "decorators", "generators", "channels", "interfaces", "Spring Boot", "POSIX".
View on GitHubboshu2/agentops
domain-kit
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/boshu2/agentops/blob/main/plugins/domain-kit/skills/languages/SKILL.md -a claude-code --skill languagesInstallation paths:
.claude/skills/languages/# Languages Skill Production patterns for Python, Go, Rust, Java, TypeScript, and Shell scripting. ## Quick Reference | Language | Key Patterns | When to Use | |----------|--------------|-------------| | **Python** | decorators, generators, async/await, pytest | Data processing, APIs, scripting | | **Go** | goroutines, channels, interfaces | Concurrent systems, CLI tools | | **Rust** | ownership, lifetimes, async tokio | Systems programming, performance | | **Java** | virtual threads, Spring Boot 3.x | Enterprise, microservices | | **TypeScript** | advanced types, generics, strict mode | Frontend, Node.js backends | | **Shell** | set -euo pipefail, POSIX compliance | Automation, CI/CD scripts | --- ## Python ### Focus Areas - Advanced features: decorators, metaclasses, descriptors - Async/await and concurrent programming - Performance optimization and profiling - Design patterns and SOLID principles - Testing with pytest, mocking, fixtures - Type hints and static analysis (mypy, ruff) ### Approach 1. Pythonic code - follow PEP 8 and Python idioms 2. Prefer composition over inheritance 3. Use generators for memory efficiency 4. Comprehensive error handling with custom exceptions 5. Test coverage above 90% with edge cases ### Output - Clean Python code with type hints - Unit tests with pytest and fixtures - Performance benchmarks for critical paths - Documentation with docstrings and examples --- ## Go ### Focus Areas - Concurrency patterns (goroutines, channels, sync) - Interface design and composition - Error handling patterns (no exceptions) - Performance optimization and profiling - Testing with table-driven tests - Module management and versioning ### Approach 1. Keep it simple - Go's strength is simplicity 2. Use interfaces for abstraction 3. Handle errors explicitly 4. Prefer channels over shared memory 5. Write table-driven tests ### Output - Idiomatic Go code following effective Go - Comprehensive tests with benchmarks - Clear error handling patt