Routing rules

Updated May 29, 2026

The router asks a short question list and resolves to a single skill:

  • Typing or public-surface question → python-types-and-apis.
  • Exception or logging question → python-errors-and-logging.
  • Decorator, descriptor, context manager, or metaclass → python-abstractions.
  • Iterator or generator refactor → python-iterators-and-generators.
  • Container choice (msgspec, dataclass, TypedDict) → python-data-shapes.
  • Concurrency or subinterpreter question → python-concurrency.
  • Testing pattern, fixture, plugin → python-testing.
  • Verification adversary selection → python-verification, then load one of hypothesis, crosshair, or mutmut.
  • Dead code, clones, profiling → python-quality-tools.

Pairing rules:

  • Web or worker boundaries usually pair python-errors-and-logging with python-concurrency or python-data-shapes.
  • Library API work usually pairs python-types-and-apis with python-data-shapes (data-shaped surface) or python-abstractions (behaviour-shaped surface).
  • Verification work always starts with python-verification; a deep dive follows only after the selector confirms the right tool.