This is where Hydra's knowledge lives — every domain, every proven approach, every pattern it knows. Drop a TOML file and Hydra learns a new domain. No training. No fine-tuning. No code.
- One folder per skill — named clearly (e.g.,
architecture/,finance/,security/) genome.tomlis required — contains[[entries]]with situation + approach pairsfunctor.tomlis optional — maps domain concepts to axiom primitives (Risk, Understanding, Dependency, Volume)- Hydra reads on boot — skills are loaded into the genome store at startup
- You can add skills at any time — restart Hydra to load new ones
- Hydra writes here too — the self-writing genome creates entries in
skills/generated/
skills/
README.md ← this file
architecture/
genome.toml ← 10 proven approaches
functor.toml ← axiom mappings
finance/
genome.toml ← 26 proven approaches
functor.toml
developer/
genome.toml ← 30 proven approaches
functor.toml
... (29 skills total, 303 genome entries)
# genome.toml
[[entries]]
situation = "choosing between microservices and monolith"
approach = "start with a monolith — extract services only when boundaries are clear"
confidence = 0.91
observations = 5000See SKILL-FORMAT.md in this folder for the complete specification.
When you ask Hydra a question, the genome store queries all loaded skills using IDF-weighted scoring + axiom vector cosine similarity. The best matches are injected into the prompt as proven approaches — with mathematically grounded confidence intervals.
Drop a TOML file. Hydra learns a new domain. That is it.