What problem does it solve?
Porting tile-based GPU kernels from Triton-TileIR or cuTile-Python to cutile-rs (Rust) requires coordinating IR dumping, device kernel authoring, FFI host wiring, correctness testing, and performance benchmarking, which is error-prone when done ad hoc.
Core Features & Use Cases
- Bounded multi-agent pipeline: Orchestrates Agents A through F with a strict routing table, spawn caps, and verdict-based handoffs covering IR analysis, kernel conversion, host FFI, correctness, and performance stages.
- Deterministic validation scripts: Ships preflight, IR validation, per-agent validators, IR diffing, and a final 17-file aggregate kernel gate.
- Worked examples and references: Includes softmax (raw-pointer launch) and bmm (tiled-output launch) templates plus coding rules, op mapping, and IR diff checklists.
- Use Case: A developer adding a cutile-rs backend to a TileGym operator runs the pipeline to produce kernel.rs, ffi.rs, a Python wrapper, backend registration, and CUPTI-backed correctness and performance reports.
Quick Start
Ask the agent to convert a TileGym kernel such as softmax to a cutile-rs backend and let the skill run its preflight and agent pipeline automatically.