7 ms·

https://github.com/obra/superpowers https://github.com/obra/superpowers

by ahofmann 2mo ago

Culonavirus 2mo ago
Some people just need to complicate things as a state of their natural being. What a tremendous waste of time.
- AndyNemmity 2mo ago
  That's funny, cause I'd argue superpowers barely does anything, and you need a much more complex setup to gain value.
  - steve_adams_86 2mo ago
    I find it very useful. What do you use that’s better?
    - AndyNemmity 2mo ago
      I don't want to turn this into an, oh look at mine. It's just always been very behind the curve. I don't think you should use anyone's honestly. You should create your own shell base, and point to skills you find might add value, and add them. Then as you learn things about the shape of how things work, what you end up doing is rewriting them to follow your rules from what you learned. What you'll find is, you'll have significantly better skills and systems.
  - sixothree 2mo ago
    It's great for feature development. It queries you about you intentions, creates a spec for you to review and modify, creates a plan for it to follow, then farms out the work to subagents. Crap on it all you want, but it makes LLM work predictable.
    - jatora 2mo ago
      It does not make LLM work predictable. Try it on the same type of project twice and see. You think you're saving time but youd accomplish similar results with 2 or 3 skills.
      - swingboy 2mo ago
        Which 2 or 3 skills?
        jatora 2mo ago
        I'll correct myself. 1 Skill for helping refine your plan/spec with propositional yes/no questions. After that no more skills needed to emulate superpowers honestly. Workflows do the rest and claude will do that for you. ultracode is 90% of superpowers
      - steve_adams_86 2mo ago
        I think this depends a lot on two things: how well-defined your requirements are up front, and how well-defined the problem space/domain are. If there's some clarity and structure with clear expectations, it seems to produce fairly reliable, consistent results, and the process of validating specs with Claude can yield all kinds of unexpected dead-ends or holes in the idea you had. I find this very helpful. But I'm curious too, what are the skills you'd use instead? superpowers are just skills themselves.
      - sixothree 2mo ago
        How is an implementation spec that helps it author a plan to follow not considered predictable? What are these skills you are referring to specifically?
- jatora 2mo ago
  Exactly. It really is such a ridiculous waste of time
- mvkel 2mo ago
  In the three years I've been vibe coding, it's the only way I've found to consistently and reliably build complex apps. How do you do it?
  - ricardobeat 2mo ago
    Three years? Vibe coding became a thing roughly 1.5 years ago, around Sonnet 4 release. How would you even compare models from 2-3 years ago to today’s? Is this satire?
    - mvkel 2mo ago
      > Vibe coding is a software development practice assisted by artificial intelligence (AI) where the software developer describes a project or task in a prompt to a large language model (LLM) which generates source code automatically. Based on this definition, yep, I've been vibe coding since 2023. The products were less sophisticated, and I was copying and pasting one function at a time, but it worked. More important: it was something I couldn't do on my own. The modern version is that bonafide engineers accept AI-generated code. It's a good thing I'm not a bonafide engineer.
appplication 2mo ago
That initially looked pretty interesting but a quick peek through issues and folks are complaining that it’s opinionated on git workflows and overriding user instructions otherwise. No thanks. Edit: a deeper look at the issues and there are many examples of it not behaving as intended. Seems superstitious at best.
- ffsm8 2mo ago
  Definitely not superstitious. It's just an opinionated workflow, you can see the steps further down in the repository. It's just spottily enforced because it's just written to the context in markdown - it's basically one of the very first attempts from the very beginning of Claude code. But superstitious would mean it's just in your head, essentially - but this has an effect. It does create questionairs, documents every decision and plan etc. Wherever you want that is up to you, I personally didn't... But it's also definitely very much causing an big difference in behavior from Claude Code
- smartbit 2mo ago
  Didn’t know what Superpowers was until this thread. Found this blog [0] describing how amazing Fable was at enhancing Superpowers. [0] https://primeradiant.com/blog/2026/superpowers-6.html https://primeradiant.com/blog/2026/superpowers-6.html
deleted 2mo ago
[deleted]

https://github.com/obra/superpowers https://github.com/obra/superpowers

Culonavirus 2mo ago

Some people just need to complicate things as a state of their natural being. What a tremendous waste of time.

AndyNemmity 2mo ago
That's funny, cause I'd argue superpowers barely does anything, and you need a much more complex setup to gain value.
- steve_adams_86 2mo ago
  I find it very useful. What do you use that’s better?
  - AndyNemmity 2mo ago
    I don't want to turn this into an, oh look at mine. It's just always been very behind the curve. I don't think you should use anyone's honestly. You should create your own shell base, and point to skills you find might add value, and add them. Then as you learn things about the shape of how things work, what you end up doing is rewriting them to follow your rules from what you learned. What you'll find is, you'll have significantly better skills and systems.
- sixothree 2mo ago
  It's great for feature development. It queries you about you intentions, creates a spec for you to review and modify, creates a plan for it to follow, then farms out the work to subagents. Crap on it all you want, but it makes LLM work predictable.
  - jatora 2mo ago
    It does not make LLM work predictable. Try it on the same type of project twice and see. You think you're saving time but youd accomplish similar results with 2 or 3 skills.
    - swingboy 2mo ago
      Which 2 or 3 skills?
      - jatora 2mo ago
        I'll correct myself. 1 Skill for helping refine your plan/spec with propositional yes/no questions. After that no more skills needed to emulate superpowers honestly. Workflows do the rest and claude will do that for you. ultracode is 90% of superpowers
    - steve_adams_86 2mo ago
      I think this depends a lot on two things: how well-defined your requirements are up front, and how well-defined the problem space/domain are. If there's some clarity and structure with clear expectations, it seems to produce fairly reliable, consistent results, and the process of validating specs with Claude can yield all kinds of unexpected dead-ends or holes in the idea you had. I find this very helpful. But I'm curious too, what are the skills you'd use instead? superpowers are just skills themselves.
    - sixothree 2mo ago
      How is an implementation spec that helps it author a plan to follow not considered predictable? What are these skills you are referring to specifically?
jatora 2mo ago
Exactly. It really is such a ridiculous waste of time
mvkel 2mo ago
In the three years I've been vibe coding, it's the only way I've found to consistently and reliably build complex apps. How do you do it?
- ricardobeat 2mo ago
  Three years? Vibe coding became a thing roughly 1.5 years ago, around Sonnet 4 release. How would you even compare models from 2-3 years ago to today’s? Is this satire?
  - mvkel 2mo ago
    > Vibe coding is a software development practice assisted by artificial intelligence (AI) where the software developer describes a project or task in a prompt to a large language model (LLM) which generates source code automatically. Based on this definition, yep, I've been vibe coding since 2023. The products were less sophisticated, and I was copying and pasting one function at a time, but it worked. More important: it was something I couldn't do on my own. The modern version is that bonafide engineers accept AI-generated code. It's a good thing I'm not a bonafide engineer.

appplication 2mo ago

That initially looked pretty interesting but a quick peek through issues and folks are complaining that it’s opinionated on git workflows and overriding user instructions otherwise. No thanks. Edit: a deeper look at the issues and there are many examples of it not behaving as intended. Seems superstitious at best.

ffsm8 2mo ago
Definitely not superstitious. It's just an opinionated workflow, you can see the steps further down in the repository. It's just spottily enforced because it's just written to the context in markdown - it's basically one of the very first attempts from the very beginning of Claude code. But superstitious would mean it's just in your head, essentially - but this has an effect. It does create questionairs, documents every decision and plan etc. Wherever you want that is up to you, I personally didn't... But it's also definitely very much causing an big difference in behavior from Claude Code
smartbit 2mo ago
Didn’t know what Superpowers was until this thread. Found this blog [0] describing how amazing Fable was at enhancing Superpowers. [0] https://primeradiant.com/blog/2026/superpowers-6.html https://primeradiant.com/blog/2026/superpowers-6.html

deleted 2mo ago

[deleted]