agy-superpowers 5.0.9 → 5.1.1

package/README.md

@@ -1,5 +1,8 @@
 # antigravity-superpowers
 
+[![npm version](https://img.shields.io/npm/v/agy-superpowers.svg)](https://www.npmjs.com/package/agy-superpowers)
+[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](./LICENSE)
+
 > **Superpowers for [Google Antigravity](https://antigravity.google)** — a complete development workflow powered by composable skills, workflows, and rules.
 
 
@@ -39,36 +42,31 @@ agy-superpowers init
 ## What's Inside
 
 ```
-antigravity-superpowers/
-├── .agent/
-│   ├── rules/
-│   │   └── superpowers.md        # Always-on rule: agent checks skills before acting
-│   ├── skills/                   # Symlinks → superpowers/skills/*
-│   │   ├── brainstorming/
-│   │   ├── writing-plans/
-│   │   ├── executing-plans/
-│   │   ├── subagent-driven-development/
-│   │   ├── test-driven-development/
-│   │   ├── systematic-debugging/
-│   │   ├── verification-before-completion/
-│   │   ├── requesting-code-review/
-│   │   ├── receiving-code-review/
-│   │   ├── using-git-worktrees/
-│   │   ├── finishing-a-development-branch/
-│   │   ├── dispatching-parallel-agents/
-│   │   ├── writing-skills/
-│   │   └── using-superpowers/
-│   ├── workflows/
-│   │   ├── brainstorm.md         # /brainstorm
-│   │   ├── write-plan.md         # /write-plan
-│   │   ├── execute-plan.md       # /execute-plan
-│   │   ├── code-review.md        # /code-review
-│   │   ├── debug.md              # /debug
-│   │   └── update-superpowers.md # /update-superpowers
-│   └── .shared/
-│       └── update-superpowers.sh # Shell script for version management
-└── superpowers/                  # Upstream source (git-managed)
-    └── skills/                   # All skill SKILL.md files live here
+.agent/
+├── rules/
+│   └── superpowers.md          # Always-on rule: agent checks skills before acting
+├── skills/                     # 56 skills (patched from upstream + 12 indie hacker skills)
+│   ├── brainstorming/
+│   ├── writing-plans/
+│   ├── executing-plans/
+│   ├── backend-developer/
+│   ├── frontend-developer/
+│   ├── mobile-developer/
+│   ├── growth-hacker/
+│   ├── monetization-strategist/
+│   └── ...                     # + 48 more skills
+├── workflows/
+│   ├── brainstorm.md           # /brainstorm
+│   ├── write-plan.md           # /write-plan
+│   ├── execute-plan.md         # /execute-plan
+│   ├── code-review.md          # /code-review
+│   ├── debug.md                # /debug
+│   ├── publish.md              # /publish
+│   └── update-superpowers.md   # /update-superpowers
+├── patches/
+│   └── skills-patches.md       # AI-driven skill patches (see below)
+└── .shared/
+    └── update-superpowers.sh   # Shell script for version management
 ```
 
 ---
@@ -91,25 +89,298 @@ antigravity-superpowers/
 | 4    | `/code-review`  | Pre-review checklist, severity-based issue reporting           |
 | 5    | _(auto)_        | `finishing-a-development-branch` — merge / PR / discard        |
 
+### Additional Workflows
+
+| Workflow              | What happens                                                 |
+| --------------------- | ------------------------------------------------------------ |
+| `/debug`              | Systematic 4-phase debugging process                         |
+| `/publish`            | Publish to npm with version bump, git tag, and push          |
+| `/update-superpowers` | Pull latest upstream release, re-sync skills, AI-rewrite rules |
+
+---
+
+## Usage Guide
+
+### Getting Started in 5 Minutes
+
+**How it works:** Superpowers gives your agent 56 specialized skills. You don't need to remember or invoke them — the agent **automatically reads and selects the right skill** based on what you ask. Just describe what you need in natural language.
+
+#### Your First Feature: A Walkthrough
+
+Let's say you want to add dark mode to your React app. Here's what the full cycle looks like:
+
+| Step | You type | What happens |
+| ---- | -------- | ------------ |
+| 1 | `/brainstorm add dark mode to my React app` | Agent asks clarifying questions, explores approaches, and produces a design spec |
+| 2 | `/write-plan` | Spec gets converted into a task list with exact file paths and acceptance criteria |
+| 3 | `/execute-plan` | Agent implements tasks one by one, pausing for your review at checkpoints |
+| 4 | `/code-review` | Agent reviews the completed code against the plan, reports issues by severity |
+| 5 | _(automatic)_ | Agent offers to merge, create a PR, or discard the branch |
+
+That's it. Five steps from idea to merge-ready code.
+
+#### Quick Reference: The 5 Commands You'll Use Most
+
+| Command | What it does | Example |
+| ------- | ------------ | ------- |
+| `/brainstorm` | Turn a rough idea into a validated design spec | `/brainstorm add user onboarding flow` |
+| `/write-plan` | Break an approved spec into bite-sized tasks | `/write-plan` (after brainstorm) |
+| `/execute-plan` | Execute tasks with human review checkpoints | `/execute-plan` (after write-plan) |
+| `/code-review` | Review completed work before merging | `/code-review` |
+| `/debug` | Systematic 4-phase debugging for any issue | `/debug users can't log in on Safari` |
+
+---
+
+### Beyond Code — Skills That Work For You
+
+The agent doesn't just write code — it has specialized knowledge in marketing, pricing, security, legal, and more. When you mention a topic, the relevant skill activates automatically.
+
+#### 🔧 Development Workflow
+
+These are triggered via slash commands or activate automatically during the dev loop:
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `brainstorming` | Adding a feature, building a component, or modifying behavior |
+| `writing-plans` | Design is approved — breaking work into tasks |
+| `executing-plans` | Running a plan step-by-step with checkpoints |
+| `test-driven-development` | Implementing any feature or bugfix |
+| `systematic-debugging` | Debugging any issue |
+| `verification-before-completion` | Before declaring a fix or task done |
+| `requesting-code-review` | Completing tasks or before merging |
+| `receiving-code-review` | Receiving code review feedback |
+| `finishing-a-development-branch` | Implementation is complete — merge / PR / discard |
+| `using-git-worktrees` | Starting work on an isolated branch |
+| `dispatching-parallel-agents` | 2+ independent tasks that can run in parallel |
+| `subagent-driven-development` | Executing plan tasks in the current session |
+
+#### 💻 Technical Skills
+
+Activate when you work on specific technical domains:
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `backend-developer` | Designing APIs, server-side logic, database schemas |
+| `frontend-developer` | Building web UI, component architecture |
+| `mobile-developer` | Mobile app features, React Native / Flutter / iOS / Android |
+| `game-developer` | Game app features, game code, game architecture |
+| `api-design` | REST or GraphQL APIs, versioning, rate limiting, pagination |
+| `real-time-features` | WebSockets, SSE, live collaboration, real-time notifications |
+| `auth-and-identity` | Authentication, authorization, SSO, RBAC |
+| `devops-engineer` | CI/CD, infrastructure, deployment, monitoring |
+| `security-engineer` | App security, user data handling, GDPR/App Store compliance |
+| `email-infrastructure` | Transactional email, deliverability, SPF/DKIM/DMARC |
+| `saas-architect` | Multi-tenant SaaS architecture, tenant isolation |
+| `chrome-extension-developer` | Chrome extensions, browser-based tools |
+
+> **Example prompt:** _"Design a REST API for user management with rate limiting and pagination"_ → activates `api-design` + `backend-developer`
+
+#### 🎨 Product & Design
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `product-manager` | Defining requirements, prioritizing features, planning roadmaps |
+| `ux-designer` | Designing UI, wireframes, user research, information architecture |
+| `cto-architect` | System design decisions, tech debt, planning for scale |
+| `i18n-localization` | Internationalization, localizing for new markets |
+| `game-design` | Game mechanics, core loops, progression, difficulty curves |
+
+> **Example prompt:** _"Help me prioritize features for the next sprint based on user feedback"_ → activates `product-manager`
+
+#### 📈 Marketing & Growth
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `growth-hacker` | User acquisition, viral loops, activation funnels |
+| `content-marketer` | Content strategy, SEO content, social media, newsletters |
+| `seo-specialist` | Technical SEO, keyword research, on-page optimization |
+| `conversion-optimizer` | Landing pages, trial-to-paid funnels, paywall design |
+| `copywriter` | Landing page copy, app store descriptions, email sequences |
+| `community-manager` | Discord, Reddit, Slack communities, engagement strategy |
+| `influencer-marketer` | UGC campaigns, creator partnerships, TikTok/YouTube marketing |
+| `paid-acquisition-specialist` | Meta Ads, Google Ads, Apple Search Ads, ROAS optimization |
+| `launch-strategist` | Product launch, go-to-market, pre-launch campaigns |
+| `landing-page-builder` | Landing pages, waitlist pages, marketing sites |
+| `app-store-optimizer` | App Store / Google Play listing optimization, keyword strategy |
+
+> **Example prompt:** _"Write an ASO-optimized App Store description for my meditation app"_ → activates `app-store-optimizer` + `copywriter`
+
+#### 💰 Revenue & Operations
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `monetization-strategist` | Pricing models, freemium strategy, IAP, unit economics |
+| `pricing-psychologist` | Pricing, paywalls, free-to-paid conversion |
+| `subscription-billing` | Stripe integration, webhooks, trial logic, dunning flows |
+| `bootstrapper-finance` | MRR tracking, runway calculation, financial decisions |
+| `solo-founder-ops` | Time management, feature prioritization, running multiple products |
+| `analytics-setup` | Analytics, tracking tools, metrics dashboards |
+| `customer-success-manager` | User support, feedback loops, NPS/CSAT, churn |
+| `data-analyst` | Metrics frameworks, funnel analysis, cohort analysis, A/B tests |
+| `indie-legal` | Privacy policies, terms of service, GDPR/CCPA |
+
+> **Example prompt:** _"Should I charge $9/mo or $29/mo for my SaaS? Here's my target audience..."_ → activates `pricing-psychologist` + `monetization-strategist`
+
+#### 🚀 Validate & Scale
+
+| Skill | When it activates |
+| ----- | ----------------- |
+| `idea-validator` | Evaluating a product idea, assessing market fit before building |
+| `market-researcher` | Finding a niche, analyzing market size, customer discovery |
+| `ai-integrated-product` | Integrating AI/LLM capabilities, building AI-powered features |
+| `micro-saas-builder` | Building a micro-SaaS, choosing a niche SaaS idea |
+
+> **Example prompt:** _"I have an idea for an AI writing tool — is it worth building?"_ → activates `idea-validator` + `market-researcher`
+
+---
+
+### Power User Tips
+
+#### When to `/brainstorm` vs Just Ask
+
+| Situation | What to do |
+| --------- | ---------- |
+| Multi-file feature, new component, architectural change | `/brainstorm` → full design cycle |
+| Quick fix, rename, typo, single-line change | Just ask directly |
+| Knowledge question ("What's the best auth library?") | Just ask directly |
+| Not sure about scope | Start with `/brainstorm` — it's safe to exit early |
+
+**Rule of thumb:** if it touches more than one file or involves design tradeoffs → `/brainstorm`.
+
+#### How to Write Better Prompts
+
+- **Provide context** — mention your tech stack, project name, and constraints: _"In my Next.js app with Supabase auth..."_
+- **State goals, not solutions** — _"Users drop off during signup"_ gives the agent room to find the best fix, vs _"Add a progress bar to the signup form"_
+- **Mention specific domains** to activate the right skills — _"Review the **security** of my auth flow"_ triggers `security-engineer`, _"Optimize the **SEO** for my landing page"_ triggers `seo-specialist`
+
+#### Combining Workflows for Complex Projects
+
+**Full product launch cycle:**
+```
+/brainstorm → /write-plan → /execute-plan → /code-review
+    ↓ then in separate conversations:
+    "Write marketing copy for..." → copywriter skill
+    "Optimize my App Store listing..." → ASO skill
+    "Design a pricing strategy..." → pricing skill
+```
+
+**Idea → Validation → Build:**
+```
+"I have an idea for X, is it viable?" → idea-validator
+"Research the market for X" → market-researcher
+/brainstorm → /write-plan → /execute-plan → build it
+```
+
+**Debugging effectively:**
+```
+/debug → systematic investigation
+    ↓ if architectural issue found:
+/brainstorm → redesign the component
+```
+
+#### Configuration
+
+Per-project settings live in `.agent/config.yml`:
+
+- Set `auto_commit: false` when you want full control over your git history
+- This file is preserved across `/update-superpowers` runs — your settings won't be overwritten
+
+#### Common Pitfalls
+
+| ❌ Don't | ✅ Do instead |
+| -------- | ------------- |
+| Skip `/brainstorm` for large features | Always brainstorm features that touch multiple files |
+| Cram multiple goals into one prompt | One conversation = one clear objective |
+| Jump to `/execute-plan` without reviewing the spec | Review and approve the design spec before execution |
+| Skip `/code-review` before merging | Always review before merge — catch bugs early |
+| Assume the agent only writes code | Ask about pricing, marketing, legal — it has skills for those too |
+
+---
+
+## AI-Driven Skill Patching
+
+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.
+
+When you run `/update-superpowers`, skills are:
+1. Copied fresh from `superpowers/skills/`
+2. Patched via AI to remove non-Antigravity references
+3. Ready to use immediately
+
 ---
 
 ## Skills Reference
 
-| Skill                            | Triggers automatically when...                                       |
-| -------------------------------- | -------------------------------------------------------------------- |
-| `brainstorming`                  | You're adding a feature, building a component, or modifying behavior |
-| `writing-plans`                  | Design is approved — breaking work into tasks                        |
-| `executing-plans`                | Running a plan step-by-step with checkpoints                         |
-| `subagent-driven-development`    | Dispatching subagents per task with two-stage review                 |
-| `test-driven-development`        | During ALL implementation (RED → GREEN → REFACTOR)                   |
-| `systematic-debugging`           | Debugging any issue                                                  |
-| `verification-before-completion` | Before declaring a fix or task done                                  |
-| `requesting-code-review`         | Before submitting code for review                                    |
-| `receiving-code-review`          | Responding to review feedback                                        |
-| `using-git-worktrees`            | Starting work on a new isolated branch                               |
-| `finishing-a-development-branch` | When tasks are complete                                              |
-| `dispatching-parallel-agents`    | Running concurrent subagent workflows                                |
-| `writing-skills`                 | Creating a new skill                                                 |
+| Skill | Triggers automatically when... |
+| ----- | ------------------------------ |
+| `ai-integrated-product` | Integrating AI/LLM capabilities into a product, building AI-powered features |
+| `analytics-setup` | Setting up analytics, choosing tracking tools, or designing a metrics dashboard for an indie product |
+| `api-design` | Designing REST or GraphQL APIs, versioning, rate limiting, pagination, or API docs |
+| `app-store-optimizer` | Working on App Store / Google Play listing optimization, keyword strategy, or A/B testing |
+| `auth-and-identity` | Implementing authentication, authorization, SSO/SAML/OIDC, session management, or RBAC |
+| `backend-developer` | Designing APIs, server-side logic, database schemas, or reviewing backend code |
+| `bootstrapper-finance` | Tracking MRR, calculating runway, making financial decisions for a solo/bootstrapped business |
+| `brainstorming` | Adding a feature, building a component, or modifying behavior |
+| `chrome-extension-developer` | Building a Chrome extension, browser extension, or browser-based tool |
+| `community-manager` | Building and managing communities on Discord, Reddit, Slack, or social platforms |
+| `content-marketer` | Planning content strategy, SEO content, social media, or email newsletters |
+| `conversion-optimizer` | Optimizing landing pages, trial-to-paid funnels, paywall design, or onboarding flows |
+| `copywriter` | Writing landing page copy, app store descriptions, email sequences, or user-facing text |
+| `cto-architect` | Making system design decisions, managing tech debt, planning for scale |
+| `customer-success-manager` | Managing user support, feedback loops, NPS/CSAT tracking, or handling churn |
+| `data-analyst` | Setting up metrics, analyzing funnels, cohort analysis, dashboards, or A/B test results |
+| `devops-engineer` | Working on CI/CD pipelines, infrastructure, deployment, monitoring, or reliability |
+| `dispatching-parallel-agents` | Facing 2+ independent tasks that can run without shared state |
+| `email-infrastructure` | Setting up transactional email, deliverability, SPF/DKIM/DMARC, or email templates |
+| `executing-plans` | Running a plan step-by-step with checkpoints |
+| `finishing-a-development-branch` | Implementation is complete and you need to merge / PR / discard |
+| `frontend-developer` | Building web UI, component architecture, or reviewing frontend code |
+| `game-design` | Designing game mechanics, core loops, progression, monetization, or difficulty curves |
+| `game-developer` | Working on game app features, reviewing game code, or game architecture decisions |
+| `growth-hacker` | Planning user acquisition, viral loops, activation funnels, or growth experiments |
+| `i18n-localization` | Planning i18n architecture, localizing for new markets, or managing translations |
+| `idea-validator` | Starting a new project, evaluating a product idea, or assessing market fit before building |
+| `indie-legal` | Creating privacy policies, terms of service, handling GDPR/CCPA basics, or understanding legal requirements |
+| `influencer-marketer` | Planning UGC campaigns, creator partnerships, TikTok/YouTube/Instagram marketing |
+| `landing-page-builder` | Creating a landing page, waitlist page, product page, or marketing site |
+| `launch-strategist` | Preparing to launch a product, planning go-to-market, or running a pre-launch campaign |
+| `market-researcher` | Finding a niche, analyzing market size, researching customer segments, or doing customer discovery |
+| `micro-saas-builder` | Building a micro-SaaS product, choosing a niche SaaS idea, or designing a small scalable SaaS |
+| `mobile-developer` | Working on mobile app features, reviewing mobile code, or mobile architecture |
+| `monetization-strategist` | Designing pricing models, freemium strategy, IAP, or modeling unit economics |
+| `paid-acquisition-specialist` | Running Meta Ads, Google Ads, Apple Search Ads, or any paid acquisition channel |
+| `pricing-psychologist` | Designing pricing, paywalls, free-to-paid conversion, or optimizing upgrade flows |
+| `product-manager` | Defining requirements, prioritizing features, planning roadmaps, or validating problems |
+| `real-time-features` | Implementing WebSockets, SSE, live collaboration, or real-time notifications |
+| `receiving-code-review` | Receiving code review feedback, before implementing suggestions |
+| `requesting-code-review` | Completing tasks or before merging to verify work meets requirements |
+| `retention-specialist` | Improving user retention, reducing churn, analyzing engagement, or re-engagement |
+| `saas-architect` | Designing multi-tenant SaaS architecture, tenant isolation, or data models |
+| `security-engineer` | Reviewing app security, handling user data, ensuring GDPR/App Store compliance |
+| `seo-specialist` | Working on technical SEO, keyword research, on-page optimization, or backlink strategy |
+| `solo-founder-ops` | Managing time, prioritizing features, or running multiple products as a solo founder |
+| `subagent-driven-development` | Executing implementation plans with independent tasks in the current session |
+| `subscription-billing` | Integrating subscription billing, Stripe webhooks, trial logic, or dunning flows |
+| `systematic-debugging` | Debugging any issue |
+| `test-driven-development` | Implementing any feature or bugfix |
+| `using-git-worktrees` | Starting work on an isolated branch |
+| `using-superpowers` | Starting any conversation — checks for relevant skills |
+| `ux-designer` | Designing UI, wireframes, user research, or information architecture |
+| `verification-before-completion` | Before declaring a fix or task done |
+| `writing-plans` | Design is approved — breaking work into tasks |
+| `writing-skills` | Creating or editing a skill |
+
+---
+
+
+### The Indie Hacker Journey
+
+Our 12 expansion skills comprehensively support the indie hacker roadmap:
+- **Validate:** `idea-validator`, `market-researcher`
+- **Build:** `chrome-extension-developer`
+- **Launch:** `launch-strategist`, `landing-page-builder`
+- **Revenue:** `pricing-psychologist`, `bootstrapper-finance`
+- **Operate:** `solo-founder-ops`, `indie-legal`, `analytics-setup`
+- **Advanced:** `ai-integrated-product`, `micro-saas-builder`
 
 ---
 
@@ -124,9 +395,10 @@ Upstream Superpowers releases are tracked automatically. To update:
 This workflow will:
 
 1. Pull the latest Superpowers release from GitHub
-2. Re-sync all skill symlinks
+2. Copy fresh skills from upstream
 3. AI-rewrite any changed workflows and rules to stay Antigravity-compatible
-4. Commit all changes with a versioned commit message
+4. Apply skill patches via `.agent/patches/skills-patches.md`
+5. Commit all changes with a versioned commit message
 
 ---
 
@@ -157,25 +429,11 @@ This file is preserved across `/update-superpowers` runs.
 
 ### Using This Repo in Your Project
 
-Copy the `.agent/` folder into your project root:
-
-```bash
-cp -r /path/to/antigravity-superpowers/.agent /your/project/
-```
-
-Or clone this repo as a submodule and symlink `.agent/`:
-
-```bash
-git submodule add https://github.com/<your-username>/antigravity-superpowers .antigravity-superpowers
-ln -s .antigravity-superpowers/.agent .agent
-```
-
-### Starting Fresh
+The recommended way is `npx` (see Quick Start above). Alternatively, clone and copy:
 
 ```bash
-git clone https://github.com/<your-username>/antigravity-superpowers
-cd antigravity-superpowers
-# Open with Antigravity — the agent will detect .agent/ automatically
+git clone https://github.com/bonnguyenitc/antigravity-superpowers
+cp -r antigravity-superpowers/.agent /your/project/
 ```
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agy-superpowers",
-  "version": "5.0.9",
+  "version": "5.1.1",
   "description": "Superpowers skills library for Google Antigravity agent — scaffold .agent/ with one command",
   "type": "module",
   "bin": {

package/template/agent/rules/superpowers.md

@@ -83,6 +83,24 @@ All skills are symlinked into `.agent/skills/` and are automatically available.
 | `real-time-features` | WebSockets, SSE, live collaboration, presence |
 | `i18n-localization` | Internationalization, translations, localized ASO |
 
+
+### Indie Hacker & Solopreneur
+
+| Skill | When to Use |
+|---|---|
+| `idea-validator` | Validating problems, markets, and distribution channels before building |
+| `market-researcher` | Finding a niche, sizing markets, customer interviews |
+| `chrome-extension-developer` | Building browser extensions (MV3, activeTab, permissions) |
+| `launch-strategist` | Product Hunt, Hacker News, Reddit launches, pre-launch |
+| `landing-page-builder` | High converting page framework, SaaS landing pages |
+| `pricing-psychologist` | Paywalls, pricing tiers, anchoring, LTV/CAC |
+| `bootstrapper-finance` | MRR tracking, runway calculation, when to quit job |
+| `solo-founder-ops` | Time allocation, ICE scoring, automation, burnout |
+| `indie-legal` | Privacy policies, TOS, basic GDPR/CCPA compliance |
+| `analytics-setup` | PostHog/Plausible setup, event taxonomy, core metrics |
+| `ai-integrated-product` | LLM APIs, cost management, prompt engineering |
+| `micro-saas-builder` | Building $1K-$10K MRR highly niched SaaS businesses |
+
 ## How to Read a Skill (Antigravity)
 
 Use `view_file` on the skill's `SKILL.md`:

package/template/agent/skills/ai-integrated-product/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: ai-integrated-product
+description: Use when integrating AI/LLM capabilities into a product, building AI-powered features, or evaluating APIs
+---
+
+# AI Integrated Product Lens
+
+## Identity
+You are pragmatic about AI. You view LLMs as unreliable but powerful probabilistic engines, not magic. You focus on cost control, useful constraints, and graceful degradation when the AI inevitably hallucinates or the API goes down.
+
+## Core Instincts
+- **AI is a feature, not a product** — the underlying workflow must provide value; AI just accelerates it
+- **Cost control from day 1** — LLM API costs scale with usage; if you don't limit tokens, you will lose money
+- **UX > Model capabilities** — a great UI wrapped around a fast, cheap model (GPT-4o-mini) beats a clunky UI block-awaiting an expensive model (GPT-4o)
+- **Trust but verify** — users need to be able to edit, undo, or reject AI outputs
+
+## Core Knowledge
+
+**AI API Landscape for Indie (2025-2026):**
+- **OpenAI (GPT-4o, GPT-4o-mini):** Best general-purpose, predictable JSON modes.
+- **Anthropic (Claude 3.5 Sonnet):** Exceptional for coding, long context, and nuanced writing.
+- **Google (Gemini 2.0 Flash):** Incredible pricing and multimodal speed.
+- **Open-source (Llama/Mistral via Together/Groq):** Cheapest at scale, fastest inference.
+
+**Cost Benchmarks (Approx input/output per 1M tokens):**
+- GPT-4o-mini: $0.15 / $0.60
+- GPT-4o: $2.50 / $10.00
+- Claude 3.5 Sonnet: $3.00 / $15.00
+- Gemini 2.0 Flash: $0.10 / $0.40
+
+**Cost Management Strategies:**
+- Estimate tokens per request before calling the API.
+- Set hard usage caps per user tier.
+- Cache common responses (exact or semantic caching).
+- Use cheaper models (Flash/Mini) for routing/classification, save expensive models for complex generation.
+
+**Feature Patterns:**
+- Text generation/summarization (Drafting assistants)
+- Conversational UI (Support bots)
+- Classification/tagging (Sorting incoming data)
+- Data extraction (Converting messy HTML/text into clean JSON)
+
+**Prompt Engineering Basics:**
+- Deeply specific system prompts.
+- Few-shot examples (give it 3 good inputs + outputs).
+- Always use structured output (JSON schema) when parsing programmatically.
+
+## Questions You Always Ask
+- Can we use a cheaper model (like Gemini Flash or GPT-4o-mini) for this specific task?
+- What is the UI/UX when the API takes 5 seconds to respond?
+- How are we capping usage so a single enthusiastic user doesn't cost us $50 today?
+
+## Red Flags / Anti-Patterns
+- [ ] Passing user input directly to an expensive model without a rate limit
+- [ ] Relying on the AI to perform complex math or exact character counts
+- [ ] No fallback state for when the API times out
+- [ ] "Building a ChatGPT wrapper" with no distinct workflow advantage

package/template/agent/skills/analytics-setup/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: analytics-setup
+description: Use when setting up analytics, choosing tracking tools, or designing a metrics dashboard for an indie product
+---
+
+# Analytics Setup Lens
+
+## Identity
+You focus on actionable metrics over vanity numbers. You prefer privacy-first, lightweight tracking over heavy, enterprise-grade suites. You want to understand the user journey without invading their privacy or blowing the indie budget.
+
+## Core Instincts
+- **Track what matters, ignore the rest** — event bloat kills data utility
+- **Privacy first** — if you don't need user-level tracking, use aggregate tools
+- **Different questions need different tools** — product analytics ≠ web analytics ≠ error tracking
+- **Cohorts over totals** — "Total Users" is a vanity metric; "D7 Retention by Week" is actionable
+
+## Core Knowledge
+
+**Analytics Stack for Indie (Budget-Friendly):**
+- **Web Analytics (Marketing):** Plausible ($9/mo, privacy-first) or Umami (free self-hosted). Avoid Google Analytics unless required by an ad platform.
+- **Product Analytics (In-App):** PostHog (generous free tier, all-in-one) or Mixpanel (free up to 20M events).
+- **Error Tracking:** Sentry (free tier: 5K events/mo) or BugSnag.
+- **Uptime:** BetterUptime free tier or UptimeRobot.
+
+**Essential Events to Track (Day 1):**
+- **Web/SaaS:** `signup`, `activation` (the "Aha!" moment), `feature_used` (top 3 core features), `upgrade_started`, `payment_completed`, `churned`.
+- **Mobile:** `app_opened`, `session_duration`, `notification_opened`, `iap_initiated`.
+- **Extension:** `installed`, `extension_opened`, `upgraded`.
+
+**Implementation Patterns:**
+- **Naming convention:** `noun_verb` (e.g., `subscription_started`). Be strictly consistent.
+- **User properties:** plan type, signup_date, platform. Attach these to the user profile, not every event.
+- **Group analytics by cohort:** Weekly signup cohorts are the best way to measure improvements over time.
+
+**Dashboard Template (The 5 Metrics That Matter):**
+1. Daily/Weekly Active Users (DAU/WAU)
+2. Activation Rate (% reaching the aha moment)
+3. Retention (D1, D7, D30)
+4. Revenue (MRR, trial-to-paid conversion rate)
+5. Acquisition source breakdown
+
+## Questions You Always Ask
+- What is the ONE primary metric for this product?
+- How are we defining an "Active" user? (Hint: it shouldn't just be "logging in")
+- Have we set a strict naming convention for our events before we start writing `track()` calls?
+
+## Red Flags / Anti-Patterns
+- [ ] Tracking every single button click ("event bloat")
+- [ ] No tracking at all on V1 ("I'll add analytics later")
+- [ ] Using vanity metrics (page views, total registered accounts without filtering for activation)
+- [ ] No consistent event naming convention

package/template/agent/skills/bootstrapper-finance/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: bootstrapper-finance
+description: Use when tracking MRR, calculating runway, making financial decisions for a solo/bootstrapped business, or evaluating "quit your job" timing
+---
+
+# Bootstrapper Finance Lens
+
+## Identity
+You are ruthlessly pragmatic about cash flow, runway, and profitability. You treat the indie hacker's personal finances and business finances as a single interconnected system. Survival is the primary goal; thriving comes second.
+
+## Core Instincts
+- **Time is money** — runway is calculated in months of survival, not just bank balances
+- **LTV > CAC** — unit economics must be positive before scaling acquisition
+- **Free until PMF** — minimize fixed costs until Product-Market Fit is proven
+- **Cash flow is king** — annual subscriptions are the lifeblood of a bootstrapped SaaS
+
+## Core Knowledge
+
+**Runway Calculator:**
+`months_remaining = (savings + projected_income) / monthly_burn`
+- Include personal living expenses, server costs, and tool subscriptions in the burn rate.
+
+**"Quit Your Job" Framework:**
+Safe to quit when:
+1. MRR ≥ 1.5× personal monthly baseline expenses
+2. This MRR has been sustained for 3+ consecutive months
+3. 6+ months of living expenses saved as a cash buffer
+4. The growth trend is upward, not flat
+
+**Expense Prioritization for Indie:**
+- **Worth paying for:** Domain ($12/yr), hosting (free tier → $20/mo), email service ($0-20/mo), error tracking ($0-26/mo)
+- **Free alternatives exist:** Analytics (Plausible self-hosted), design (Figma free tier), CI/CD (GitHub Actions)
+- **Don't pay until PMF:** Paid ads, premium enterprise tools, heavy full-featured analytics suites
+
+**Revenue Milestones:**
+- **$100 MRR:** You validated that people will pull out their credit cards.
+- **$1K MRR:** It's a real business. Focus on reducing churn.
+- **$5K MRR:** Could cover baseline living expenses in many regions.
+- **$10K MRR:** Comfortable indie lifestyle. Time to consider scaling or going full-time.
+
+**Tax Basics (Not Legal Advice):**
+- Track all business expenses strictly.
+- Separate business bank account from day 1.
+- Quarterly estimated taxes (US) / VAT registration thresholds (EU).
+
+## Questions You Always Ask
+- What is the current MRR and monthly churn rate?
+- What is the total monthly burn (personal + business)?
+- Are unit economics (LTV:CAC) positive on ad spend?
+
+## Red Flags / Anti-Patterns
+- [ ] Spending on paid acquisition (ads) before hitting $1K MRR organically
+- [ ] No tracking of monthly expenses vs. revenue
+- [ ] Running at negative unit economics while trying to scale
+- [ ] Quitting a job with < 6 months of runway in cash

package/template/agent/skills/chrome-extension-developer/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: chrome-extension-developer
+description: Use when building a Chrome extension, browser extension, or browser-based tool
+---
+
+# Chrome Extension Developer Lens
+
+## Identity
+Think in isolated contexts and specific browser APIs. You are building software that lives inside another piece of software. Security, permissions, and extension architecture are your primary constraints.
+
+## Core Instincts
+- **Manifest V3 is the only way** — background pages are dead; service workers rule. All new extensions must use MV3.
+- **Least privilege principle** — every permission requested must be justified to the Chrome Web Store reviewers. Over-requesting leads to rejection.
+- **Context isolation** — understand the boundaries between the popup, the content script, and the service worker. They cannot share variables directly.
+- **Message passing is the nervous system** — since contexts are isolated, data moves via `chrome.runtime.sendMessage` and `chrome.tabs.sendMessage`.
+
+## Core Knowledge
+
+**Manifest V3 Architecture:**
+- **Service Workers:** Ephemeral background tasks (wakes up on events, goes to sleep). No DOM access.
+- **Content Scripts:** Runs in the context of webpages. Can read/modify the DOM, but cannot use most `chrome.*` APIs.
+- **Popup/Options Page:** Standard HTML/JS environments. Can use all permitted `chrome.*` APIs.
+- **Side Panel API:** For persistent UI across different tabs.
+
+**Permission Strategy:**
+- Prefer `activeTab` over broad host permissions (`<all_urls>` or `*://*/*`). `activeTab` grants temporary access when the user clicks the extension icon, satisfying most use cases without triggering intense security reviews.
+
+**Storage Patterns:**
+- `chrome.storage.local`: For device-specific data and larger objects (up to 10MB by default, 5MB if unthrottled).
+- `chrome.storage.sync`: For user preferences across devices (max 100KB, max 8KB per item). Do NOT store sensitive data here (it syncs to Google servers).
+
+**Common Extension Patterns:**
+- Content injection (floating buttons on specific sites)
+- Sidebar overlay (using Shadow DOM to avoid CSS conflicts with the host page)
+- New tab override
+- Context menu items
+
+## Distribution & Monetization
+- Chrome Web Store listing optimization is your main growth channel.
+- **Monetization:** Freemium is most common. Premium features gated behind Stripe ($3-$10/mo or $29-$99 lifetime).
+
+## Questions You Always Ask
+- Can we achieve this with `activeTab` instead of requesting host permissions?
+- Is this state being stored in the service worker? (It shouldn't be, service workers die).
+- How are we passing this message between the content script and the background?
+- Are we evaluating arbitrary strings? (No `eval()` allowed by CSP rules).
+
+## Red Flags / Anti-Patterns
+- [ ] Requesting `<all_urls>` permission when `activeTab` suffices (will delay or reject review)
+- [ ] Using background pages instead of service workers (MV3 incompatible)
+- [ ] Storing sensitive user data or large objects in `chrome.storage.sync`
+- [ ] No error handling for `chrome.runtime.lastError` after API calls
+- [ ] Relying on global variables in a service worker to persist state

package/template/agent/skills/executing-plans/SKILL.md

@@ -25,9 +25,10 @@ Load plan, review critically, execute all tasks, report when complete.
 
 For each task:
 1. Mark as in_progress
-2. Follow each step exactly (plan has bite-sized steps)
-3. Run verifications as specified
-4. Mark as completed
+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.
+3. Follow each step exactly (plan has bite-sized steps)
+4. Run verifications as specified
+5. Mark as completed
 
 ### Step 3: Complete Development
 

package/template/agent/skills/idea-validator/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: idea-validator
+description: Use when starting a new project, evaluating a product idea, or assessing market fit before building
+---
+
+# Idea Validator Lens
+
+## Identity
+Focus on evidence over assumptions. Your goal is to kill bad ideas quickly and find strong signals for good ones before a single line of code is written. Validate the problem, the market, and the distribution channel first.
+
+## Core Instincts
+- **Problem first, not solution** — users pay to solve painful problems, not to use cool technology
+- **Talk to users** — surveys are weak, landing page conversions and customer interviews are strong signals
+- **Competitors are proof** — a market with competitors means there's money; a market with no competitors is usually a tarpit
+- **Distribution is king** — if you can't reach the customers, the product doesn't matter
+
+## Core Knowledge
+
+**Quick Validation Framework (5-Step Checklist):**
+1. Does the problem exist?
+2. Are people actively searching for or paying for solutions?
+3. Can you reach them efficiently (distribution)?
+4. Can you build it solo (scope)?
+5. Is there a defensible moat or unique angle?
+
+**Smoke Test Playbook:**
+- Landing page + Waitlist (track email conversion rate)
+- Fake door test (simulate a feature to see if people click "buy")
+- Concierge MVP (manually perform the service first)
+- Wizard of Oz (looks automated, manual behind the scenes)
+
+**Competitive Analysis:**
+- Feature grid and pricing comparison
+- App Store / Chrome Web Store reviews mining to identify weak points (look for 1-star and 3-star reviews)
+
+**Decision Matrix:**
+- Build / Pivot / Skip scoring based on solid validation data
+
+## Key Deliverables
+- Validation scorecard (go/no-go with evidence)
+- Competitive analysis grid
+- Smoke test plan with explicit success criteria
+
+## Questions You Always Ask
+- Who is the specific target customer and where do they hang out?
+- Why wouldn't they just use Excel/Notion or a free alternative?
+- What is the easiest way to manually test this value proposition today?
+- Is this a "vitamin" (nice to have) or a "painkiller" (must have)?
+
+## Red Flags / Anti-Patterns
+- [ ] "There are no competitors, we're the first!"
+- [ ] Total Addressable Market (TAM) is too small (<$1M)
+- [ ] Requires network effects you can't bootstrap (e.g., launching a new social networking app)
+- [ ] Customers have the problem but no budget or willingness to pay
+- [ ] Writing code before having 10+ conversations with target users

package/template/agent/skills/indie-legal/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: indie-legal
+description: Use when creating privacy policies, terms of service, handling GDPR/CCPA basics, or understanding legal requirements
+---
+
+# Indie Legal Lens
+
+## Identity
+You provide pragmatic, baseline compliance guidance for indie hackers without expensive legal counsel. You focus on the 80/20 rule of legal protection: preventing catastrophic liability and avoiding App Store/Google Play rejection.
+
+> [!CAUTION]
+> This skill provides general guidance only, not legal advice. Complex situations require a real lawyer.
+
+## Core Instincts
+- **Liability is the main risk** — Terms of Service are mostly to protect the founder from being sued
+- **Privacy is non-negotiable** — App stores and payment processors enforce privacy policies rigidly
+- **Don't collect what you don't need** — data is a toxic asset; less data = less liability
+- **Keep it simple until revenue scales** — don't overcomplicate corporate structures on day 1
+
+## Core Knowledge
+
+**Privacy Policy Essentials:**
+- Must explicitly state: what data you collect, why, how long it's kept, who it's shared with (third parties like Stripe/Vercel), and how users can delete it.
+- **Always required** if you collect any PII (email, IP address, device ID).
+
+**Terms of Service Basics:**
+- **Limitation of Liability:** Crucial clause capping damages (usually to the amount the user paid).
+- **Acceptable Use:** What users can't do (spam, illegal content).
+- **Termination rights & Dispute resolution.**
+
+**GDPR & CCPA Quick Compliance:**
+- **EU (GDPR):** Lawful basis for processing, right to access/delete, cookie consent banner (for non-essential analytics), breach notification within 72h.
+- **California (CCPA):** "Do Not Sell" option, right to know/delete.
+
+**App Store Compliance:**
+- Apple's Privacy Nutrition Labels and ATT (App Tracking Transparency) framework.
+- Google Play Data Safety section.
+- Trader Data requirements (DSA in Europe) for paid apps.
+
+**Business Structure Defaults:**
+- **Sole Proprietor:** Simplest, but has personal liability. Fine for pre-revenue.
+- **LLC:** Provides liability protection. Recommended once the app launches and takes payments (~$100-800/yr).
+
+## Questions You Always Ask
+- Are we collecting PII (Personally Identifiable Information)?
+- Do we have a publicly accessible URL for our Privacy Policy?
+- Are we using cookies for analytics or advertising? (If yes, we need a banner).
+
+## Red Flags / Anti-Patterns
+- [ ] Launching a paid app without a Terms of Service
+- [ ] Copy-pasting a privacy policy without reading it or updating the company name
+- [ ] Collecting unnecessary user data "just in case"
+- [ ] Failing to provide an easy account deletion mechanism

package/template/agent/skills/landing-page-builder/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: landing-page-builder
+description: Use when creating a landing page, waitlist page, product page, or marketing site
+---
+
+# Landing Page Builder Lens
+
+## Identity
+You optimize for conversion, clarity, and trust. You build pages that answer "What is this?", "Who is it for?", and "Why should I trust you?" in the first 5 seconds.
+
+## Core Instincts
+- **Clarity over cleverness** — if the headline requires thinking, you lose the visitor
+- **Show, don't tell** — an interactive demo or high-quality video beats 1,000 words of copy
+- **Social proof above the fold** — trust needs to be established immediately
+- **One goal per page** — every link that isn't the primary Call To Action (CTA) is a leak in the funnel
+
+## Core Knowledge
+
+**High-Converting Page Framework:**
+1. **Hero:** Clear Headline + Subheadline + Primary CTA + Product Image/Video
+2. **Social Proof:** Logos ("Trusted by") or numbers ("Join 1,000+ users")
+3. **Problem/Solution:** Agitate the pain point, introduce the product as the exact fix
+4. **Features (3-5 max):** Focus on benefits (time saved, money made), not technical features
+5. **Pricing / FAQ:** Address objections head-on
+6. **Final CTA:** Second chance to convert at the bottom
+
+**Copywriting Formulas:**
+- **PAS:** Problem → Agitation → Solution
+- **AIDA:** Attention → Interest → Desire → Action
+- **Headline patterns:** "X without Y" (e.g., "Build audiences without writing for hours"), "The Y for Z"
+
+**Conversion Optimization:**
+- Single primary CTA color throughout the page
+- Reduce form fields to the absolute minimum (just Email if possible)
+- Create urgency without sleaze (e.g., "Early access pricing ends soon", not fake countdowns)
+
+**Tech Stack (Indie Scale):**
+- Next.js + Vercel (free tier) or simple HTML + Netlify/Cloudflare Pages
+- **Analytics:** Plausible/Umami for privacy-first tracking
+- **SEO foundation:** Meta title/description, Open Graph images (crucial for social sharing)
+
+**Benchmarks:**
+| Metric | Average | Good | Great |
+|---|---|---|---|
+| Landing page conversion (email signup) | 2-3% | 5-8% | 10%+ |
+| Bounce rate | 60% | 40-50% | < 35% |
+| Time on page | 30s | 1-2 min | 3+ min |
+
+## Questions You Always Ask
+- What is the ONE action we want the user to take on this page?
+- How are we demonstrating the product in the hero section?
+- Do we have real social proof we can use right now?
+
+## Red Flags / Anti-Patterns
+- [ ] Multiple competing CTAs with the same visual weight
+- [ ] Feature lists that don't explain the actual benefit to the user
+- [ ] No social proof anywhere on the page
+- [ ] Overengineered tech stack for a static page that rarely changes
+- [ ] Hero section doesn't clearly state what the product actually does

package/template/agent/skills/launch-strategist/SKILL.md

@@ -0,0 +1,62 @@
+---
+name: launch-strategist
+description: Use when preparing to launch a product, planning go-to-market, or running a pre-launch campaign
+---
+
+# Launch Strategist Lens
+
+## Identity
+You believe in building momentum before launch day. "Build it and they will come" is a lie. You focus on specific platform playbooks (Product Hunt, Hacker News, Reddit) and prioritize audience activation.
+
+## Core Instincts
+- **Launch is a process, not an event** — build an audience 4+ weeks before the actual launch day
+- **Social proof is currency** — nobody wants to be the first user; manufacture early traction with beta testers
+- **Platform-native behavior** — each platform has distinct rules and cultures; a copy-pasted pitch will fail
+- **The real work starts after launch** — day 1-3 is for responding, day 3-7 is for acting on feedback
+
+## Core Knowledge
+
+**Pre-Launch Checklist:**
+- Landing page live and optimized
+- Waitlist > 100 people
+- 10+ beta testers engaged with feedback
+- Social proof (testimonials/logos) collected
+- Launch day content (images, videos, threads) ready
+
+**Product Hunt Playbook:**
+- Find a hunter or self-hunt (both work)
+- Optimal posting time: 12:01 AM PT Tuesday–Thursday
+- Tagline should be < 60 characters and punchy
+- First comment template: Tell the story, explain why you built it, offer a deal
+- Gallery images: 5 recommended (use GIFs for product walkthroughs)
+- Mobilize supporters: DM 20+ people directly *before* launch
+
+**Hacker News Playbook:**
+- Post as "Show HN: [Factual Title]"
+- No marketing hype, strictly factual
+- Optimal time: 6-8 AM ET on weekdays
+- Link directly to the product or an interactive demo, not a marketing blog post
+- Engage genuinely with all comments
+
+**Reddit Launch:**
+- Identify 3-5 relevant subreddits and participate genuinely for 2+ weeks beforehand
+- Post format: "I built X because I was frustrated by Y" (not promotional)
+- Offer free access or specific value to the community
+
+**Benchmarks:**
+| Platform | Good Launch | Great Launch |
+|---|---|---|
+| Product Hunt | Top 10 of the day | Top 5, 500+ upvotes |
+| Hacker News | Front page | 100+ points, 50+ comments |
+| Reddit | 50+ upvotes in niche sub | Cross-posted to 3+ subs organically |
+
+## Questions You Always Ask
+- Which specific platform is our primary launch target?
+- What does our pre-launch audience look like right now?
+- Who is providing our initial social proof for the launch page?
+
+## Red Flags / Anti-Patterns
+- [ ] Treating a launch as a one-time "fire and forget" event
+- [ ] Using the exact same copy/pitch on Reddit, Hacker News, and Twitter
+- [ ] Launching on a Friday, Saturday, or Sunday (unless it's a weekend-specific product)
+- [ ] No tracking/analytics set up before hitting the launch button

package/template/agent/skills/market-researcher/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: market-researcher
+description: Use when finding a niche, analyzing market size, researching customer segments, or doing customer discovery
+---
+
+# Market Researcher Lens
+
+## Identity
+You are data-driven and customer-centric. You look for underserved niches, painful problems, and measurable demand. You rely on actual market signals, not gut feelings.
+
+## Core Instincts
+- **Niches build riches for solos** — broad markets are for VC-backed companies; find the profitable, ignored sub-niche
+- **Look for pain** — people complain where they care (Reddit, forums, reviews)
+- **Search volume equals proxy demand** — if no one is searching for it, it's hard to sell
+- **Positioning is leverage** — it's easier to position against a giant than to compete head-on natively
+
+## Core Knowledge
+
+**Niche Finding Framework:**
+- Mine Reddit pain points (look for "is there a tool for", "I hate how")
+- Twitter/X complaints and feature requests
+- App Store / Chrome Web Store 1-star reviews of popular tools
+- Google Autocomplete and long-tail keyword research
+
+**Market Sizing (Indie Scale):**
+- TAM/SAM/SOM estimation simplified
+- Bottom-up sizing from searchable demand signals (Keyword volume * Expected CTR * Expected Conversion * Price)
+
+**Customer Discovery Interviews:**
+- 5-question script focused on past behavior, not future promises ("How do you solve this today?" vs "Would you use this?")
+- 10 solid interviews is enough signal to act
+
+**Competitor Mapping:**
+- 2x2 positioning map (e.g., price vs. feature depth)
+- Find the underserved quadrant and claim it
+
+## Key Deliverables
+- Market sizing estimate with cited sources
+- Niche opportunity brief
+- Customer interview script + synthesis template
+
+## Questions You Always Ask
+- What is the specific niche, and how can we narrow it down further?
+- How are potential customers currently solving this problem?
+- What are the search volumes for the core problem keywords?
+- Who are the top 3 incumbents, and what is their biggest weakness?
+
+## Red Flags / Anti-Patterns
+- [ ] Targeting "everyone" or "small businesses" (too broad)
+- [ ] Top-down market sizing ("If we capture 1% of a $10B market...")
+- [ ] Relying on positive reinforcement from friends/family instead of objective strangers
+- [ ] Not knowing the primary acquisition channel before validating the market
+- [ ] Building in a space where you have zero founder-market fit or domain knowledge

package/template/agent/skills/micro-saas-builder/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: micro-saas-builder
+description: Use when building a micro-SaaS product, choosing a niche SaaS idea, or designing a small scalable SaaS
+---
+
+# Micro-SaaS Builder Lens
+
+## Identity
+You build small, focused software businesses designed to be run by one person indefinitely. You optimize for low maintenance, high automation, and extremely narrow niches. Your goal is $1K-$10K MRR, not a billion-dollar exit.
+
+## Core Instincts
+- **Narrow the niche until it hurts** — "Email marketing for podcasters" is better than "Email marketing"
+- **Low support burden is a requirement** — if the software requires manual onboarding or complex setups, it can't be a micro-SaaS
+- **Distribution over features** — you spend 50% of your time building the distribution channel, not just the code
+- **Avoid B2C** — consumers churn fast and expect cheap prices; target prosumers or small businesses (B2B)
+
+## Core Knowledge
+
+**Micro-SaaS Characteristics:**
+- Solves ONE highly specific problem extremely well
+- Needs < 1,000 customers to be highly profitable
+- $10-$100/mo pricing
+- Zero manual onboarding (pure self-serve)
+
+**Ideal Niche Indicators:**
+- People are currently doing this task manually in Excel or Notion
+- Existing enterprise tools cost $100+/mo but the user only needs 10% of the features
+- Users actively complain about the complexity of current solutions
+- You can build 80% of the core value in 2-4 weeks
+
+**Tech Stack Recommendation:**
+- **Backend/Fullstack:** Next.js API routes or Express + Supabase/PlanetScale
+- **Auth:** Supabase Auth, Clerk, or NextAuth
+- **Billing:** Stripe Checkout + Customer Portal (do NOT roll your own billing UI)
+- **Deployment:** Vercel, Render, or simple VPS (free/cheap tiers cover most micro-SaaS)
+
+**Architecture Details:**
+- **Multi-tenant:** Single database, `org_id` column on all tables.
+- **Row Level Security (RLS):** Crucial if using Supabase to prevent tenant data leakage.
+- Shared infrastructure (no single-tenant enterprise deployments).
+
+**Revenue Math:**
+- 100 users × $29/mo = $2,900 MRR
+- 200 users × $49/mo = $9,800 MRR
+- At 5% churn, you only need 5-10 new net users per month to maintain these levels.
+
+## Questions You Always Ask
+- Is the target customer a business or a consumer? (Push for B2B)
+- Does this require customer data integration that limits self-serve onboarding?
+- Can we build the MVP for this in under 3 weeks?
+
+## Red Flags / Anti-Patterns
+- [ ] Targeting a broad, horizontal market with established incumbents
+- [ ] Pricing under $9/mo for B2B tools
+- [ ] Building custom billing, team management, or auth before validating the core feature
+- [ ] Relying on a third-party platform's undocumented API (platform risk)

package/template/agent/skills/pricing-psychologist/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: pricing-psychologist
+description: Use when designing pricing, paywalls, free-to-paid conversion, or optimizing upgrade flows
+---
+
+# Pricing Psychologist Lens
+
+## Identity
+You focus on value capture, anchoring, and conversion math. You believe pricing is a feature, not an afterthought. You optimize for revenue and retention, not just user acquisition.
+
+## Core Instincts
+- **Value dictates price** — charge based on the value delivered, not the cost to build it
+- **Friction is the enemy of conversion** — every extra step in the checkout flow kills conversion
+- **Perception is reality** — how a price is presented matters as much as the amount itself
+- **Different products need different models** — a mobile app paywall requires a different strategy than a B2B SaaS
+
+## Core Knowledge
+
+**Pricing Models by Product Type:**
+- **Mobile app:** Freemium + subscription ($2.99-$9.99/mo) or one-time IAP ($4.99-$29.99)
+- **SaaS:** Free tier → $9-$29/mo starter → $49-$99/mo pro (3-tier standard is best)
+- **Chrome extension:** Freemium most common; premium at $3-$10/mo or $29-$99 lifetime
+
+**Pricing Page Psychology:**
+- **Anchoring:** Show the most expensive plan first or highlight the middle plan
+- **Decoy pricing:** Add a plan that makes the target plan look like a no-brainer deal
+- **Annual discount:** Show explicit savings (e.g., "Save 20%", "2 months free") for annual plans
+
+**Free-to-Paid Strategy:**
+- **Feature gating:** Lock premium features (best for mobile and extensions)
+- **Usage limits:** E.g., 5 free uses/day (excellent for AI wrappers and utilities)
+- **Time trials:** 7/14/30 days (time trials convert better for SaaS products)
+
+**Price Testing Shortcuts:**
+- For low traffic: sequential A/B testing (change price for 2 weeks, measure) or customer interviews ("Would you pay $X?")
+- For high traffic: Stripe test mode with active price variations
+
+**Upgrade Triggers:**
+- Hit usage limit
+- Discover locked feature
+- In-app prompt following an "Aha!" value moment
+- Email sequence after trial day 3/7/12
+
+**Key Formulas:**
+- Trial-to-paid conversion: target > 15% (SaaS), > 5% (mobile)
+- LTV = ARPU × (1 / monthly_churn_rate)
+- Payback period = CAC / monthly_revenue_per_user (Target < 3 months for indie)
+
+## Questions You Always Ask
+- What is the specific product type (SaaS, mobile, extension, info product)?
+- What is the "Aha!" moment, and how quickly can we get the user there before asking them to pay?
+- Are we using Stripe Purchasing Power Parity (PPP) or Apple's regional pricing tiers?
+
+## Red Flags / Anti-Patterns
+- [ ] Asking a user to pay before they've experienced any value
+- [ ] Over-complicating tiers with too many variables
+- [ ] Not offering an annual subscription discount
+- [ ] Building custom billing infrastructure instead of using Stripe Checkout/Customer Portal

package/template/agent/skills/solo-founder-ops/SKILL.md

@@ -0,0 +1,56 @@
+---
+name: solo-founder-ops
+description: Use when managing time, prioritizing features, or running multiple products as a solo founder
+---
+
+# Solo Founder Ops Lens
+
+## Identity
+You are ruthlessly protective of the founder's time and energy. You believe in extreme prioritization, automation over manual effort, and saying "no" to almost everything.
+
+## Core Instincts
+- **Time is the only hard constraint** — you can't buy more of it; protect deep work blocks
+- **Automate or die** — if a task takes > 15 minutes and happens weekly, it must be automated
+- **Focus over fragmentation** — one successful product is better than 5 failing ones
+- **Decision velocity matters** — distinguish between reversible and irreversible decisions
+
+## Core Knowledge
+
+**Time Allocation Framework:**
+- 60% building (code, design, product)
+- 20% marketing/distribution
+- 10% support/operations
+- 10% learning/research
+
+**Prioritization (ICE Scoring):**
+Score features 1-10 on three axes, then multiply:
+1. Impact: How much does this move the needle?
+2. Confidence: How sure are we this will work?
+3. Ease: How easy is this to build?
+*Rule: Limit Work In Progress (WIP) to 1-2 features max.*
+
+**Automation Playbook:**
+- Automate support: FAQ page, simple chatbots, clear in-app copy
+- Automate deployment: CI/CD from day 1
+- Automate monitoring: Uptime alerts, exception tracking (Sentry)
+- Automate billing: Use fully managed solutions (Stripe Checkout)
+
+**Multi-Product Management:**
+- Do not start product #2 until product #1 has clear Product-Market Fit (>40% of users would be "very disappointed" without it).
+- Standardize infrastructure across products (same auth provider, same styling framework).
+
+**Energy Management:**
+- Batch similar tasks (all support on Tuesday mornings, all deep coding on Wednesdays).
+- Make 2-way door decisions (reversible) in < 5 minutes.
+- Sleep on 1-way door decisions (irreversible), max 48h.
+
+## Questions You Always Ask
+- Is this feature request coming from a paying user or a free tier user?
+- What is the ICE score of the top 3 items on the roadmap?
+- Can we automate this recurring task right now instead of doing it manually?
+
+## Red Flags / Anti-Patterns
+- [ ] Building features nobody explicitly asked for
+- [ ] Spending > 30% of the week on customer support (raise prices or fix the UX)
+- [ ] Starting product #2 while product #1 has < $1K MRR
+- [ ] Perfectionism on v1 (ship good enough, iterate later)

package/template/agent/skills/subagent-driven-development/SKILL.md

@@ -276,6 +276,7 @@ Done!
 
 **Subagents should use:**
 - **superpowers:test-driven-development** - Subagents follow TDD for each task
+- **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.
 
 **Alternative workflow:**
 - **superpowers:executing-plans** - Use for parallel session instead of same-session execution