Open the ShaderToy an account you already use, then ask Strawberry to turn the work in front of you into a reviewable next step. It can help across shader projects, render settings, code experiments, and publish-ready descriptions, using the relevant tabs and files you choose.
01
A shader experiment is easier to revisit when the intent is recorded.
From the ShaderToy project, code, and notes you selected, Strawberry can assemble a concise experiment record: what is being explored, what changed, and what should be tested next. That makes visual iteration less dependent on memory.
02
Render artefacts should become a test plan, not a vague hunch.
Show a companion the ShaderToy work and the visual issue you are seeing.
It can structure a diagnostic checklist around the visible shader code, inputs, and expected result, leaving the actual edits for your review.
03
Good examples need an explanation people can follow.
Strawberry can prepare a readable project description from the ShaderToy tab, explaining the effect, key controls, and notable techniques in language suited to the audience you choose. You decide what is accurate enough to publish.
04
A weekly experiment log preserves the thread between visual iterations.
Save your ShaderToy review format as a skill and run a Friday routine that prepares a log of open experiments, unresolved artefacts, and the next visual test. Friday works because it captures the week’s trials before the next session starts from scratch.
ShaderToy Strawberry