Go Error Management
>
Secure Go
>
Go Control Structures
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.
Research Experiment
>-
Vibespec Init
>-
Go Concurrency Practice
>
Research Status
>-
Go Functions Methods
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.
Humanize Ru
>
Research Init
>-
Prompts Review
>-
Triz Solver
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.
Security Policy Generator
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.
Go Standard Library
>
Scamper
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.
Go Data Types
>
Vibe Research
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.
Research Prior Art
>-
Vibespec Update
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.
Go Concurrency Foundations
>
Deeper Research
>
Research Decision
>-
Vibespec Check
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.
Explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change, when requirements are unclear, or when discussing architecture and design decisions.
Research Hypothesis
>-
Vibespec Create
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.
Go Testing Mistakes
>
Go Strings
>
Go Code Organization
>
Vibespec Consult
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.
Vibe Brain
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.
Research Synthesis
>-
Go Optimizations
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…