What problem does it solve?
Porting NVIDIA cuTile kernels (@ct.kernel) to Triton (@triton.jit) is error-prone: wrong API mappings, missing TMA usage, and layout-flag mistakes cause crashes or 5-50x performance regressions. This Skill provides a phase-gated conversion workflow with verified API mappings, checklists, and debugging guides.
Core Features & Use Cases
- Guided Conversion Workflow: A gated analyze β convert β validate β test β benchmark pipeline with a mandatory completion checklist covering correctness, TMA usage, and performance gates.
- API Mapping & Gotchas: Complete cuTile-to-Triton mapping tables (ct.load/ct.store, ct.mma, ct.launch, ct.Constant) plus documented translation errors like hardcoded pointer types and int32 stride overflow.
- Performance & Debugging References: TMA (tl.make_tensor_descriptor) enforcement for 2D+ loads, dual-kernel layout flag patterns, autotune grid via META, and fixes for cudaErrorIllegalAddress and numerical mismatches.
- Use Case: An engineer porting a TileGym softmax or attention kernel from cuTile to Triton follows the checklist, applies the API mapping, runs pytest gates, and benchmarks Triton against the cuTile baseline.
Quick Start
Ask your agent to convert the cuTile kernel in my repository to Triton and validate it with the TileGym pytest suite.