agy-superpowers 5.2.2 → 5.2.3

package/template/agent/skills/game-developer/SKILL.md

@@ -1,175 +0,0 @@
----
-name: game-developer
-description: Use when working on mobile app features, reviewing mobile code, or making architecture decisions — regardless of platform (React Native, Flutter, iOS, Android)
----
-
-# Game Developer Lens
-
-> **Philosophy:** Games are real-time, frame-budget-constrained simulations. Every millisecond counts.
-> Fun is the product. Performance is the enabler. Both must ship together.
-
----
-
-## ⚠️ ASK BEFORE ASSUMING
-
-| What | Why it matters |
-|------|----------------|
-| **Platform?** Mobile / PC / Console / Web | Frame budget, input model, distribution channel all differ |
-| **Engine?** Unity / Unreal / Godot / custom | Determines every technical pattern |
-| **Genre?** Puzzle / RPG / Action / Idle | Core loop architecture differs fundamentally |
-| **Online?** Singleplayer / Multiplayer / MMO | Networking complexity changes everything |
-
-When unspecified, assume Unity + C# + mobile (iOS + Android).
-
----
-
-## Frame Budget
-
-```
-Target frame rate → frame budget → time per frame
-60 FPS  =  16.67ms per frame  (mobile standard)
-30 FPS  =  33.33ms per frame  (minimum acceptable mobile)
-120 FPS =   8.33ms per frame  (high-refresh displays)
-
-Budget allocation guideline (16.67ms total):
-  CPU (game logic + physics): ~6ms
-  CPU (rendering commands):   ~4ms
-  GPU (draw calls + shaders): ~6ms
-  Headroom (OS, audio, GC):  ~0.67ms
-
-If any system consistently exceeds budget → frame drops → player frustration
-```
-
----
-
-## Engine Decision Tree
-
-```
-What engine?
-├── AAA budget + PC/Console + team → Unreal Engine (C++)
-├── Mobile + fast iteration + mid-size → Unity (C#)
-├── Indie + open source + 2D/3D → Godot (GDScript or C#)
-├── Browser target → Phaser.js / Babylon.js / Three.js
-└── Existing engine in codebase → match codebase
-```
-
----
-
-## Core Instincts
-
-- **The game loop is sacred** — Input → Update → Render, every frame, on time
-- **Object pooling over instantiation** — `Instantiate()` at runtime = GC spike = frame drop
-- **Draw calls are the enemy** — batch sprites, use atlases, instanced rendering
-- **Physics runs on a fixed timestep** — decouple physics from render frame rate
-- **GC pauses kill games** — allocate in `Start()`/`Awake()`, never in `Update()`
-- **Profiler first, optimize second** — never guess what's slow
-
----
-
-## Performance Thresholds (Mobile)
-
-| Metric | Good | Investigate |
-|--------|------|-------------|
-| Frame rate (gameplay) | 60 FPS sustained | < 45 FPS |
-| Frame rate (menus/UI) | 60 FPS | < 30 FPS |
-| Draw calls per frame | < 100 | > 200 |
-| Texture memory | < 256MB | > 512MB |
-| APK / IPA size | < 100MB | > 200MB (impacts conversion) |
-| RAM usage (mid-range device) | < 300MB | > 500MB (OS kills app) |
-| Load time (initial) | < 5s | > 10s |
-| GC allocation per frame | 0B | > 0B (any = risk) |
-
----
-
-## ❌ Anti-Patterns to Avoid
-
-| ❌ NEVER DO | Why | ✅ DO INSTEAD |
-|------------|-----|--------------|
-| `Instantiate()`/`Destroy()` in `Update()` | GC spike = frame drop | Object pooling |
-| `GameObject.Find()` in `Update()` | Expensive search every frame | Cache reference in `Start()` |
-| Non-atlased sprites | 1 draw call per sprite = explosion | Sprite Atlas / texture packing |
-| `string` concatenation in `Update()` | String allocation = GC | `StringBuilder` or avoid |
-| Unnecessary `GetComponent<>()` per frame | Expensive reflection | Cache in `Awake()/Start()` |
-| Physics on non-fixed timestep | Non-deterministic simulation | Use `FixedUpdate()` for physics |
-| Uncompressed audio | Large bundle, high memory | OGG for music, WAV for short SFX only |
-| `Debug.Log()` in build | CPU overhead, even in release | Strip with `#if UNITY_EDITOR` or Conditional |
-
----
-
-## Platform Considerations
-
-| Concern | iOS | Android |
-|---------|-----|---------|
-| Max texture size | 4096×4096 | 4096×4096 |
-| Graphics API | Metal | Vulkan / OpenGL ES 3.0 |
-| Target FPS API | `Application.targetFrameRate = 60` | Same |
-| Memory kill threshold | ~1.5GB | Varies by device (256MB–4GB) |
-| App size limit (OTA) | 200MB cellular cap | No cap (varies by store) |
-| Haptic feedback | `UnityEngine.iOS.Device.SetNoBackupFlag` / Core Haptics | Vibration API |
-
----
-
-## Multi-Scene / Asset Loading Pattern
-
-```csharp
-// Async scene loading (never use sync — it freezes)
-async void LoadScene(string sceneName) {
-  var op = SceneManager.LoadSceneAsync(sceneName, LoadSceneMode.Additive);
-  op.allowSceneActivation = false;
-  while (op.progress < 0.9f) {
-    loadingBar.value = op.progress;
-    await Task.Yield();
-  }
-  op.allowSceneActivation = true;
-}
-
-// Addressables for asset streaming (don't include everything in build)
-var handle = Addressables.LoadAssetAsync<GameObject>("enemies/boss");
-await handle.Task;
-```
-
----
-
-## Questions You Always Ask
-
-**When designing a system:**
-- Does any allocation happen inside `Update()`? (GC risk)
-- Is this system tested on a low-end Android device (Qualcomm 450-class)?
-- What's the draw call count before and after this change?
-- Does this work at 30 FPS? (Not just 60 FPS in editor)
-
-**When reviewing code:**
-- Are expensive operations cached?
-- Is physics logic in `FixedUpdate()`, not `Update()`?
-- Are textures atlased and compressed?
-
----
-
-## Red Flags in Code Review
-
-**Must fix:**
-- [ ] Allocations happening inside `Update()` loop
-- [ ] `Find()` or `GetComponent<>()` called per frame without caching
-- [ ] Unatlased sprite renderers (high draw call count)
-- [ ] Synchronous scene loading
-
-**Should fix:**
-- [ ] No object pooling for frequently spawned objects
-- [ ] Uncompressed audio assets
-- [ ] Debug.Log calls in production build paths
-
----
-
-## Who to Pair With
-- `game-design` — for game loop, balance, and player psychology
-- `mobile-developer` — for mobile platform constraints and store distribution
-- `monetization-strategist` — for IAP and ad monetization strategy
-- `app-store-optimizer` — for App Store/Google Play listing
-
----
-
-## Tools
-**Engines:** Unity · Unreal Engine · Godot  
-**Profiling:** Unity Profiler · Xcode Instruments · Android GPU Inspector · RenderDoc  
-**Asset pipeline:** TexturePacker (atlasing) · Addressables (Unity) · FMOD / Wwise (audio)  
-**Analytics:** Unity Analytics · GameAnalytics · Firebase (games)

package/template/agent/skills/growth-hacker/SKILL.md

@@ -1,122 +0,0 @@
----
-name: growth-hacker
-description: Use when planning user acquisition, building viral loops, designing activation funnels, or running growth experiments — for any product type
----
-
-# Growth Hacker Lens
-
-> **Philosophy:** Growth is a system, not a campaign. Build loops, not one-time spikes.
-> Optimize activation before acquisition. A leaky bucket can't be filled by pouring more water.
-
----
-
-## Core Instincts
-
-- **Fix the funnel before filling it** — acquisition without retention is burning money
-- **North Star first** — all growth work should connect to one metric that captures delivered value
-- **Build loops, not funnels** — sustainable growth is self-reinforcing (referral, content, product virality)
-- **Kill ideas fast** — run the simplest possible test before investing in a full build
-- **Pre-PMF: qualitative; post-PMF: quantitative**
-
----
-
-## AARRR Framework (Pirate Metrics)
-
-| Stage | Key Question | Metric |
-|-------|-------------|--------|
-| **Acquisition** | Where do users come from? | CAC, channel attribution |
-| **Activation** | Do users experience value quickly? | % hitting "aha moment" in session 1 |
-| **Retention** | Do users come back? | D1/D7/D30 retention rates |
-| **Revenue** | Do users pay? | Conversion rate, ARPU, MRR |
-| **Referral** | Do users tell others? | Viral coefficient K, NPS |
-
-**Indie hacker priority order: Retention → Activation → Revenue → Acquisition → Referral**
-(Fix retention first — everything else is downstream.)
-
----
-
-## Viral Coefficient
-
-```
-K = i × c
-  i = average invites sent per user
-  c = conversion rate of those invites (0–1)
-
-K > 1 = viral (exponential growth)
-K = 0.5 + strong acquisition = sustainable growth
-K < 0.1 = product-led growth isn't working; use other channels
-```
-
----
-
-## Activation Benchmarks
-
-| Metric | Good | Great |
-|--------|------|-------|
-| Day 1 retention (mobile) | > 30% | > 45% |
-| Activation rate (hit aha moment) | > 40% | > 60% |
-| Time to first value | < 5 min | < 2 min |
-| Onboarding completion | > 60% | > 80% |
-
-**Aha moment** = the specific action that most correlates with long-term retention. Find it via cohort analysis: what do retained users do that churned users don't?
-
----
-
-## ❌ Anti-Patterns to Avoid
-
-| ❌ NEVER DO | Why | ✅ DO INSTEAD |
-|------------|-----|--------------|
-| Scale acquisition pre-PMF | Filling a leaky bucket | Get to K=0.5+ / 40% D30 retention first |
-| Run experiments without hypothesis | Results are uninterpretable | Document hypothesis before every experiment |
-| Celebrate signup numbers | Signups are vanity; activation and retention are sanity | Track activated users, not total signups |
-| One-time launch spike as "growth" | Not repeatable, not a system | Build channels with compounding returns |
-| Change multiple variables in one test | Can't attribute the result | One variable at a time |
-| Scale a channel before unit economics work | CAC > LTV = faster bankruptcy | LTV:CAC ≥ 3:1 before scaling spend |
-
----
-
-## Questions You Always Ask
-
-**When diagnosing growth:**
-- Where is the biggest drop in the AARRR funnel right now?
-- What does the aha moment look like, and how fast do users get there?
-- Is this a retention problem (fix product) or an acquisition problem (optimize funnel)?
-
-**When planning experiments:**
-- What's the hypothesis? What would prove it wrong?
-- What's the minimum sample size for statistical significance?
-- How long does the experiment need to run? (Avoid stopping early)
-
----
-
-## Red Flags
-
-**Must address:**
-- [ ] D30 retention < 10% and team is focused on acquisition
-- [ ] No defined aha moment / activation event
-- [ ] Growth experiments running without documented hypothesis
-- [ ] CAC > LTV (actively destroying value)
-
-**Should address:**
-- [ ] No referral mechanism in product
-- [ ] Acquisition fully dependent on paid (no organic loop)
-- [ ] Onboarding completion < 50%
-
----
-
-## Who to Pair With
-- `product-manager` — for activation and aha moment definition
-- `data-analyst` — for cohort analysis and experiment significance
-- `retention-specialist` — for fixing the funnel before scaling
-
----
-
-## Key Formulas
-
-```
-CAC     = total acquisition spend / new customers acquired
-LTV     = ARPU × (1 / monthly_churn_rate)
-LTV:CAC = should be ≥ 3:1 (ideally > 5:1)
-Payback = CAC / monthly_gross_margin_per_customer (target < 12 months)
-K       = invites_per_user × invite_conversion_rate
-```

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

@@ -1,55 +0,0 @@
----
-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

@@ -1,53 +0,0 @@
----
-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/influencer-marketer/SKILL.md

@@ -1,141 +0,0 @@
----
-name: influencer-marketer
-description: Use when planning UGC campaigns, creator partnerships, TikTok/YouTube/Instagram marketing, affiliate programs, or word-of-mouth amplification strategies
----
-
-# Influencer Marketer Lens
-
-> **Philosophy:** Creators are trusted media channels with pre-built audiences. One authentic review beats 1000 banner ads.
-> The best influencer marketing doesn't look like marketing.
-
----
-
-## Core Instincts
-
-- **Authenticity > reach** — a micro-influencer who uses your product converts better than a mega-influencer who doesn't
-- **Product-market fit before influencer fit** — influencer marketing amplifies; it doesn't create
-- **Micro > macro for early-stage** — 10K–100K followers with high engagement beats 1M followers with 0.5% ER
-- **UGC is the asset** — even if a campaign flops, the content you own is valuable for ads
-- **Long-term > one-off** — repeat mentions build brand association; single posts are noise
-
----
-
-## Influencer Tier Reference
-
-| Tier | Followers | Instagram ER | TikTok ER | Best for |
-|------|-----------|-------------|----------|----------|
-| **Nano** | 1K – 10K | 5–9% | 9–15% | Niche communities, very authentic |
-| **Micro** | 10K – 100K | 3–5% | 5–9% | Best ROI for indie hackers; targeted audiences |
-| **Mid-tier** | 100K – 500K | 1.5–3% | 3–6% | Scale with proven product |
-| **Macro** | 500K – 1M | 1–2% | 2–4% | Brand awareness; expensive |
-| **Mega / Celebrity** | 1M+ | 0.5–1% | 1–3% | Mass awareness; rarely cost-effective |
-
-**Engagement Rate (ER):** `(likes + comments) / followers × 100`  
-**Minimum bar:** ER < 1% (Instagram) or < 2% (TikTok) = avoid regardless of follower count.  
-**Note:** TikTok ERs are structurally higher than Instagram due to algorithmic distribution to non-followers.
-
----
-
-## Platform Strategy
-
-| Platform | Content format | Best for | Purchase intent |
-|----------|---------------|----------|----------------|
-| **TikTok** | Short video (15s–3min) | Consumer apps, Gen Z/Millennial | Medium-high |
-| **YouTube** | Long-form, tutorials, reviews | Tools, SaaS, education | High |
-| **Instagram** | Reels, Stories, carousel | Lifestyle, consumer apps | Medium |
-| **X (Twitter)** | Threads, screenshots | Developer tools, B2B | Medium |
-| **Newsletter** | Written features, sponsored posts | B2B SaaS, niche products | Very high |
-
----
-
-## Creator Outreach Template
-
-```
-Subject: [Your product] + [Creator name] collab?
-
-Hi [Name],
-
-I've been following your [specific content] for [time] — specifically loved [specific post].
-
-I built [product] for [specific audience that matches theirs]. I think your followers would 
-genuinely find it useful because [specific reason].
-
-I'd love to offer you [free access / commission / fee] to try it and share your honest 
-experience — no script, just your real take.
-
-Interested in a quick chat?
-[Name]
-```
-
-**Key:** Reference specific content → show you actually watch them → explain why it fits their audience → make the ask small.
-
----
-
-## Compensation Models
-
-| Model | When to use | Risk |
-|-------|------------|------|
-| **Product gifting** | Nano/micro; product is genuinely useful | Low reach if they don't post |
-| **Affiliate / commission** | Performance-based; aligns incentives | Creators may prefer upfront |
-| **Flat fee + affiliate** | Larger creators; guaranteed post | Higher upfront cost |
-| **Revenue share** | Long-term partnerships | Complex to track |
-| **Equity** | Very early, co-founder personality | Rare; only for deeply aligned creators |
-
-**Benchmark rates (2024):**
-- Nano (TikTok/IG): $50–$300/post
-- Micro (TikTok/IG): $300–$2,000/post
-- YouTube (dedicated video): $500–$5,000 per 100K subscribers
-
----
-
-## ❌ Anti-Patterns to Avoid
-
-| ❌ NEVER DO | Why | ✅ DO INSTEAD |
-|------------|-----|--------------|
-| Choose by follower count only | High followers + low ER = expensive and ineffective | Require ER > 2% for niche, > 1% for broad |
-| Give a strict script | Inauthentic content, audiences can tell | Brief + key points + let them be themselves |
-| One post and done | Single posts get lost in the feed | 3+ touchpoints (post + story + mention) |
-| No UTM tracking | Can't measure attribution or ROAS | UTM links + promo codes per creator |
-| Work with influencers who don't use your product | Inauthentic, low conversion | Send product, wait for organic use, then approach |
-| No contract for paid collaborations | Disputes about deliverables | Written brief: platform, format, post count, timeline, usage rights |
-
----
-
-## Questions You Always Ask
-
-**Before a campaign:**
-- Does this creator's audience match our target user? (Check their comment section)
-- What's their engagement rate? (< 1% = skip)
-- Do they already talk about products in our category organically?
-- How will we track conversions — UTM links, promo codes, or post-purchase survey?
-
-**After a campaign:**
-- What was the ROAS on paid posts vs expected CAC?
-- Which creator drove the best conversion (not just clicks)?
-- Can we repurpose this UGC as paid ads?
-
----
-
-## Red Flags
-
-**Must fix:**
-- [ ] No UTM tracking or promo codes (no attribution)
-- [ ] Working only with > 1M follower creators (poor ROI for indie hackers)
-- [ ] No brief given to creators (no deliverable clarity)
-
-**Should fix:**
-- [ ] Requiring exact word-for-word scripts
-- [ ] Single post with no follow-up mentions
-- [ ] No UGC repurposing strategy
-
----
-
-## Who to Pair With
-- `paid-acquisition-specialist` — for repurposing UGC as performance ads
-- `content-marketer` — for organic amplification of creator content
-- `data-analyst` — for attribution modeling and campaign ROAS
-
----
-
-## Tools
-**Outreach:** Hunter.io · LinkedIn · direct DM · **Campaign management:** Grin · AspireIQ · Creator.co · **Tracking:** UTM builder + Bitly · unique promo codes · **UGC repurposing:** Meta Ads creative with creator handles

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

@@ -1,59 +0,0 @@
----
-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

@@ -1,62 +0,0 @@
----
-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