What problem does it solve? Writing PyPTO operator kernels for Ascend NPU hardware requires strict adherence to layered architecture rules, tile shape constraints, dynamic axis handling, and JIT entry conventions. This Skill guides a coder agent through per-Phase incremental construction of operator implementation files, preventing common compile-time and runtime failures. ## Core Features & Use Cases - Per-Phase Module Generation: Produces one <op>_module<k>_impl.py per orchestrator dispatch based on DESIGN.md and module_interfaces.yaml contracts, then a cleanup pass that consolidates into <op>_impl.py plus a Chinese README.md. - Layer G-K Structure Enforcement: Builds implementations on the impl_template.py skeleton with strict separation between cache bridge, PyPTO sub-kernels, loop-owning kernel impl, JIT entry, and host wrapper. - Constraint & Error Guidance: Ships execution-constraints references, error-code troubleshooting flows, and shell scripts for CANN environment setup and idle NPU chip detection. - Use Case: An orchestrator assigns active_module M2 for a fused attention operator; the coder agent reads the design docs, emits the applicable constraint checklist, and generates exactly one compliant module impl file before stopping. ## Quick Start Ask the agent to implement the current active module of your operator using the pypto-op-develop skill with the existing SPEC.md, DESIGN.md, and module_interfaces.yaml.