dev-asset-lesson

An asset pipeline lesson requires a consistent directory layout across pipeline/, common/, tools/, and tests/ to scaffold Python orchestration and C tooling. You define the scope for Type A, B, or C lessons with shared tests and documentation ensuring reproducibility.

Designing asset pipeline lessons involves hybrid Python and C scaffolding to teach production-grade asset tooling. You provide an initial README with scope, example config, and sample assets while following consistent directory layouts and validation criteria like CMakeLists.

Yes, validating an asset pipeline lesson requires a README, CMakeLists, tests, and example configurations. These validation criteria ensure your header-only library lesson aligns with forge-gpu asset pipeline conventions and maintains reproducibility.

Yes, the hybrid pipeline scaffolding supports asset processing, procedural geometry, and web frontend tracks. It integrates real-world forge-gpu asset workflows with cross-track references across Python-based orchestration and C-based tools.

Type A, B, and C lessons differ in scope and required structure within the asset pipeline. Each type defines specific roles for Python orchestration, C tools, and header-only libraries while maintaining shared tooling in common/ and tests directories.

Your asset pipeline lesson needs shared tooling in pipeline/ and common/ to ensure reusability across Python, C tools, and C libraries. Cross-track references integrate real-world forge-gpu asset workflows for consistent production-grade tooling.