Explore → Plan → Implement. A thinking partner for exploring ideas, investigating problems, and clarifying requirements, that transitions into a structured roadmap specification (tasks in What/How/Where/Acceptance criteria format) for user approval, then implements the approved plan. Use when the user wants to think through something before a change, when requirements are unclear, or when discussing architecture and design decisions.
Comprehensive code review methodology for evaluating code changes. Identifies bugs, logic errors, security issues, structural problems, performance concerns, and unintended behavior changes. Use when reviewing uncommitted changes, specific commits, branch comparisons, or pull requests.
Removes signs of machine generation from Russian-language AI text, preserving its original register and communicative purpose. Does not turn everything into conversational style — scientific text remains scientific, business text remains business, and conversational remains conversational. Use when you need to remove AI markers from text for publication, bypass AI detectors, or adapt machine output to natural Russian speech in the required register.
Analyzes the project codebase, documentation, and memory to identify the single highest-priority task to work on right now. Triggers on phrases like "Hey, what are we going to do today, Brain?", "What should I work on?", "What's next?", or any request for task prioritization.
Write secure Go applications through everyday development practices — no AppSec expertise required. Covers the 12 OWASP Top 10 categories (2021 & 2025) with idiomatic Go patterns, standard library defaults, recommended libraries, and a security-focused linter setup. Use when writing or reviewing Go backend code, designing Go APIs, configuring production deployments, setting up CI/CD security checks, or hardening existing Go services.
Guides the agent to write well-organized Go code and projects. Use when writing or reviewing Go code involving variable scoping, nested control flow, init functions, getters/setters, interfaces, generics, type embedding, functional options, package structure, utility packages, package naming, code documentation, or linter configuration. Covers the 16 most common code and project organization mistakes in Go.
Guides the agent to avoid foundational concurrency mistakes in Go: confusing concurrency with parallelism, assuming concurrency is always faster, misusing channels vs mutexes, ignoring data races and race conditions, mis-sizing worker pools for CPU- vs I/O-bound work, and misunderstanding Go contexts. Use when writing, reviewing, or refactoring any concurrent Go code, goroutines, channels, mutexes, worker pools, or context usage.
Enforces practical Go concurrency rules from "100 Go Mistakes" (Ch.9, #61-#74) when writing or reviewing concurrent Go code. Use when code involves goroutines, channels, select statements, sync primitives (Mutex, WaitGroup, Cond, errgroup), or when passing contexts across goroutine boundaries. Catches context propagation bugs, goroutine leaks, loop variable captures, channel misuse, data races with append/slices/maps, sync type copying, and deadlocks from string formatting.