Skill
build-optimize
Priority: P1 (High — full build takes 60+ minutes, blocking development velocity)
Motivation
AITER's full build takes 60+ minutes, dominated by CK-Tile kernel compilation (Flash Attention alone generates 2782 HIP files, plus MOE GEMM variants). For development iteration, most developers only need a subset of kernels. A skill that analyzes build time bottlenecks and generates minimal build configurations would dramatically improve development velocity. This also supports the CK-free build strategy where CK kernels shift to FlyDSL as the backend.
What This Skill Should Do
- Profile build time: Analyze build logs to identify which targets/kernels consume the most compilation time
- Dependency analysis: Map which Python operators depend on which compiled kernels (CK, ASM, Triton)
- Suggest minimal configs: Given a target workload (e.g., "DeepSeek-V3 decode only"), output the minimal set of kernels needed
- Generate build flags: Produce CMake/build flags that skip unnecessary CK kernels for the target configuration
- CK-free feasibility: For each CK kernel, assess whether a Triton or FlyDSL replacement exists or is planned
Acceptance Criteria
Skill
build-optimizePriority: P1 (High — full build takes 60+ minutes, blocking development velocity)
Motivation
AITER's full build takes 60+ minutes, dominated by CK-Tile kernel compilation (Flash Attention alone generates 2782 HIP files, plus MOE GEMM variants). For development iteration, most developers only need a subset of kernels. A skill that analyzes build time bottlenecks and generates minimal build configurations would dramatically improve development velocity. This also supports the CK-free build strategy where CK kernels shift to FlyDSL as the backend.
What This Skill Should Do
Acceptance Criteria