Elixir Skill Router

HARD-GATE

Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).

Routing priority

1. Playbook when the request is multi-step (TDD, bug fix, quality, setup, LiveView feature, Oban job, migration, PR review).
2. Atomic skill when the request is a single domain (Ecto query, channel auth, Credo config).
3. Fallbacks: language → elixir-essentials; web ambiguity → phoenix-liveview-essentials.

See assets/skill-map.json (mappings, defaults, disambiguation).

Core Process