skills

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.

Enforces correct usage of Go control structures including range loops, break statements, and defer in loops. Use when writing or reviewing Go code that iterates over slices, arrays, maps, or channels with range, uses break inside switch/select within loops, or places defer calls inside loops.

Guides the agent to avoid common Go mistakes with basic data types, slices, and maps. Use when writing or reviewing Go code that involves integer literals, numeric overflow, floating-point arithmetic, slice initialization/slicing/appending/copying, map initialization, or value comparison. Covers mistakes #17-#29 from "100 Go Mistakes and How to Avoid Them."

Guides the agent to avoid common Go error management mistakes when writing or reviewing Go code. Covers panic usage, error wrapping vs transforming, checking error types and values correctly with errors.As/errors.Is, handling errors exactly once, explicitly ignoring errors, and handling defer errors. Use when writing, reviewing, or refactoring Go error handling code, or when working with sentinel errors, custom error types, wrapped errors, or defer cleanup.

Enforces best practices for Go functions and methods including receiver type selection, named result parameters, nil receiver pitfalls, io.Reader over filenames, and defer argument evaluation. Use when writing, reviewing, or refactoring Go functions, methods, receivers, or defer statements.

Guides the agent to write and review performance-sensitive Go code by applying CPU cache awareness, false sharing prevention, instruction-level parallelism, data alignment, escape analysis, allocation reduction, inlining, profiling, GC tuning, and Docker/Kubernetes GOMAXPROCS configuration. Use when writing hot-path Go code, reviewing performance-critical sections, reducing allocations, profiling applications, tuning GC behavior, or deploying Go services in containers.

Guides the agent to avoid common Go standard library mistakes when writing or reviewing Go code. Covers time.Duration misuse, time.After memory leaks, JSON handling pitfalls (type embedding, monotonic clock, map of any), SQL mistakes (sql.Open, connection pooling, prepared statements, null values, row iteration errors), closing transient resources (HTTP body, sql.Rows, os.File), missing return after HTTP error replies, and using default HTTP client/server without timeouts. Use when writing, reviewing, or refactoring code that uses the time, encoding/json, database/sql, net/http, or os packages.

Guides the agent to write correct and efficient Go string code. Use when writing or reviewing Go code that iterates over strings, concatenates strings, trims strings, converts between string and []byte, or extracts substrings. Covers rune semantics, string iteration pitfalls, trim vs. suffix/prefix functions, Builder-based concatenation, avoiding useless string/byte conversions, and preventing memory leaks from substrings.

Guides the agent to avoid common Go testing mistakes when writing or reviewing test code. Covers test categorization (build tags, env vars, short mode), race detection, test execution modes (parallel, shuffle), table-driven tests, avoiding sleeps in tests, handling the time API deterministically, using httptest/iotest utility packages, writing accurate benchmarks, and leveraging Go testing features (coverage, external test packages, utility functions, setup/teardown). Use when writing, reviewing, or refactoring Go tests, benchmarks, or test helpers, or when setting up CI test pipelines for Go projects.

Detect discrepancies between project specifications and actual code. Use when you suspect specs have drifted from implementation, after a major refactoring, during onboarding to verify spec accuracy, or on explicit user request. For each discrepancy found, interactively asks the user whether to trust the code, trust the spec, trust neither, or ignore.

Proactively consult project specifications before making structural changes. Use BEFORE modifying layer boundaries, adding/removing interfaces, changing architectural patterns, adding new components to existing domains, or any change that could violate documented invariants. This skill navigates the spec system to load relevant context.

Create a new specification document following the project's spec system templates and conventions. Use when adding a new domain, component, contract, architecture doc, or Architecture Decision Record (ADR). Ensures correct format, naming, placement, cross-references, and INDEX.md update.

Initialize a specification system for a project from scratch. Analyzes the codebase to identify architectural layers, domains, boundaries, and key decisions, then generates the initial set of specs (META.md, WORKFLOW.md, INDEX.md, domain specs, contracts, architecture docs, ADR template). Use when bootstrapping specs for a new project, setting up documentation governance, or creating a spec system for an existing codebase that has none.

Update existing specification documents after code changes that alter documented behavior, interfaces, or invariants. Use after implementation when you have changed behavior covered by a spec, added/removed/renamed interfaces in a contract, modified architectural boundaries, or changed configuration. Ensures format preservation, cross-reference integrity, and INDEX.md currency.

Review all prompts in a codebase for optimality, balancing effectiveness and token efficiency. Covers explicit prompt files, string-literal prompts, and dynamically constructed prompts in code. Use when the user asks to review, audit, or optimize prompts, system messages, LLM instructions, or agent prompts.

Analyze a project repository and generate a comprehensive SECURITY.md with threat model, security architecture, and secure coding guidelines. Use when the user asks to create a security policy, generate a threat model, fill in a SECURITY.md template, or assess project security posture.

Conduct thorough, multi-source research using Tree of Thoughts methodology. Produces cited, multi-perspective syntheses with explicit confidence ratings, evidentiary hierarchy, and transparent documentation of pruned branches. Use when the user asks for research, analysis, investigation, deep dive, literature review, or any complex topic requiring structured reasoning.

Analyze hypothesis results and the current state of the hypothesis graph to recommend continue, pivot, kill, or fork decisions for an research iteration. Considers timebox constraints, budget, research question alignment, and graph topology. Use after an experiment completes, when the researcher needs help deciding next steps, or when reviewing the overall research direction.

Guide experiment design, execution tracking, and result recording for an research hypothesis. Helps set up reproducible environments, plan minimal experiments, track progress against the timebox, and formally record outcomes. Use when starting an experiment for a hypothesis, setting up a test environment, tracking experiment progress, or documenting experiment results.

Create, update, and manage hypothesis cards within an research project. Maintains the hypothesis graph (Mermaid diagram) and the catalog table. Handles parent-child relationships, status transitions, and result recording. Use when formulating a new hypothesis, recording experiment results, updating hypothesis status, or managing the hypothesis graph.

Initialize a new research project following the Iterative Engineering Research Methodology. Creates the file catalog structure (brief, hypothesis graph, prior art page) and populates the research brief through structured dialogue with the researcher. Use when starting a new research, setting up a new investigation, or creating a sub-research.

Search, evaluate, and catalog prior art for an research project. Finds and annotates academic papers, CVEs, tools, conference talks, and source code repositories. Maintains the prior-art.md catalog with relevance assessments. Use when investigating existing work, reviewing literature, searching for CVEs, or when the researcher mentions prior art, references, or related work.

Generate a comprehensive status overview of an research project. Reads the brief, hypothesis graph, and hypothesis cards to produce a summary of progress, active fronts, time and budget consumption, and key findings. Use when the researcher wants a progress check, when preparing for a quarterly review, or when someone new needs to understand the current state of a research project.

Execute the synthesis phase of an research project. Analyzes the hypothesis graph, determines report verbosity (simple vs. complex path), generates the final report, creates a prototype inventory, and finalizes the implementation plan in the brief. Use when concluding a research project, writing the final report, or when the research question has been answered or the budget is exhausted.

Transform existing ideas into improved variants using the SCAMPER method (Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse). Use when the user has a baseline idea to improve, a process to redesign, or needs systematic ideation for differentiation.

Solve inventive engineering, product, process, or system-design problems using TRIZ methodology. Use when facing design trade-offs, technical contradictions, or when you need breakthrough concepts rather than incremental optimization.

Iterative research copilot for exploratory "vibe research." Progressively sharpens a broad topic into a sharp, high-value line of inquiry through multiple research loops. Use when the user wants to explore a topic, do open-ended research, brainstorm research directions, or says "vibe research."