omega

Use whenever the user wants to run, plan, kick off, iterate on, or close out a Victoria training version (e.g. "let's start V200", "next training run", "kick off the next iteration", "what should we try next for Victoria", "ship V###", "log this training run"). Codifies the continual-improvement loop — read the latest entry in omega/nodes/victoria/training_log/, propose the next version's hypothesis, run the gates, write the new V###.md entry, update the high-water table, commit, and push.

Structured research pipeline for Omega — takes an idea or hypothesis, searches for evidence, compares to existing Omega capabilities, and delivers a verdict with implementation recommendations. Use when asked to /research a topic, evaluate a new signal source, assess an external tool/library, or investigate trading strategies.

IterDRAG iterative retrieval-augmented generation pattern — search, summarize, reflect loop for deep research tasks

Go coding standards, error handling, concurrency, and Connect-RPC conventions for the Omega project

Buf conventions, proto3 best practices, schema evolution rules, and Connect-ES v2 frontend patterns for Omega

Go table-driven tests, Python pytest patterns, React Testing Library, property-based testing, and integration test conventions for Omega