superpowers VS claude-code

Meanwhile, the ecosystem materialized. obra/superpowers shipped a complete software development methodology built on composable skills — 1,276+ stars and growing. The cobusgreyling/loop-engineering repo cataloged patterns from Osmani and Cherny into a practical reference.

Projects like Superpowers proved that agents can follow structured methodologies — brainstorm before coding, write tests before implementation, review against specs before declaring success. The skills are mandatory workflows, not suggestions. The agent checks for relevant skills before any task.

If you're looking for complementary skills and plugins then have a look at Addy Osmani's Agent Skills or Superpowers, both provide essential coding assistant skills like Test-Driven Development (TDD). OpenSpec provides consistency, and your workflow can evolve around it.

Before any implementation, I plan. I use the brainstorming skill from Superpowers to think through the approach, then Grill Me - a separate skill that probes for contradictions, gaps, and missing assumptions, question by question. Once I'm satisfied, I save the result as a PRD and move to writing-plans (also from Superpowers), which produces a detailed implementation plan: class names, properties, architecture, tests.

These don't replace the spec; they govern how the agent acts on it. Superpowers uses guided Q&A to clarify intent, then runs sub-agents behind a verification-before-completion gate. GSD manages context in waves for solo developers. HVE Core runs an RPI loop: Research, Plan, Implement, Review.

> It would be extremely cool to be able to write one or two lines of prompt in my harness, and have a light model iterate with me a few times writing/proposing requirements, guidelines and explanations, refining the prompt until it's ready to be sent to the actual LLM.

I feel like the vast majority of AI-using coders already do this via skills suites like Superpowers (see /superpowers:brainstorming), no? https://github.com/obra/superpowers

I sometimes use Superpowers skills such as writing-plan and writing-spec. The Superpowers brainstorming skill stores design specs under docs/superpowers/specs/YYYY-MM-DD--design.md, and the writing-plans skill stores implementation plans under docs/superpowers/plans/YYYY-MM-DD-.md. (GitHub, GitHub)

obra/superpowers – GitHub

You really have to a) use Opus and b) use the frontend-design skill for decent results.

https://github.com/anthropics/claude-code/blob/main/plugins/...

agents are everywhere nowadays, one left a long pointless comment on a bug report i submitted on github. well, a bug report that an agent submitted on my behalf. agents all the way down. maybe i'm part of the problem.

https://github.com/anthropics/claude-code/issues/66085

https://github.com/anthropics/claude-code/issues/66780

Censored because I'm writing a paper. :)

Oh and forget learning about chemistry. Only criminals want to learn organic chemistry. :(

Anthropic's own frontend-design skill attempts to do that. You can install it in Claude Code, or you can tweak it to be closer to your own style:

https://github.com/anthropics/claude-code/blob/main/plugins/...

But what I find works best is to point Claude at a design system documentation website (your own company's or another public source) and tell it to use that design style. It usually does OK, and the results are usually much more in line with that style and not as Claude-y.

Quick grounding for anyone new: Claude Code is Anthropic's official agentic coding tool — an AI coding assistant that lives in your terminal. It reads your codebase, edits files, runs commands, and integrates with your dev tools through natural language. It runs in the terminal, in VS Code/Cursor and JetBrains, in a desktop app, on the web at claude.ai/code, and in the Claude iOS app — all sharing the same engine, so your CLAUDE.md, settings, and MCP servers travel with you.

anthropics/claude-code Issue #13717 (MCP at ~49% of context)

Source: https://github.com/anthropics/claude-code/issues/65697

However, with the VSCode extension, even if I perform a /clear, the source is overwritten as startup. This is a known issue tracked in GitHub issue #49937. It works if you use the CLI alone, but it cannot be identified when using the extension.