Designs software architecture and selects appropriate patterns for projects. Use when designing systems, choosing architecture patterns, structuring projects, making technical decisions, or when asked about microservices, monoliths, or architectural approaches.
Implements error handling patterns, structured logging, retry strategies, circuit breakers, and graceful degradation. Use when designing error handling, setting up logging, implementing retries, adding error tracking, or when asked about error boundaries, log aggregation, alerting, or resilience patterns.
Component architecture: Terraform root modules, abstract components, component inheritance, versioning, mixins, catalog patterns
Design patterns: stack organization, component catalogs, inheritance, configuration composition, version management, layered configuration
Redis patterns including caching strategies, pub/sub, streams for event processing, Lua scripts, and data structures
Django architecture patterns including DRF, ORM optimization, signals, middleware, and project structure
Idiomatic Go patterns for error handling, interfaces, concurrency, testing, and module management
Microservices design patterns including service mesh, event-driven architecture, saga pattern, and API gateway
Rust systems programming patterns including ownership, traits, async runtime, error handling, and unsafe guidelines
Spring Boot patterns including JPA repositories, REST controllers, layered services, and configuration
Real-time communication patterns with WebSocket, Socket.io, Server-Sent Events, and scaling strategies
Implement StreamHub real-time indicators with O(1) performance. Use for ChainHub or QuoteProvider implementations. Covers provider selection, RollbackState patterns, performance anti-patterns, and comprehensive testing with StreamHubTestBase.
Implement BufferList incremental indicators with efficient state management. Use for IIncrementFromChain or IIncrementFromQuote implementations. Covers interface selection, constructor patterns, and BufferListTestBase testing requirements.
Built-in MCP (Model Context Protocol) client that connects to external MCP servers, discovers their tools, and registers them as native Gauss Agent tools. Supports stdio and HTTP transports with automatic reconnection, security filtering, and zero-config tool injection.
This skill defines the only right architecture for android projects. Activate when doing big tasks (related to several files and their interconnections) in this project
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals.
Idiomatic Golang design patterns — functional options, constructors, error flow and cascading, resource management and lifecycle, graceful shutdown, resilience, architecture, dependency injection, data handling, and streaming. Apply when designing Go APIs, structuring applications, choosing between patterns, making design decisions, architectural choices, or production hardening.
Golang struct and interface design patterns — composition, embedding, type assertions, type switches, interface segregation, dependency injection via interfaces, struct field tags, and pointer vs value receivers. Use this skill when designing Go types, defining or implementing interfaces, embedding structs or interfaces, writing type assertions or type switches, adding struct field tags for JSON/YAML/DB serialization, or choosing between pointer and value receivers. Also use when the user asks about "accept interfaces, return structs", compile-time interface checks, or composing small interfaces into larger ones.
Docker 容器逃逸技术。当在 Docker 容器内部需要逃逸到宿主机、发现 docker.sock 挂载、容器以特权模式运行、procfs 被挂载、Docker API 端口暴露、或需要利用容器配置错误时使用。覆盖特权容器逃逸、socket 逃逸、procfs 逃逸、Remote API 利用、用户组提权、挂载逃逸、内核漏洞、运行时 CVE、capabilities 滥用。发现容器环境就应使用此技能
Answer weather queries with a fixed demo response.
