What problem does it solve? Ascend C kernel developers frequently hit API misuse issues such as alignment violations, repeatTimes overflow, precision loss in half-precision arithmetic, and cross-core synchronization races. This Skill supplies verified usage patterns, parameter constraints, and platform-specific differences for the Ascend C API surface so kernels are written correctly the first time. ## Core Features & Use Cases - API Category Index: Covers arithmetic (Add/Sub/Mul/Div), reductions (ReduceMax/ReduceSum), data movement (DataCopy/DataCopyPad), Cube Matmul/GMM high-level APIs, buffer management (TBuf/TQue), precision casting, pipeline synchronization, cross-core flags, Hcomm point-to-point communication, HCCL host APIs, and DMA atomic operations. - Scenario-Based Guidance: Maps common operator scenarios (Softmax, LayerNorm, MatMul, GroupedMatmul, RoPE splitting, non-aligned data, mixed precision) to the right API patterns and pitfalls. - API Blacklist and Restrictions: Documents banned APIs (GlobalTensor::SetValue/GetValue in production), restricted APIs (DataCopy requiring strict 32-byte alignment), and platform-specific limits (DAV_2201 vs DAV_3510). - Use Case: When implementing a fused BatchMatmul + ReduceMax + ReduceSum operator on Ascend NPU, consult the Matmul, reduce, and cross-core sync references to coordinate Cube and Vector pipelines correctly. ## Quick Start Ask how to correctly use a specific Ascend C API such as DataCopyPad or ReduceMax, including its alignment constraints and platform limitations.