What problem does it solve?
Writing portable, production-quality Slang shader code requires deep knowledge of modules, generics, parameter blocks, capabilities, and cross-compilation targets, and mistakes in these areas cause subtle backend-specific bugs.
Core Features & Use Cases
- Shader Authoring and Review: Write, refactor, and review Slang code for graphics, compute, tessellation, and ray tracing stages with correctness, portability, and performance checks.
- Cross-Compilation Guidance: Compile Slang to SPIR-V, DXIL, GLSL, Metal, CUDA, and CPU targets using slangc with explicit capability and layout handling.
- Engine Integration: Design reflection-driven C++ host integration with parameter blocks, binding layouts, and CMake setup.
- Use Case: Ask for a PBR vertex/fragment shader pair using parameter blocks targeting Vulkan, and receive validated Slang code with binding summaries and host-side assumptions.
Quick Start
Ask the assistant to write a Slang compute shader with parameter blocks that compiles to both SPIR-V and DXIL.