Live data from Hacker News

Superpowers 6

blog.fsck.com

21–30 of 84 posts

Re: Superpowers 6

#21
I'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 with the brainstorming skill first?

Re: Superpowers 6

#22
post #20

All these prompt and skill based git repos are sus... nothing is benchmarked -its all so subjective and unproven and breaks with model updates -everyone and his uncle has a 'secret sauce skill' -that just proves to me the subjectivity of this endeavor.

Ehe ... https://github.com/prime-radiant-inc/superpowers-evals

Re: Superpowers 6

#23
post #6

I 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.

I'm a certified Superpowers hater. It's just not necessary with the modern models and fills up the context windows with garbage and adds an insane number of turns for no benefit.

I had similar prompts back when the models were terrible at instruction-following, so it was actually useful to fill up their context with a mass of instructions so they'd be less likely to forget rules.

Now I've got a few small slash commands or pasted prompts that work perfectly every time as the models follow them exactly.

Re: Superpowers 6

#24
Superpowers 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 Code as much as possible, and I feel like it keeps getting better and better and all these prompt shenanigans are just not worth it.

Re: Superpowers 6

#25
For what it's worth, I really enjoy superpowers. In particular, it does a great job with TDD that stops the model from jumping to conclusions, and I've been able to get it, even with Opus, to execute on much longer specs quite well.

Re: Superpowers 6

#26

How does Superpowers compare with Matt Pocock's skills[1]? I only tried the latter, and to be honest, I had positive results without burning a quadrillion tokens. [1] https://www.youtube.com/watch?v=-QFHIoCo-Ko

apparently Matt has a upgraded version /grill-with-docs

https://www.youtube.com/watch?v=6BB6exR8Zd8

Re: Superpowers 6

#27
This is great in concept but what prevents me from using it is TDD. I don't want to waste tokens on producing code that doesn't ship to the end user. Design by Contract is a far superior approach. If you've never heard of Design by Contract I don't blame you, our culture really failed to bring it mainstream. But I swear by it and it gives me real superpowers. Maybe I should fork this and gut the TDD part and replace it.

Re: Superpowers 6

#28

I'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 off a task without having used superpowers.

Re: Superpowers 6

#29
My use case is I have them installed and let Claude decide when to use them. Looks like for my recent sessions it has been using superpowers:test-driven-development 5%, and superpowers:subagent-driven... 1%. I haven't really been working on new projects this past week though which seems to be where they fire off the most, in particular the "writing a plan" one.

Re: Superpowers 6

#30

How does Superpowers compare with Matt Pocock's skills[1]? I only tried the latter, and to be honest, I had positive results without burning a quadrillion tokens. [1] https://www.youtube.com/watch?v=-QFHIoCo-Ko

I heckin love his /grill-me skill. Terse, to the point, and delivers outsized results. Gonna take a moment to share my own generic "retro" prompt, which has found many areas of improvement IME. > Let's conclude with a retro. Did you run into any issues during this session that you think could be improved? Any failed tool calls, confusing docs/prompts, or tricky wording that took you effort to figure out, etc? Any fin…

> This prompt reveals how absolutely _ass_ the Claude Code harness is (so many stupid tool call failures)

I've just started using Claude Code this month after months of Claude in VSCode + GitHub Copilot (and a bit of dabbling with AWS Kiro), and I'm actually impressed by how seemingly polished Claude Code is.

I think Copilot in VSCode broke far more in my months of (ab)using it.

Post reply on HN