What problem does it solve? Developing Ascend C MC2 operators that fuse multi-card collective communication with on-device computation involves choosing among multiple communication paths (AIV+URMA, MTE, CCU) and coding foundations (blaze-shmem, apace, ascendc-api), each with strict red-line constraints. This Skill provides the decision trees, capability registry, route-specific constraints, and review checklists needed to design, implement, debug, and optimize these fusion operators correctly. ## Core Features & Use Cases - Route Decision & Capability Registry: A decision tree plus a route registry table maps chip (dav-3510/dav-2201), operator type (collective-comm/MoE), invocation form, communication path, and coding foundation to supported, planned, or explicitly unsupported combinations. - Three Coding Foundation Guides: Detailed references for blaze-shmem (SHMEM + Blaze templates), apace (APACE template framework with D1-D6 design contracts and R1-R21 red lines), and ascendc-api (MTE-based MoE Dispatch/Combine with four mandatory constraints). - Requirement Analysis & Quality Gates: Grill protocol with 9 interrogation dimensions, REQUIREMENTS.md template, 14-item quality checklist, and development-readiness gating. - Use Case: When asked to build an AllToAll+Matmul fusion operator on Ascend 950, the Skill routes you to the apace or blaze-shmem path, enforces constraints like banning HCCL high-level APIs, and provides profiling guidance with L2 cache flushing. ## Quick Start Ask the assistant to design or review an MC2 communication-compute fusion operator such as AllToAll+Matmul or MoE Dispatch on Ascend hardware, and it will apply the appropriate route decision tree and constraints.
