functional-area-resolver

To compress large AGENTS.md routing files, replace per-skill rows with functional-area dispatchers that list sub-skills in a (dispatcher for: ...) clause. This pattern reduces context budget overhead while preserving access to all sub-skills.

A functional-area dispatcher is a single routing entry that replaces many per-skill rows by listing sub-skills in a (dispatcher for: ...) clause. It compresses large routing files like AGENTS.md and RESOLVER.md to keep routing maintainable as skill counts scale.

Yes, you can use area-level dispatchers without losing sub-skills reach. The dispatcher pattern lists all sub-skills within a (dispatcher for: ...) clause, ensuring full access is preserved while significantly reducing the routing file's context budget.

You verify routing accuracy before committing by applying built-in verification gates and historical AB evaluation. Running routing-eval checks ensures the functional-area dispatchers maintain correct LLM agent routing decisions without errors.

Your RESOLVER.md file exceeds the context budget because it grows with every added skill. Compressing routing into functional-area dispatchers replaces numerous per-skill rows with single area entries, enabling efficient memory loading and faster routing decisions.