Claude Code Superpowers: Skills, Workflow, and What to Save

Claude Code Superpowers is a community plugin that adds a set of pre-built skills to Claude Code. Each skill is a reusable instruction sequence that tells Claude Code how to handle a recurring task — generating a changelog, reviewing a pull request, writing tests — without you writing the instruction from scratch each time.

Skills are a good starting point, not a final answer. The task plan you are working through and the lessons you learn along the way still need a home outside the session. Tools like fenbs keep that record, so the next session can build on what the plugin helped you produce.

What is Claude Code Superpowers?

The plugin distributes its skills as files that Claude Code reads, typically through a CLAUDE.md entry or a skills directory in your project. Each skill defines what Claude Code should do when you invoke it by name. Because the skills are plain text, you can read them, copy them, and adapt them to your project.

Being community-built, Superpowers is not maintained by Anthropic. The skill definitions can drift out of date as Claude Code evolves. Check the project's repository for compatibility with your current Claude Code version before relying on its skills for important work.

How do you install Claude Code Superpowers?

Installation typically involves downloading or cloning the skill collection and pointing Claude Code at it through your project or global CLAUDE.md. The exact steps are in the plugin's own documentation; follow those steps and then verify the install with the step below.

1. Follow the installation instructions on the plugin's repository. This usually means running a setup command or adding a reference to your CLAUDE.md.
2. Open Claude Code in your project and ask it to list the skills it knows. Confirm the Superpowers skills appear by name.
3. Test one skill on a safe, non-critical file before using it on production code. Check that the output matches what the skill description promised.
4. Review the skill's source instructions if anything looks unexpected. The skill is plain text; reading it tells you exactly what Claude Code is being asked to do.

How do you review a skill's instructions?

Before using any skill on real work, read what it instructs Claude Code to do. Open the skill file or the CLAUDE.md entry that defines it. Look for scope assumptions, file path patterns, or destructive operations. A skill written for one project structure may behave unexpectedly on yours.

Pay attention to any git or file operations in the instructions. A skill that commits, pushes, or deletes files should be tested in an isolated working copy first. The Claude Code sandbox guide covers running Claude Code in an environment where mistakes are contained.

What should you adapt from the default skills?

Default skills are generic. They do not know your project's conventions, your team's naming rules, or which files are off-limits. The most useful version of a skill for your project is usually one you have modified to match your specific context.

• Add your project's naming conventions so generated code matches existing style.
• Restrict the file scope to the directories that skill should touch.
• Include the acceptance criteria for the task the skill helps with, so Claude Code knows what done looks like.
• Add a reminder to save progress to fenbs before stopping, so the work from each skill run is captured.

How do you save what the plugin teaches you?

Using a skill on a real task often surfaces project-specific lessons: edge cases the default skill missed, a naming convention it got wrong, or a sequence of steps that works better than what the skill prescribes. Those lessons are worth saving, because the next session using the same skill should start from what you learned rather than from the generic default.

A fenbs lessons record captures what happened, what you learned, and what to do differently. The next session can read those lessons alongside the skill, so it does not repeat a mistake the previous one already caught.

How to do this with fenbs

1. Create a free account and add the project you are using Superpowers on.
2. Add the skill names you are using and any adapted instructions to fenbs as a Skills and prompts entry. This makes the right variant available to any connected assistant.
3. Connect Claude Code to fenbs from Integrations and ask it to read the project context before invoking a skill.
4. After a skill run, record any lesson — a missed edge case, a convention the skill got wrong — as a fenbs lesson linked to the task.
5. Before stopping, ask Claude Code to save task progress and Where we left off so the next session knows where the skill got to.

fenbs does not install or run Superpowers skills. It holds the record of what each run produced and what to do differently next time. For understanding what Claude Code skills are and how they differ from plugins and subagents, the plugins vs skills guide covers those distinctions.