Skip to content
Agent Orchestration
Skill

/superpowers

Use when a task in Cursor may benefit from a structured workflow and one or more companion skills from this pack, such as brainstorming, feature development, design, review, debugging, planning, or verification.

BOOST
From plugin
flowpilot
13620 skills
Install
$ npx -y skills add 6BNBN/FlowPilot --skill superpowers --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/superpowers

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when a task in Cursor may benefit from a structured workflow and one or more companion skills from this pack, such as brainstorming, feature development, design, review, debugging, planning, or verification.

SKILL.md

superpowers.SKILL.md
name: superpowers
description: Use when a task in Cursor may benefit from a structured workflow and one or more companion skills from this pack, such as brainstorming, feature development, design, review, debugging, planning, or verification.

Superpowers

Purpose

This is the entry skill for the pack. Use it to choose the right companion workflow before doing substantial work.

Skill Selection Guide

  • Use `brainstorming` when requirements are fuzzy or design decisions matter.
  • Use `feature-dev` when building a new feature or changing behavior in a structured way.
  • Use `frontend-design` when creating or redesigning UI with a strong visual direction.
  • Use `systematic-debugging` when investigating bugs, failing tests, or unexpected behavior.
  • Use `code-review` when reviewing local files, diffs, or a PR for real issues.
  • Use `writing-plans` when the user wants a written implementation plan.
  • Use `executing-plans` when there is already a plan and you should execute it in batches.
  • Use `verification-before-completion` before claiming work is complete or passing.

Operating Rules

  • Pick one primary workflow skill for the task.
  • Combine skills only when the combination is genuinely useful.
  • Reuse existing project patterns before introducing new abstractions.
  • Ask concise clarifying questions before editing when the request is underspecified.
  • Keep the user informed about the chosen workflow when the work is substantial.

Avoid

  • Mentioning vendor-specific runtimes or internal tooling.
  • Forcing the same workflow onto every task.
  • Skipping verification before making completion claims.
Read more
Ships withflowpilot

一个文件,一句开发需求,全自动开发。 把 flow.js 丢进任何项目,打开你选择的客户端(Claude Code / Codex / Cursor / snow-cli 等)描述你要做什么,然后去喝杯咖啡。 回来的时候,代码写好了,测试跑完了,git 也提交了。 新增说明:现已兼容 Claude Code、Codex、Cursor、snow-cli 和其他客户端;init 时可直接选择目标客户端并生成对应的 instruction file / 配置。 新增说明:内置 instruction file /

Get the whole plugin

Other skills on flowpilot.