krnopt-hw-aware-optimization

Identify GPU compute capability and workload shape for CUDA kernel optimization.

Updated May 27, 2026
One-click install
npx skills add https://github.com/igamenovoer/domain-skills --skill krnopt-hw-aware-optimization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: krnopt-hw-aware-optimization
Source: https://github.com/igamenovoer/domain-skills/tree/main/domain/cuda/krnopt-hw-aware-optimization
Command: npx skills add https://github.com/igamenovoer/domain-skills --skill krnopt-hw-aware-optimization

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps engineers reason about architecture-specific CUDA optimization to maximize kernel throughput on target GPUs by mapping workload characteristics to hardware surfaces and selecting appropriate optimization branches.

Core Features & Use Cases

  • Hardware-branch aware analysis across pre-SM90, SM90 Hopper, SM100 Blackwell, and consumer Blackwell to pick the right strategy.
  • Domain-driven planning for MoE, grouped GEMM, FP8 precision paths, and data-movement patterns, with actionable code-path recommendations.
  • Structured plan linking hardware targets to concrete code shapes (TMA, WGMMA, TMEM, CLC, PDL) and measurable validation steps.

Quick Start

Outline a hardware-aware CUDA optimization plan for your kernel.

Frequently Asked Questions about krnopt-hw-aware-optimization

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan hardware-aware CUDA optimization for a specific GPU compute capability?

Hardware-aware CUDA optimization maps your kernel's workload shape to target GPU compute capabilities, selecting an architecture branch like pre-SM90, SM90 Hopper, or SM100 Blackwell to maximize throughput with appropriate hardware surfaces.

What is the best way to optimize MoE and FP8 precision kernels on SM90 Hopper architectures?

Optimizing MoE and FP8 kernels on SM90 Hopper requires domain-driven planning that maps data-movement patterns to specific code shapes like TMA and WGMMA, providing actionable code-path recommendations and measurable validation steps for profiling.

How do I map workload characteristics to hardware surfaces like TMA and WGMMA?

Mapping workload characteristics to hardware surfaces involves identifying the target compute capability and specifying candidate surfaces like TMA, WGMMA, TMEM, CLC, or PDL to construct a structured plan linking hardware targets to concrete code shapes.

Does kernel optimization strategy differ between SM90 Hopper and consumer Blackwell GPUs?

Kernel optimization strategy differs across architectures by recommending specific architecture branches, separating SM90 Hopper from consumer Blackwell to select the correct hardware-aware optimization path and candidate surfaces for target validation.

Why do I need to specify evidence and next steps for profiling and validating kernel throughput?

Specifying evidence and next steps for profiling confirms the hardware utilization hypothesis, ensuring that the selected architecture branch and code shapes like TMA actually maximize kernel throughput on the target GPU.

Can I use CUTLASS for grouped GEMM optimization on SM100 Blackwell architectures?

Grouped GEMM optimization on SM100 Blackwell benefits from hardware-aware planning that selects appropriate code paths and surfaces like TMEM, ensuring the CUTLASS-based implementation matches the target architecture's unique compute capabilities.