What problem does it solve?
It prevents MoE changes from drifting away from TensorRT-LLM’s current architecture by enforcing clean ownership boundaries across ConfigurableMoE, MoEScheduler, backends, quantization/weights, EPLB, communication, and routing-factory logic.
Core Features & Use Cases
- Architecture-aligned design and refactoring: Guides reviews and edits that touch MoE modules (fused_moe modules, ConfigurableMoE, MoEScheduler, communication strategies, EPLB, quantization/weight handling, routing/factories, and MoE tests).
- Owner-boundary enforcement: Ensures behavior is implemented in the correct layer (assembler vs scheduler vs backend compute vs quantization-weight methods vs communication strategies).
- Testability and safety gates: Requires citing canonical code patterns and planning targeted unit coverage for the specific boundary being changed (including multi-GPU and EPLB/migration-related behavior).
Quick Start
Use the trtllm-moe-develop skill to review or plan a refactor you intend to make in TensorRT-LLM’s MoE codebase, ensuring the change preserves architecture boundaries and includes the right MoE tests.