# Evals — scaling

These cases are routing and trigger fixtures, not an automated test harness. `should_trigger` lists prompts the `scaling` description and body must claim (including non-obvious and Catalan/Spanish phrasings); `should_not_trigger` lists near-miss prompts that belong to a real sibling, each tagged with the `route_to` id it should defer to (`performance`, `redis`, `postgresdb`, `monitoring`, `deployment`); `capability` is one launch-readiness scenario with a `must_include` rubric. To run them, read each prompt against `../SKILL.md` and confirm by hand that triggers fire, non-triggers route to the named sibling, and a real answer to the capability scenario covers every rubric line — or feed this file to the repo's eval runner if one is present. The k6 artifacts themselves are checked separately by `../scripts/verify.sh`.
