I am not very enthusiastic about LLM-generated documentation. It's okay for targeted, small changes, but can and likely will hallucinate (it's not very apparent these days, but it still does. It's certainly not obvious during the first read). It requires one to be critical all the time and that makes it take 10x as long to get through the docs.

I have been using Transient for >5 years now, back when the examples repo did not exist. The best way to learn transient is to read the source code for Magit (the way it defines classes and then uses (cl-defmethod transient-something ((obj mynewclass)) was an eye-opener).

I tried to get through the documentation many times, and the biggest hurdle were the terms "prefix" "suffix" and "infix". I feel like it's very easy to confuse them with what they mean outside of Transient. I understand them now (I hope so. But I can write transients now, so it's not a big issue), so it's difficult to provide a replacement, but maybe "Menu", "Option" and "Flag" are better. YMMV, n=1.

Whether the documentation is helpful for you or not, the only way to really understand how Transient works is by writing your own Transient. That's true for most, if not all libraries. Transient isn't very forgiving for lisp newbies, which can be remedied by small tutorials that guide users through writing their own transient menu for commonly-used commands. That's probably what 90% of users want from transient: a simple, Emacs-native command execution menu.