flutter-scene-assets-shaders

Files (20)

• .DS_Store
• SKILL.md
• animation.txt · examples/
• build-hook.txt · examples/
• raw-shader.txt · examples/
• shaderbundle-manifest.txt · examples/
• stress-tests.txt · examples/
• toon-dart.txt · examples/
• toon-fmat.txt · examples/
• assets-and-animation.md · references/
• materials-and-shaders.md · references/
• animation.txt · references/sources/
• assets-and-loading.txt · references/sources/
• custom-materials.txt · references/sources/
• declarative-scenes.txt · references/sources/
• flutter-gpu-api.txt · references/sources/
• flutter-gpu-shaders-readme.txt · references/sources/
• geometry.txt · references/sources/
• materials.txt · references/sources/
• shader-material-api.txt · references/sources/

SKILL.md (first lines)

# Scene assets and shaders

Choose the shader owner first. Use Scene's `.fmat` and `PreprocessedMaterial` for a managed Scene mesh. Use a compiled raw shader bundle with Scene's `ShaderMaterial` when a Scene mesh needs direct stage control. Use `package:flutter_gpu/gpu.dart` bindings when writing a direct GPU render pass. Each path has its own resource and uniform binding API.

- For glTF, textures, geometry, and animation, read [assets-and-animation.md](references/assets-and-animation.md).
- For `.fmat`, raw shaders, material binding, and color output, read [materials-and-shaders.md](references/materials-and-shaders.md).

Keep asset names, shader parameter names, vertex attribute names, and Dart bindings consistent. Load and create GPU resources outside per-frame code. Use the source path when loading Scene assets converted by its build hook.

After a build-hook, asset, material, or shader binding change, run `flutter analyze` and build the affected target. Open a small scene with the asset or material on each supported target and inspect the rendered result. Analysis alone cannot verify shader compilation, GPU bindings, or output pixels.

From mordechai30/flutter-dart-skills, BSD-3-Clause.

More from mordechai30/flutter-dart-skills