shader-gen

1# Shader Generator
2 
3If `submit_shader` or `inspect_item` are not loaded yet, load them with `ToolSearch` before calling them, so you use their real parameters instead of guessing.
4 
5Submit-only: creates a backend generation job, returns `jobId`. Use the `track_progress` tool for job lifecycle after submission.
6 
7**Always use `generate.ts` for new shaders.** Manual authoring is only for editing existing asset code — never as a fallback when generation fails.
8 
9## Catalog-first rule — try existing assets before generation
10 
11Before generating a shader, call `browse_library` unless the user names an exact asset id that is already visible in `browse_assets`.
12 
13`browse_library` is the source of truth for built-in effects, built-in transitions, and project effect/transition assets. Built-ins are stable global asset ids, not per-project DB assets, so they may not appear in `browse_assets`.
14 
15Apply catalog entries with `edit_item`, do **not** call `submit_shader`.
16 
17Good catalog searches:
18 
19```text
20browse_library(query: "zoom")
21browse_library(category: "transitions", query: "dissolve")
22browse_library(category: "audio-fx")
23```
24 
25Generate only when no catalog entry matches the user's intent closely enough.
26 
27### `builtin:zoom` uses the same track-bound placement as every effect
28…