If I wasn’t so attuned to agent slop, I’d be thinking I’m just too dumb to get it but no, whatever GPT model wrote this is not good enough (and the fact this was published by OpenAI suggests this is not an operator skill issue).

I can share the code if there's interest.

Sometimes it doesn't split it among optimal boundaries, but it's usually good enough to help. There's probably room for improvement and extension (eg. re-splitting a branch containing many not-logical commits, moving changes between commits, merging commits, ...) – contributions welcome!

You can install it as a Claude Code plugin here: https://github.com/KevinWuWon/kww-claude-plugins (or just copy out the prompt from the repo into your agent of choice)

Arbitrary structure rules like "do_thing_a(); do_thing_b(); do_thing_c();" also is not unless you can explain how this helps make it easier to understand compared to say, one big function with "// DO THING A" comments.

Basically, you should aim to minimise complexity in software design, but importantly, complexity is defined as "how difficult is it to make changes to it". "How difficult" is largely determined by the amount of cognitive load necessary to understand it.

I wonder if LLMs can use the type information more like a human with an IDE.

eg. It generates "(blah blah...); foo." and at that point it is constrained to only generate tokens corresponding to public members of foo's type.

Just like how current gen LLMs can reliably generate JSON that satisfies a schema, the next gen will be guaranteed to natively generate syntactically and type- correct code.

https://x.com/windsurf/status/1951340259192742063

git-branchless is just a better set of tools for working on a git repo so local tools like the JetBrains git integration will work just fine.

It operates on a similar philosophy to Jujutsu (make it easy to manipulate the commit tree) and the authors did exchange ideas with each other.

Have you considered a fourth file for Implemented such that Spec = Implemented + Design?

It would serve both as a check that nothing is missing from Design, and can also be an index for where to find things in the code, what architecture / patterns exist that should be reused where possible.

And what about coding standards / style guide? Where does that go?

From my research, a home battery costs, per kWh, about 8x an electric car battery and I don't know why.