Never used this tool before cause I didn’t know it existed. I was scrolling through the slash commands and noticed it, ran it on a whim. It provided several actually useful lines to add to CLAUDE.md and some useful skills and hooks too. I imagine this could improve workflows for a lot of folks who didn’t know about it. Here’s the gist it gave me: <begin ai text> At a Glance What’s working: You run Claude like a disciplined engineering lead: multi-hour, phased Burst/ECS optimization campaigns and large Spline-to-skeleton migrations, all structured into numbered slices with handoff docs and context anchors. You consistently demand empirical proof—profiler instrumentation, characterization tests, full suites passing—before accepting commits, which has turned ambitious goals into verified wins like a 39x BuildMesh speedup and major heap pressure reductions. You’re also strong at insisting on true root causes for hard bugs (cross-frame races, domain-reload leaks, namespace shadowing) rather than surface patches. Impressive Things You Did → What’s hindering you: On Claude’s side, the recurring pattern is trial-and-error fixes that regress before converging—especially on mesh geometry and shaders, where a change passes a weak test while leaving normals flipped, holes present, or the plant brighter instead of dimmer. On your side, the friction is mostly environmental: verification ran against the wrong Unity worktree or with the editor closed, producing fabricated-looking metrics and even a broken merge to main, and shell heredoc quoting repeatedly mangled commit messages. Where Things Go Wrong → Quick wins to try: Try Task Agents to formalize what you already do manually—spin isolated sub-agents per migration phase that self-verify against the full suite before reporting back. For your geometry work, ask Claude to write adversarial topology assertions (manifold-ness, winding, no self-overlap) up front so fixes are judged against a real oracle, not one weak test. A Hook that confirms the active worktree and editor state before any verify/merge step would eliminate your most damaging false-confidence failures. Features to Try → Ambitious workflows: As models improve, your phased migrations become a natural fit for a coordinator agent that fans out 5-10 independent worktree refactors in parallel, each self-verifying and only merging when green—collapsing multi-day campaigns into parallel bursts. Your mesh sessions could run a fully autonomous test-driven convergence loop that reverts any regressing change until the geometry provably converges or surfaces a structural redesign as a blocking finding. And your performance work could shift to an autonomous profiler-driven agent that generates ranked, evidence-backed root-cause hypotheses and commits only verified, reproducible wins—skipping the wrong-hypothesis detours that burned cycles. On the Horizon → <end ai text> Curious what it says for others. submitted by /u/SmallKiwi
Originally posted by u/SmallKiwi on r/ClaudeCode
You must log in or # to comment.