According to AlphaMoat, as of 2026-10, Superpowers Mode has 6,719 downloads and 8 stars — ranked by downloads #4,241 among 10,914 AI skills in this ranking, and #357 of 1,069 in Development.
The list defaults to total downloads and can also be sorted by stars; detail-page rankings use total downloads.
| Platform | Downloads | Stars | Comments |
|---|---|---|---|
| ClawHub ↗ | 5.3K | 6 | - |
| SkillHub ↗ | 6.7K | 8 | — |
Platforms count differently and update at different times.
Mode state is tracked in memory/superpowers-mode.md (enabled/updatedAt/notes). When enabled, coding requests follow a fixed order: quickly clarify objective and constraints, produce a short chunked spec, produce an implementation plan with small tasks, optionally run a 30-second mini risk review (how this can fail in production, the weakest dependency/state assumption, the regression signal and how to roll back fast), execute task-by-task (prefer test-first for risky changes), then verify against acceptance criteria and summarize the outcome and next step. Enable/disable/status phrases — including enable superpowers, superpowers off, and bilingual variants — are each confirmed with one short message. Red-flag self-checks catch thoughts like shipping non-trivial changes without a plan, deferring tests on risky edits, assuming rollback is unnecessary before touching config/auth/cron/system files, or calling something done without explicit verification. Guardrails: the workflow is not forced on non-coding chat; if the user asks for speed (just do it), it skips to a minimal plan and executes; updates stay concise to avoid process spam.
Profile published 2026-10-27
Generated from the skill’s documentation as examples; not results of actual runs.
The counting method changed in 2026-09: skills with the same name are now counted separately by author, and the full catalog is covered. Dashed lines show months before the change; they are not compared with later months, and no growth is computed across the change.
| Month | Downloads | MoM | Stars |
|---|---|---|---|
| 2026-10 | 6.7K | — | 8 |
| 2026-09 | 5.3K | — | 8 |
| 2026-08 | 5.0K | +4.3% | 8 |
| 2026-07 | 4.8K | +14.6% | 8 |
| 2026-06 | 4.2K | +3.4% | 6 |
| 2026-05 | 4.1K | — | 8 |
| 2026-03 | 2.7K | — | 4 |
The author’s original file, shown as plain text without edits or review by AlphaMoat. Links are not clickable; check commands before running them. Fetched 2026-10-23.
--- name: superpowers-mode description: Enable or disable a strict engineering workflow inspired by obra/superpowers when the user explicitly asks (e.g., "включи superpowers", "disable superpowers"). When enabled and the task is coding/build/debug, enforce: clarify goal, write spec, write plan, execute in small steps (prefer TDD), then review/finish. Use this skill only for coding workflows, not general chat. --- # Superpowers Mode (On-demand) Use this only when the user explicitly asks to enable/disable this mode, or when mode is already enabled for coding tasks. ## State file
Track mode in: `memory/superpowers-mode.md` Format: ```md enabled: true|false updatedAt: <ISO> notes: <optional> ``` ## Commands - Enable phrases: `включи superpowers`, `enable superpowers`, `superpowers on` - Write `enabled: true` to the state file. - Confirm in 1 short message. - Disable phrases: `выключи superpowers`, `disable superpowers`, `superpowers off` - Write `enabled: false`. - Confirm in 1 short message. - Status phrases: `статус superpowers`, `superpowers status` - Read state and report enabled/disabled. ## Workflow when enabled (coding tasks only) For coding/build/debug requests, follow this order: 1. Clarify objective and constraints quickly. 2. Produce a short spec (chunked, easy to review). 3. Produce an implementation plan with small tasks. 4. (Optional, 30 sec) Run a mini risk review: - How can this fail in production? - What is the weakest dependency/state assumption? - What signal will show regression + how to rollback fast? 5. Execute task-by-task (prefer test-first for risky changes). 6. Verify against acceptance criteria, then summarize outcome + next step. Use templates from `references/` when useful. ## Red flags (quick self-check) If you notice these thoughts, slow down and apply the workflow: - "Сейчас быстро вкачу без плана" for non-trivial changes. - "И так понятно, тесты потом" on risky edits. - "Откат не нужен" before touching config/auth/cron/system files. - "Похоже работает" without explicit verification. ## Guardrails - Do not force this workflow for non-coding chat. - If user asks for speed (`quick`, `без плана`, `just do it`), skip to minimal plan and execute. - Keep updates concise; avoid process spam.
【全栈能力】编程大神.Skill:面向复杂真实项目的高阶全栈编程助手。不止生成代码,而是从一句目标接手陌生代码库,拆解需求、补齐实现、追到根因、完成重构、联调前后端,并把结果推进到能运行、能验证、能交付。覆盖 Web、后端、脚本、iOS、安卓、鸿蒙 ArkUI、微信小程序及其他技术栈,支持中英文工程、疑难 Bug、跨模块任务和长任务续做;用构建、日志、真实入口、设备或接口证据说明结果。仅问概念时直接回答,要求落地时持续推进到验收或明确阻塞。
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
编程专家.Skill P8级编程助手,25年实战经验技能Skill,全栈:Java/Php网站/软件项目、API设计、Bug诊断、代码生成、代码审查、重构、测试用例、性能基准、技术选型、文档生成、任务拆解、Spec驱动、Karpathy规范、CMS二次开发、前端设计、MySQL/Mariadb、项目知识图谱,以及工程纪律层(根因调试硬闭环、阶段导航、事故复盘/SLO、威胁建模/供应链安全、生产就绪/渐进式发布、AI编码治理、面向Agent代码可读性、LLM应用安全)。支持 @标识 显式调用跳过路由。
工程专题、鸿蒙与微信小程序开发的集成派生版
编程专家 Pro:融合编程专家 2.0.3 工程专题与编程大神的鸿蒙 ArkTS/ArkUI、微信小程序和小游戏开发资料。用于项目实现、根因调试、审查、重构、测试、架构性能分析及多端开发验证。支持自然语言和 @专题标识,按任务读取包内知识;只问概念时直接回答。
适用场景:全栈编程助手。接到需求先读现有代码和约束,再动手:Java/PHP 开发、接口设计、缺陷定位、代码评审、重构、测试用例、性能排查、技术选型与文档产出,也做 CMS 二次开发、前端页面和 MySQL 调优。每次改动先给方案和影响范围,改完必须跑验证,交付附交接说明。适合要把代码真正跑通、而不是只要片段的场景。写完代码常要配套的造价、法律、工程文档,站内已有现成技能,用「查找技能」按需求找即可。
A skill for working with GitHub through the gh CLI: pull request checks, workflow runs, and API queries.
Data as of 2026-10. Downloads and stars are aggregated monthly from public skill registries (ClawHub, SkillHub). See data methodology.