No, I don’t know what those are. (Looked them up and I don’t teach every possible handler, but I teach people how to do structured inputs etc..)

I teach TDD philosophy as well as conways law, parnas hiding etc…without using those terms

So things like problem decomposition into tractable chunks minimum viable product, prototyping, how do you iterate, write the smallest possible test… you know things like this which are just taking incremental work and then iterating on it

It’s basically everything I’ve learned about building stuff since 1997

**Interestingly I thought prompt engineering was going to be a fad but it’s turned into a whole ass new discipline which makes less sense as more robust toolchains come into play and models handle the context interpretation better

Not the original commenter, but I feel pretty strongly that frameworks for software review loops are at best training wheels for people who haven't yet developed the right understanding. I don't use any sort of complex skills framework, I just tell the AI what I want while leaving reasonable Claude-sized gaps to fill in, and my results are usually better and often faster than people who get lost in framework management. Perhaps they're more useful for pure greenfield development, but for most software developers who are working on existing systems I have not seen a strong use case for them.

There's one guy I know who constantly has problems with Claude going off-script, and every time I dig in, it's clear that the poor thing is so overloaded with instructions and skill lists that it can't figure out what he actually wants it to do.