agentleFS
KPISTOLASKPISTOLAS/claude-skills/skills/01-themeliodi/using-superpowers/SKILL.md

using-superpowers

Skill0 starsChanged 21 days agoLicence not identifiedView on GitHub

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

180 other projects use a version of this, 147 of them edited; 114 of 139 edited versions we compared changed its rules; 6 new projects in the last 4 weeks, against 9 the 4 before.

How people change it

114 of 139 edited versions changed its rules, and some changes recur.

Of the 139 edited versions we compared: 25 keep every rule, 114 made changes of their own.

Rules people drop

  1. If your harness appears here, read its reference file for special instructions:dropped by 111 of 114
  2. Before entering plan mode: if you haven't already brainstormed, invoke the brainstorming skill first.dropped by 102 of 114
  3. When multiple skills apply, process skills come first — they set the approach, then implementation skills (frontend-design, etc.) carry it out. …dropped by 102 of 114
  4. If you were dispatched as a subagent to execute a specific task, ignore this skill. </SUBAGENT-STOP>dropped by 45 of 114
  5. If you think there is even a 1% chance a skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.dropped by 5 of 114
  6. IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.dropped by 5 of 114

Rules people add

  1. When multiple skills could apply, use this order:added by 99 of 114
  2. In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.added by 86 of 114
  3. In other environments: Check your platform's documentation for how skills are loaded.added by 86 of 114
  4. If CLAUDE.md, GEMINI.md, or AGENTS.md says "don't use TDD" and a skill says "always use TDD," follow the user's instructions. The user is in control.added by 57 of 114
  5. In Copilot CLI: Use the skill tool. Skills are auto-discovered from installed plugins. The skill tool works the same as Claude Code's Skill tool.added by 39 of 114
  6. A rule we can't quote: its licence doesn't allow itadded by 3 of 114
  7. A rule we can't quote: its licence doesn't allow itadded by 3 of 114
  8. A rule we can't quote: its licence doesn't allow itadded by 3 of 114

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 6 new projects took it in the last 4 weeks, 0.7× the 4 weeks before.

Week of Sep 20: 1 new projectWeek of Sep 27: 3 new projectsWeek of Oct 4: 3 new projectsWeek of Oct 11: 2 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 3 new projectsWeek of Nov 1: 1 new projectWeek of Nov 8: 1 new project
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 19 projects that use this

  • kntismSkill

    condition-based-waiting

    Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

    Also in 3 projects that use this

  • frankxaiSkill

    defense-in-depth

    Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

    Also in 3 projects that use this

  • MicrosoftSkill

    root-cause-tracing

    Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

    Also in 3 projects that use this

  • +3 more from Leodorareluctant259

The file

We split this skill into the rules it gives an agent

6 rules. 3 are common, 3 are distinctive, and 0 are very specific to this project.

  • 3

    Common

    Most of the 152 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 152 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.