agy-superpowers 5.0.9 → 5.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -1,5 +1,8 @@
1
1
  # antigravity-superpowers
2
2
 
3
+ [![npm version](https://img.shields.io/npm/v/agy-superpowers.svg)](https://www.npmjs.com/package/agy-superpowers)
4
+ [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
5
+
3
6
  > **Superpowers for [Google Antigravity](https://antigravity.google)** — a complete development workflow powered by composable skills, workflows, and rules.
4
7
 
5
8
 
@@ -39,36 +42,31 @@ agy-superpowers init
39
42
  ## What's Inside
40
43
 
41
44
  ```
42
- antigravity-superpowers/
43
- ├── .agent/
44
- ├── rules/
45
- │ │ └── superpowers.md # Always-on rule: agent checks skills before acting
46
- │ ├── skills/ # Symlinks → superpowers/skills/*
47
- ├── brainstorming/
48
- ├── writing-plans/
49
- ├── executing-plans/
50
- ├── subagent-driven-development/
51
- ├── test-driven-development/
52
- ├── systematic-debugging/
53
- ├── verification-before-completion/
54
- │ ├── requesting-code-review/
55
- │ │ ├── receiving-code-review/
56
- ├── using-git-worktrees/
57
- ├── finishing-a-development-branch/
58
- ├── dispatching-parallel-agents/
59
- ├── writing-skills/
60
- │ └── using-superpowers/
61
- │ ├── workflows/
62
- │ ├── brainstorm.md # /brainstorm
63
- │ │ ├── write-plan.md # /write-plan
64
- │ ├── execute-plan.md # /execute-plan
65
- │ │ ├── code-review.md # /code-review
66
- │ │ ├── debug.md # /debug
67
- │ │ └── update-superpowers.md # /update-superpowers
68
- │ └── .shared/
69
- │ └── update-superpowers.sh # Shell script for version management
70
- └── superpowers/ # Upstream source (git-managed)
71
- └── skills/ # All skill SKILL.md files live here
45
+ .agent/
46
+ ├── rules/
47
+ └── superpowers.md # Always-on rule: agent checks skills before acting
48
+ ├── skills/ # 44 skills (patched from upstream)
49
+ │ ├── brainstorming/
50
+ │ ├── writing-plans/
51
+ │ ├── executing-plans/
52
+ │ ├── backend-developer/
53
+ │ ├── frontend-developer/
54
+ │ ├── mobile-developer/
55
+ │ ├── growth-hacker/
56
+ │ ├── monetization-strategist/
57
+ └── ... # + 36 more skills
58
+ ├── workflows/
59
+ │ ├── brainstorm.md # /brainstorm
60
+ │ ├── write-plan.md # /write-plan
61
+ │ ├── execute-plan.md # /execute-plan
62
+ │ ├── code-review.md # /code-review
63
+ ├── debug.md # /debug
64
+ │ ├── publish.md # /publish
65
+ └── update-superpowers.md # /update-superpowers
66
+ ├── patches/
67
+ └── skills-patches.md # AI-driven skill patches (see below)
68
+ └── .shared/
69
+ └── update-superpowers.sh # Shell script for version management
72
70
  ```
73
71
 
74
72
  ---
@@ -91,25 +89,75 @@ antigravity-superpowers/
91
89
  | 4 | `/code-review` | Pre-review checklist, severity-based issue reporting |
92
90
  | 5 | _(auto)_ | `finishing-a-development-branch` — merge / PR / discard |
93
91
 
92
+ ### Additional Workflows
93
+
94
+ | Workflow | What happens |
95
+ | --------------------- | ------------------------------------------------------------ |
96
+ | `/debug` | Systematic 4-phase debugging process |
97
+ | `/publish` | Publish to npm with version bump, git tag, and push |
98
+ | `/update-superpowers` | Pull latest upstream release, re-sync skills, AI-rewrite rules |
99
+
100
+ ---
101
+
102
+ ## AI-Driven Skill Patching
103
+
104
+ Skills are sourced from upstream Superpowers but automatically patched to be Antigravity-native. The patching system uses a human-readable spec at `.agent/patches/skills-patches.md` which the AI interprets semantically — making patches resilient to upstream changes.
105
+
106
+ When you run `/update-superpowers`, skills are:
107
+ 1. Copied fresh from `superpowers/skills/`
108
+ 2. Patched via AI to remove non-Antigravity references
109
+ 3. Ready to use immediately
110
+
94
111
  ---
95
112
 
96
113
  ## Skills Reference
97
114
 
98
- | Skill | Triggers automatically when... |
99
- | -------------------------------- | -------------------------------------------------------------------- |
100
- | `brainstorming` | You're adding a feature, building a component, or modifying behavior |
101
- | `writing-plans` | Design is approved breaking work into tasks |
102
- | `executing-plans` | Running a plan step-by-step with checkpoints |
103
- | `subagent-driven-development` | Dispatching subagents per task with two-stage review |
104
- | `test-driven-development` | During ALL implementation (RED GREEN REFACTOR) |
105
- | `systematic-debugging` | Debugging any issue |
106
- | `verification-before-completion` | Before declaring a fix or task done |
107
- | `requesting-code-review` | Before submitting code for review |
108
- | `receiving-code-review` | Responding to review feedback |
109
- | `using-git-worktrees` | Starting work on a new isolated branch |
110
- | `finishing-a-development-branch` | When tasks are complete |
111
- | `dispatching-parallel-agents` | Running concurrent subagent workflows |
112
- | `writing-skills` | Creating a new skill |
115
+ | Skill | Triggers automatically when... |
116
+ | ----- | ------------------------------ |
117
+ | `api-design` | Designing REST or GraphQL APIs, versioning, rate limiting, pagination, or API docs |
118
+ | `app-store-optimizer` | Working on App Store / Google Play listing optimization, keyword strategy, or A/B testing |
119
+ | `auth-and-identity` | Implementing authentication, authorization, SSO/SAML/OIDC, session management, or RBAC |
120
+ | `backend-developer` | Designing APIs, server-side logic, database schemas, or reviewing backend code |
121
+ | `brainstorming` | Adding a feature, building a component, or modifying behavior |
122
+ | `community-manager` | Building and managing communities on Discord, Reddit, Slack, or social platforms |
123
+ | `content-marketer` | Planning content strategy, SEO content, social media, or email newsletters |
124
+ | `conversion-optimizer` | Optimizing landing pages, trial-to-paid funnels, paywall design, or onboarding flows |
125
+ | `copywriter` | Writing landing page copy, app store descriptions, email sequences, or user-facing text |
126
+ | `cto-architect` | Making system design decisions, managing tech debt, planning for scale |
127
+ | `customer-success-manager` | Managing user support, feedback loops, NPS/CSAT tracking, or handling churn |
128
+ | `data-analyst` | Setting up metrics, analyzing funnels, cohort analysis, dashboards, or A/B test results |
129
+ | `devops-engineer` | Working on CI/CD pipelines, infrastructure, deployment, monitoring, or reliability |
130
+ | `dispatching-parallel-agents` | Facing 2+ independent tasks that can run without shared state |
131
+ | `email-infrastructure` | Setting up transactional email, deliverability, SPF/DKIM/DMARC, or email templates |
132
+ | `executing-plans` | Running a plan step-by-step with checkpoints |
133
+ | `finishing-a-development-branch` | Implementation is complete and you need to merge / PR / discard |
134
+ | `frontend-developer` | Building web UI, component architecture, or reviewing frontend code |
135
+ | `game-design` | Designing game mechanics, core loops, progression, monetization, or difficulty curves |
136
+ | `game-developer` | Working on game app features, reviewing game code, or game architecture decisions |
137
+ | `growth-hacker` | Planning user acquisition, viral loops, activation funnels, or growth experiments |
138
+ | `i18n-localization` | Planning i18n architecture, localizing for new markets, or managing translations |
139
+ | `influencer-marketer` | Planning UGC campaigns, creator partnerships, TikTok/YouTube/Instagram marketing |
140
+ | `mobile-developer` | Working on mobile app features, reviewing mobile code, or mobile architecture |
141
+ | `monetization-strategist` | Designing pricing models, freemium strategy, IAP, or modeling unit economics |
142
+ | `paid-acquisition-specialist` | Running Meta Ads, Google Ads, Apple Search Ads, or any paid acquisition channel |
143
+ | `product-manager` | Defining requirements, prioritizing features, planning roadmaps, or validating problems |
144
+ | `real-time-features` | Implementing WebSockets, SSE, live collaboration, or real-time notifications |
145
+ | `receiving-code-review` | Receiving code review feedback, before implementing suggestions |
146
+ | `requesting-code-review` | Completing tasks or before merging to verify work meets requirements |
147
+ | `retention-specialist` | Improving user retention, reducing churn, analyzing engagement, or re-engagement |
148
+ | `saas-architect` | Designing multi-tenant SaaS architecture, tenant isolation, or data models |
149
+ | `security-engineer` | Reviewing app security, handling user data, ensuring GDPR/App Store compliance |
150
+ | `seo-specialist` | Working on technical SEO, keyword research, on-page optimization, or backlink strategy |
151
+ | `subagent-driven-development` | Executing implementation plans with independent tasks in the current session |
152
+ | `subscription-billing` | Integrating subscription billing, Stripe webhooks, trial logic, or dunning flows |
153
+ | `systematic-debugging` | Debugging any issue |
154
+ | `test-driven-development` | Implementing any feature or bugfix |
155
+ | `using-git-worktrees` | Starting work on an isolated branch |
156
+ | `using-superpowers` | Starting any conversation — checks for relevant skills |
157
+ | `ux-designer` | Designing UI, wireframes, user research, or information architecture |
158
+ | `verification-before-completion` | Before declaring a fix or task done |
159
+ | `writing-plans` | Design is approved — breaking work into tasks |
160
+ | `writing-skills` | Creating or editing a skill |
113
161
 
114
162
  ---
115
163
 
@@ -124,9 +172,10 @@ Upstream Superpowers releases are tracked automatically. To update:
124
172
  This workflow will:
125
173
 
126
174
  1. Pull the latest Superpowers release from GitHub
127
- 2. Re-sync all skill symlinks
175
+ 2. Copy fresh skills from upstream
128
176
  3. AI-rewrite any changed workflows and rules to stay Antigravity-compatible
129
- 4. Commit all changes with a versioned commit message
177
+ 4. Apply skill patches via `.agent/patches/skills-patches.md`
178
+ 5. Commit all changes with a versioned commit message
130
179
 
131
180
  ---
132
181
 
@@ -157,25 +206,11 @@ This file is preserved across `/update-superpowers` runs.
157
206
 
158
207
  ### Using This Repo in Your Project
159
208
 
160
- Copy the `.agent/` folder into your project root:
161
-
162
- ```bash
163
- cp -r /path/to/antigravity-superpowers/.agent /your/project/
164
- ```
165
-
166
- Or clone this repo as a submodule and symlink `.agent/`:
167
-
168
- ```bash
169
- git submodule add https://github.com/<your-username>/antigravity-superpowers .antigravity-superpowers
170
- ln -s .antigravity-superpowers/.agent .agent
171
- ```
172
-
173
- ### Starting Fresh
209
+ The recommended way is `npx` (see Quick Start above). Alternatively, clone and copy:
174
210
 
175
211
  ```bash
176
- git clone https://github.com/<your-username>/antigravity-superpowers
177
- cd antigravity-superpowers
178
- # Open with Antigravity — the agent will detect .agent/ automatically
212
+ git clone https://github.com/bonnguyenitc/antigravity-superpowers
213
+ cp -r antigravity-superpowers/.agent /your/project/
179
214
  ```
180
215
 
181
216
  ---
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "agy-superpowers",
3
- "version": "5.0.9",
3
+ "version": "5.1.0",
4
4
  "description": "Superpowers skills library for Google Antigravity agent — scaffold .agent/ with one command",
5
5
  "type": "module",
6
6
  "bin": {
@@ -25,9 +25,10 @@ Load plan, review critically, execute all tasks, report when complete.
25
25
 
26
26
  For each task:
27
27
  1. Mark as in_progress
28
- 2. Follow each step exactly (plan has bite-sized steps)
29
- 3. Run verifications as specified
30
- 4. Mark as completed
28
+ 2. **Check for domain skills** — before writing any code, identify which domain skill applies to this task's context (e.g. `mobile-developer` for React Native work, `backend-developer` for API work, `frontend-developer` for web UI). Read only the relevant SKILL.md (not all references); load specific references on demand as the task requires them.
29
+ 3. Follow each step exactly (plan has bite-sized steps)
30
+ 4. Run verifications as specified
31
+ 5. Mark as completed
31
32
 
32
33
  ### Step 3: Complete Development
33
34
 
@@ -276,6 +276,7 @@ Done!
276
276
 
277
277
  **Subagents should use:**
278
278
  - **superpowers:test-driven-development** - Subagents follow TDD for each task
279
+ - **Domain skills matching the task context** - e.g. `mobile-developer` for React Native work, `backend-developer` for API work, `frontend-developer` for web UI. Include only the relevant SKILL.md in the implementer prompt context; load specific references on demand as the task requires them.
279
280
 
280
281
  **Alternative workflow:**
281
282
  - **superpowers:executing-plans** - Use for parallel session instead of same-session execution