DRAFT for Adam. Facts, times, numbers, clips and your quoted prompts are real. Dashed boxes are yours to write. Section labels and captions are Claude's placeholders.
twentytwentytwenty

Combat Shine

Sept 29–30, 2026 · VFX, tooling, pipeline · Strangedeep

Before

  1. alright well there are tons of problems in the playthrough, we regressed on the death animation, i died from an attack of opportunity, also the new UI still sucks so much compared to the HTML versions we made, … continue with the wow, but the very basics of the game are total ass right now. how can we improve things? also the weird little pauses have to go.

Before clip goes here: the same fight with the shine switched off. Not recorded yet; it needs a Strangedeep session.
After: a hit with the shine on (Godot, Sept 30).

The prompts

  1. also i have another question. I am seeing amazing demos of HTML canvas animations that people are doing with opus. Is there any way to do that in strangedeep? have we blew it by moving into godot?

  2. i think we need to go ahead and get some of that shine in there! let's see the first demo

  3. ok, those are amazing! let's get that in the game!

  4. what else can we do here? i mean if you can add layers to the abilities and VFX and UI let's freakin go. let's hear a plan about all the things you can shine up

  5. uh, yes, all of these sound amazing

  6. alright, well the shaders on the stand-in armors aren't really that valuable, but for everything else it's amazing.

Influences

Adam writes this. Where the idea came from: the canvas demos, games, painting, anything else.

The turn

Adam writes this. What you realized, what you rejected and why, what changed your mind.

Try it

This is the exact lab the look was approved in. Every moment has a button, and the sliders are the same ones the Godot settings came from.

Open the lab on its own page

What AI did, what I decided

AI

  • Wrote the lab as one HTML file of canvas and vanilla JavaScript, and checked it in a browser.
  • Ported the approved look into Godot: six shaders plus C# to drive them from one settings file.
  • Wrote and ran the automated checks.

Adam

Adam writes this.

Stack

RoleModel or toolReasoningTime
Lead: plans, writes briefs, reviewsClaude Code, Opus 5.5xhighwhole session
Built the labOpus 5.5 subagentxhigh47 min
Ported it to GodotOpus 5.5 subagentxhigh64 min
Ran the checksSonnet 5.5 subagent (sd-runner)low46 min
LabHTML canvas 2D, vanilla JavaScript, no libraries
GameGodot 4.7.2 .NET, C#, GDShader (6 shaders), Compatibility renderer
Checks and footageNode.js verify scripts, Godot movie maker, ffmpeg
ReviewThe lab as a Claude artifact; decisions on the Review Desk

40 subagents ran across the whole session, about half Opus 5.5 and half Sonnet 5.5.

Proof

verify:combat-shine
438 checks passed
13 negative controls, all caught
0 environment rebuilds on revision-only, actor-only and loot-only updates
0.15 ms mean per frame, 1.8 ms max

What's next

Adam writes this. Known open items, for reference: the aim outline reads too bright on the small test enemy; clips still to record for critical, kill, miss, block and turn change; the enemy intent marks are built but not yet triggered by any rule.