Superpowers is pretty much convincing LLMs they can do better. It almost never works that way.
Superpowers 6
51–60 of 84 posts
Re: Superpowers 6
#52[deleted]
Re: Superpowers 6
#53I gave Superpowers 5.x a whirl for a week, and aside from consuming a stupid amount of tokens, it did materially worse across all my personal benchmarks and general day-to-day development compared to plain Codex/Claude. I'm convinced it's either some 4D ploy by the AI cartels to set tokens ablaze, or it only provides Superpowers to those without any power to begin with. Rating: 1/5 Pinocchios. Would not recommend.
This. I found superpowers a huge token guzzler. And more generic a skill is the worse it seemed to perform. I have found that skills are something you need to build yourself and for your needs and most importantly be willing to throw away. One team I know blindly checked this into every repo they had. They also had the highest cost per pr across all teams in our org (of about 60 eng teams). AI has already given peopl…
This. I found the original superpowers was a great start, but rewrote all those skills to fit my workflow, and iterated on that.
Writing skills is the new writing code.
Re: Superpowers 6
#54The screenshot of ol' claude closed code with that ascii table tells it all: Vapor AIware.
As if it really would work like that. The noise added by the verbosity alone is not taken care of enough, and this entire thing belongs on the great pile of ai vaporware.
Re: Superpowers 6
#55I think I’ve mostly found superpowers helpful, especially for TDD. It’s cool from this blog (and their GitHub) that they’ve verified it in various ways too. One issue is that I’ll sometimes see it wanting to write a whole doc for a follow on feature with a similar structure and have to tell it to just use the last one again.
The most annoying thing is that it always pauses before implementing to ask if I want it to use Subagents (which it always recommends) or not.
Re: Superpowers 6
#56I'm honestly surprised at all the people here commenting that superpowers didn't work out for them. For me personally, it was a game changer when I first began using it and now it simply is as much a part of my workflow as any say, using git (yeah it has its warts but way way more value). Also, the latest (version 6) is noticebly token efficient as claimed. Did the people who found it underwhelming not try starting w…
I feel the same way. I've used superpowers since I found it during the initial Ralph hysteria and love it. Every task I do starts with brainstorming and it always produces great results, even coordinating across multiple repos. Having the plan to read and comment on ahead of time is great, although admittedly maybe that is built in to the major harnesses now and I just don't know about it. Always feel uneasy kicking…
Same here, the brainstorming and research phases are good and the spec part at well, I do side adversarial reviews all the time with other independent agents and feed sp the reviews and they are tools to avoid gliding over the surface. The dev process is longer but the result when done in a sound architecture with documented practices is quite good even though it’s slow.
Very happy with the tool so far
Re: Superpowers 6
#57I gave Superpowers 5.x a whirl for a week, and aside from consuming a stupid amount of tokens, it did materially worse across all my personal benchmarks and general day-to-day development compared to plain Codex/Claude. I'm convinced it's either some 4D ploy by the AI cartels to set tokens ablaze, or it only provides Superpowers to those without any power to begin with. Rating: 1/5 Pinocchios. Would not recommend.
The model
|
The harness
|
The harness of the harness?!!
Re: Superpowers 6
#58To be blunt I can't take this product seriously when they don't even run benchmarks. Your prompts make Claude better? Cool: prove it. Methods to evaluate LLM performance exist, they're called evals/benchmarks, and every company that is serious about AI runs them when they release a new version. (Of course benchmarks have their own issues, but squabbling over which benchmark is best and what issues there are is step 2…
To be blunt you should perhaps read the README before being condescending and dismissive. https://github.com/prime-radiant-inc/superpowers-evals
Re: Superpowers 6
#59Superpowers feels like 20 years ago when people would be sharing and debating their incredibly elaborate .vimrc files, which totally made them super productive. Meanwhile, I tried to stick to stock configuration as much as possible (mostly for portability / ssh reasons). In a similar vein, these days some of my colleagues are sharing all their skills and prompt tricks and stuff, and I try to just use barebones Claude…
Ultracode is pretty good. I’m not basically using the grill-with-docs from Matt and default plan mode on Cc or codex. It’s just enough.
Is it usable on Pro plan? Seems like it would burn my rate limits immediately
Re: Superpowers 6
#60I think I’ve mostly found superpowers helpful, especially for TDD. It’s cool from this blog (and their GitHub) that they’ve verified it in various ways too. One issue is that I’ll sometimes see it wanting to write a whole doc for a follow on feature with a similar structure and have to tell it to just use the last one again. The most annoying thing is that it always pauses before implementing to ask if I want it to u…
This is the point where I usually start a new session with a fresh context window and invoke the sub-agent development skill and just point to the spec+plan.
I’d be curious to see if there was a way to automatically do this for me in Claude Code.