Adds or edits runnable tt3de demos under demos/ using Textual and TT3DViewStandAlone: app skeleton, scene graph, ShaderPy wiring, textures, and camera setup. Does not author TTSL shader source—delegates SHADER_SRC to ttsl-implementation. Runs a short discovery pass first with suggested answers the user can accept via shorthand. Use when the user asks for a demo, example app, standalone viewer, or demos/2d or demos/3d scripts.
Writes and edits Tiny Tiny Shader Language (TTSL) shader source, and implements compiler / VM / opcode changes when needed. Use for TTSL materials, shading logic, all_passes_compilation, ttsl_run, ShaderPy, globals_dict, tt_* builtins, tt_texture, or extending python/tt3de/ttsl/, low_level_def, gen-opcodes.
Facilitates structured Q&A to author standardized tt3de evolution documents under `.evolution/` (versioned markdown). Reads `source/` docs for project context. Supports starting from scratch, recovering an incomplete evolution, or using an existing evolution as reference. Challenges proposals across functionality, technical design, usability, testability, complexity, and a priori performance. Use when the user mentions evolution documents, `.evolution/`, roadmaps, design proposals, or `/create-skill tt3de-evol`.
Facilitates structured Q&A to author standardized tt3de evolution documents under `.evolution/` (versioned markdown). Reads `source/` docs for project context. Supports starting from scratch, recovering an incomplete evolution, or using an existing evolution as reference. Challenges proposals across functionality, technical design, usability, testability, complexity, and a priori performance. Use when the user mentions evolution documents, `.evolution/`, roadmaps, design proposals, or `/create-skill tt3de-evol`.
Implements low-level operations in the tt3de engine — Rust core changes in src/ (geometry, raster, materials, buffers, textures, VM helpers) surfaced to Python via pyo3 thin bindings (*_py.rs) and matching wrappers under python/tt3de/. Runs a thorough design discovery pass first to validate the approach (subsystem placement, ownership/lifetimes, hot-path impact, parallel variants, Python API shape, error handling, tests), proposing reasonable defaults the user can accept by shorthand. Use when adding or changing native operations, when the user mentions "low-level", "Rust binding", "pyo3", "*_py.rs", "hot path", "raster", "geombuffer", "primitivbuffer", "primitiv_building", "vertexbuffer", "drawbuffer", "texturebuffer", "material bridge", "MaterialBufferPy", "DrawingBufferPy", "render_primitive", "PixInfo", "maturin develop", or asks to expose a Rust function/class to Python.
Implements high-level tt3de Python API and end-user ergonomics for Node2D, Node3D, Prefab, and asset loading flows (OBJ, BMP, PNG) without changing Rust code. Runs a design discussion first so the user drives the public interface, keeping the result simple, clear, and neat for project end users. Use when adding or changing Python scene graph helpers, prefab factories, loaders, convenience APIs, or high-level behavior under python/tt3de/.
Implements low-level operations in the tt3de engine — Rust core changes in src/ (geometry, raster, materials, buffers, textures, VM helpers) surfaced to Python via pyo3 thin bindings (*_py.rs) and matching wrappers under python/tt3de/. Runs a thorough design discovery pass first to validate the approach (subsystem placement, ownership/lifetimes, hot-path impact, parallel variants, Python API shape, error handling, tests), proposing reasonable defaults the user can accept by shorthand. Use when adding or changing native operations, when the user mentions "low-level", "Rust binding", "pyo3", "*_py.rs", "hot path", "raster", "geombuffer", "primitivbuffer", "primitiv_building", "vertexbuffer", "drawbuffer", "texturebuffer", "material bridge", "MaterialBufferPy", "DrawingBufferPy", "render_primitive", "PixInfo", "maturin develop", or asks to expose a Rust function/class to Python.
Implements high-level tt3de Python API and end-user ergonomics for Node2D, Node3D, Prefab, and asset loading flows (OBJ, BMP, PNG) without changing Rust code. Runs a design discussion first so the user drives the public interface, keeping the result simple, clear, and neat for project end users. Use when adding or changing Python scene graph helpers, prefab factories, loaders, convenience APIs, or high-level behavior under python/tt3de/.