The README is unnerving. Do people really see the Claude-salesman style of writing as something normal?
On the other hand, I should be thanking Anthropic for making it so easy to spot, they might have done this intentionally.
This insufferable period of AI will eventually come to an end. We just have to power through as people get fed by it. Mindless writeups, social media posts, emails, cold calls.. they all bear common trait of no to low effort and it shows. It's as vapid and empty as the impulse that thought it would be a good idea. Some of us consciously go by the rule that if you haven't bothered to write, we're not going to bother to read.. rest will grow into the same mindset. Spam farms pretending to be sales optimizations, linkedin lunatics with "valuable messages", low effort slackers larping to be engineers.. it's all going to go away and true value will prevail. Right now, it's not too much different than nigerian prince letters, industrialized.
Yep I agree. I was looking for a getting started like for example here for openspec: https://github.com/Fission-AI/OpenSpec/blob/main/docs/gettin... but couldn't find anything like that
I found the At a glance section especially funny. Just a ton of buzzwords compressed together. One of the most dense tables I've ever seen on GitHub.
Agreed, I could just about bear it until I hit the “ Six load-bearing ideas” section. Very off-putting.
No thing-you-don't-want. No second-thing-you-don't want. Just thing-you-want, the-way-you-want-it.
It's midness. People don't find it good, it's just less effort to meh it.
>Do people really see the Claude-salesman style of writing as something normal?
In certain circles, yeah. It's bad powerpoint writing by ambitious but dull mid-level managers, memeified. There's a lot of it out there.
If you were to distill that kind of copy into an AI model and then reproduce it with just a touch of uncanny valley, yup. 100% that's what it is.
> That's not "AI tries to design something". That's an AI that has been trained, by the prompt stack, to behave like a senior designer with a working filesystem, a deterministic palette library, and a checklist culture
What, you don't want your senior designer to have a working filesystem and checklist culture? No deterministic palettes?