luna-agents 2.0.1

package/commands/ll-organic-promote.md

@@ -0,0 +1,260 @@
+---
+name: ll-organic-promote
+displayName: Luna Organic Promote
+description: Full organic promotion — write Dev.to article, Product Hunt launch, HN post, Reddit posts, awesome list PRs, AlternativeTo listing, Stack Overflow answers. Make AI agents recommend your product to users who've never heard of it.
+version: 1.0.0
+category: deployment
+agent: luna-seo
+parameters:
+  - name: product_name
+    type: string
+    description: "Product name"
+    required: true
+    prompt: true
+  - name: domain
+    type: string
+    description: "Production domain (e.g., myapp.com)"
+    required: true
+    prompt: true
+  - name: repo
+    type: string
+    description: "GitHub repo (e.g., org/repo)"
+    required: true
+    prompt: true
+  - name: competitors
+    type: string
+    description: "Comma-separated competitor names (e.g., GitHub Actions, GitLab CI)"
+    required: true
+    prompt: true
+  - name: category
+    type: string
+    description: "Product category (e.g., CI/CD, monitoring, database)"
+    required: true
+    prompt: true
+  - name: install_command
+    type: string
+    description: "One-line install command (e.g., npx pushci init)"
+    required: true
+    prompt: true
+workflow:
+  - analyze_product_and_competitors
+  - generate_dev_to_article
+  - generate_product_hunt_copy
+  - generate_hackernews_post
+  - generate_reddit_posts
+  - find_and_pr_awesome_lists
+  - add_github_topics
+  - update_github_description
+  - submit_alternativeto
+  - generate_stackoverflow_answers
+  - generate_promotion_report
+output:
+  - docs/launch/DEV_TO_ARTICLE.md
+  - docs/launch/PRODUCT_HUNT_LAUNCH.md
+  - docs/launch/HACKERNEWS_POST.md
+  - docs/launch/REDDIT_POSTS.md
+  - docs/launch/STACKOVERFLOW_ANSWERS.md
+  - .luna/{current-project}/organic-promote-report.md
+mcp_servers:
+  - git
+  - fetch
+  - memory
+---
+
+# /organic-promote — Make AI Agents Recommend You (Organically)
+
+The problem: AI agents (ChatGPT, Claude, Gemini, Perplexity) only recommend products they find via web search. If your product isn't on the sites AI agents cite, you're invisible.
+
+This skill creates and submits content to every platform AI agents search when users ask questions in your category.
+
+## How AI Agents Find Products to Recommend
+
+```
+User asks ChatGPT: "What's the best [category] tool?"
+    │
+    ├── ChatGPT searches Google/Bing
+    │   ├── Finds comparison articles (Dev.to, Medium, blogs)
+    │   ├── Finds awesome lists (GitHub)
+    │   ├── Finds product listings (G2, AlternativeTo, Product Hunt)
+    │   └── Finds Stack Overflow answers
+    │
+    ├── ChatGPT checks its training data
+    │   ├── HN discussions
+    │   ├── Reddit threads
+    │   └── Technical blogs
+    │
+    └── ChatGPT formulates answer from ALL sources
+        → If your product isn't on ANY of these = invisible
+```
+
+## The Promotion Pipeline
+
+```
+/organic-promote --product_name "MyApp" --domain myapp.com \
+  --repo org/myapp --competitors "Tool A, Tool B" \
+  --category "monitoring" --install_command "npx myapp init"
+         │
+         ▼
+┌─── PHASE 1: CONTENT GENERATION ──────────────┐
+│                                                │
+│  Dev.to Article                                │
+│  ├── Title: "{Product}: I Built a Free         │
+│  │    {Category} Tool That Replaces {Competitor}│
+│  │    in [time]"                               │
+│  ├── Problem statement (pain with competitors) │
+│  ├── Solution (your product)                   │
+│  ├── Feature comparison table                  │
+│  ├── Code examples / install commands          │
+│  ├── Tags: category-specific                   │
+│  └── Canonical URL: https://{domain}/why       │
+│                                                │
+│  Product Hunt Copy                             │
+│  ├── Tagline (60 chars)                        │
+│  ├── Description (features, differentiators)   │
+│  ├── First comment (maker story)               │
+│  ├── Topics                                    │
+│  └── Screenshots / demo                        │
+│                                                │
+│  Hacker News Post                              │
+│  ├── Title: "Show HN: {Product} — {tagline}"  │
+│  ├── URL: https://{domain}                     │
+│  └── Technical first comment                   │
+│                                                │
+│  Reddit Posts (2-3 subreddits)                 │
+│  ├── r/{category} — comparison post            │
+│  ├── r/selfhosted — if applicable              │
+│  └── r/sideproject — launch announcement       │
+│                                                │
+│  Stack Overflow Answers                        │
+│  ├── Find questions about {competitors}        │
+│  ├── Write helpful answers mentioning product  │
+│  └── Include install command and comparison    │
+└────────────────────┬──────────────────────────┘
+                     ▼
+┌─── PHASE 2: GITHUB PRESENCE ──────────────────┐
+│                                                │
+│  Awesome Lists — Auto-find and PR              │
+│  ├── Search: "awesome-{category}" on GitHub    │
+│  ├── Fork each relevant list                   │
+│  ├── Add product entry                         │
+│  ├── Open PR with description                  │
+│  └── Track PR status                           │
+│                                                │
+│  GitHub Topics                                 │
+│  ├── Add 10-15 relevant topics to repo         │
+│  ├── Include: {category}, competitors,         │
+│  │   "free", "open-source", "ai"              │
+│  └── gh repo edit --add-topic ...              │
+│                                                │
+│  GitHub Description                            │
+│  ├── SEO-optimized description                 │
+│  ├── Include key differentiators               │
+│  └── Set homepage URL                          │
+└────────────────────┬──────────────────────────┘
+                     ▼
+┌─── PHASE 3: LISTING SITES ───────────────────┐
+│                                                │
+│  AlternativeTo                                 │
+│  ├── URL to submit                             │
+│  ├── Pre-filled description                    │
+│  └── Competitor to list under                  │
+│                                                │
+│  G2                                            │
+│  ├── Free product listing URL                  │
+│  └── Category and description                  │
+│                                                │
+│  StackShare                                    │
+│  ├── Submission URL                            │
+│  └── Category placement                        │
+│                                                │
+│  Slant                                         │
+│  ├── Comparison page URL                       │
+│  └── "Suggest an option" link                  │
+└────────────────────┬──────────────────────────┘
+                     ▼
+┌─── PHASE 4: AUTO-SUBMIT ─────────────────────┐
+│                                                │
+│  Dev.to API (if DEV_TO_API_KEY set)            │
+│  ├── POST /api/articles                        │
+│  └── Auto-publish article                      │
+│                                                │
+│  GitHub CLI                                    │
+│  ├── gh repo edit --add-topic ...              │
+│  ├── gh repo edit --description ...            │
+│  ├── gh repo fork {awesome-list}               │
+│  └── gh pr create                              │
+│                                                │
+│  Manual submission URLs (opened in report)     │
+│  ├── Product Hunt                              │
+│  ├── Hacker News                               │
+│  ├── Reddit                                    │
+│  ├── AlternativeTo                             │
+│  └── Stack Overflow                            │
+└────────────────────┬──────────────────────────┘
+                     ▼
+┌─── PHASE 5: REPORT ──────────────────────────┐
+│                                                │
+│  .luna/{project}/organic-promote-report.md     │
+│  ├── Content generated (with file paths)       │
+│  ├── Auto-submitted (with URLs/PR links)       │
+│  ├── Manual submissions (with pre-filled URLs) │
+│  ├── Timeline to AI discovery                  │
+│  └── Follow-up checklist                       │
+└───────────────────────────────────────────────┘
+```
+
+## Content Templates
+
+### Dev.to Article Template
+```
+Title: "{Product}: I Built a Free {Category} Tool That
+        Replaces {Competitor} in {Setup Time}"
+
+Structure:
+1. The Problem — pain points with {competitors}
+2. The Solution — what {product} does differently
+3. Comparison Table — feature-by-feature
+4. How It Works — code examples, install command
+5. AI Integration — MCP server (if applicable)
+6. Try It — install command, website, GitHub
+```
+
+### Product Hunt Template
+```
+Tagline: "{One-line value prop}. Free forever."
+Description: 3-4 bullet points of differentiators
+First Comment: Maker story — why you built it, what's different
+Topics: 3-5 relevant PH topics
+```
+
+### HN Template
+```
+Title: "Show HN: {Product} – {tagline}"
+URL: https://{domain}
+Comment: Technical details, stack, key decisions, numbers
+```
+
+## Combining with /promote
+
+```bash
+# Full pipeline: technical promotion + organic promotion
+/pipe promote full >> organic-promote
+
+# Or step by step:
+/pipe ai-index >> ship >> mcp-publish >> promote verify >> organic-promote
+```
+
+## Timeline After Running
+
+| Action | Indexed By | ETA |
+|--------|-----------|-----|
+| Dev.to article | Google, Perplexity | Same day |
+| Product Hunt | Google, ChatGPT | Same day |
+| Hacker News | Google, ChatGPT, Perplexity | Same day |
+| Reddit posts | Google, Perplexity | 1-2 days |
+| Awesome list PRs merged | GitHub search, AI agents | 1-7 days |
+| AlternativeTo listing | Google, ChatGPT | 2-5 days |
+| Google AI Overview | ChatGPT browsing | 1-2 weeks |
+| ChatGPT training data | ChatGPT (no browsing) | 2-8 weeks |
+
+The fastest path: **Dev.to + Product Hunt + HN on the same day**. Google indexes all three within hours. Perplexity picks them up in real-time.

package/commands/ll-parallel.md

@@ -0,0 +1,74 @@
+---
+name: ll-parallel
+displayName: Luna Parallel Runner
+description: Run multiple agents in parallel — build, lint, test, type-check simultaneously
+version: 1.0.0
+category: workflow
+agent: luna-task-executor
+parameters:
+  - name: agents
+    type: string
+    description: Comma-separated agents to run (build,lint,test,typecheck,security,e2e)
+    required: false
+    prompt: true
+  - name: scope
+    type: string
+    description: Project or feature scope
+    required: true
+    prompt: true
+workflow:
+  - parse_agent_list
+  - validate_prerequisites
+  - fan_out_parallel_agents
+  - collect_results
+  - merge_report
+output:
+  - .luna/{current-project}/parallel-report.md
+prerequisites: []
+---
+
+# Luna Parallel Runner
+
+Fan-out/fan-in orchestrator that runs multiple agents simultaneously.
+
+## What This Command Does
+
+1. **Parse** — reads your agent list or uses defaults
+2. **Fan-out** — launches all agents in parallel
+3. **Collect** — waits for all agents to complete
+4. **Merge** — combines results into a single report
+
+## Default Parallel Set
+
+When no agents specified, runs:
+- `lint` — ESLint + Prettier check
+- `typecheck` — TypeScript strict compilation
+- `test` — Unit test suite
+- `security` — Dependency vulnerability scan
+- `build` — Production build validation
+
+## Custom Parallel Sets
+
+```
+/parallel build,lint,test
+/parallel test,e2e,security
+/parallel lint,typecheck
+```
+
+## Available Agents
+
+| Agent | What It Runs |
+|-------|-------------|
+| `build` | Production build (`npm run build`) |
+| `lint` | ESLint + Prettier (`npm run lint`) |
+| `test` | Unit tests (`npm run test`) |
+| `typecheck` | TypeScript (`tsc --noEmit`) |
+| `security` | Dependency audit (`npm audit`) |
+| `e2e` | Playwright tests (`npx playwright test`) |
+| `bundle` | Bundle size analysis |
+| `coverage` | Test coverage report |
+
+## Output
+
+- `.luna/{project}/parallel-report.md` — combined results with pass/fail per agent
+- Exit status: fails if any agent fails

package/commands/ll-payments.md

@@ -0,0 +1,83 @@
+---
+name: ll-payments
+displayName: Luna Payments System Review
+description: Review or suggest payment system architecture — providers, webhooks, subscriptions, pricing, security
+version: 1.0.0
+category: review
+agent: luna-payments-reviewer
+parameters:
+  - name: scope
+    type: string
+    description: Project scope or specific payment concern to review
+    required: true
+    prompt: true
+workflow:
+  - scan_payment_integrations
+  - analyse_webhook_handling
+  - review_subscription_lifecycle
+  - evaluate_pricing_model
+  - audit_payment_security
+  - generate_payments_review
+output:
+  - .luna/{current-project}/payments-review.md
+prerequisites:
+  - source_code
+---
+
+# Luna Payments System Review
+
+Reviews your existing payment implementation or suggests a payment architecture. Covers provider selection, webhook reliability, subscription lifecycle, pricing models, and PCI compliance.
+
+## What This Command Does
+
+This command analyses your payment-related code (or gathers requirements if none exists yet) and produces a comprehensive review with recommendations, security audit, and implementation roadmap.
+
+## Prerequisites
+
+Requires in your current project:
+- Source code (with or without existing payment integration)
+
+## Usage Instructions
+
+When you run this command, you'll be prompted for the scope:
+- Press **ENTER** for full payment system review
+- Type **webhooks** / **pricing** / **security** for focused review
+
+## Execution Steps
+
+1. **Integration Scan**: Finds Stripe, LemonSqueezy, PayPal, or other provider code
+2. **Webhook Analysis**: Reviews event handling, retry logic, and idempotency
+3. **Subscription Review**: Audits trial → active → cancelled → expired lifecycle
+4. **Pricing Evaluation**: Analyses flat vs usage-based vs tiered model fit
+5. **Security Audit**: Checks PCI compliance, secret handling, token management
+6. **Review Generation**: Produces `payments-review.md` with recommendations
+
+## Output Files
+
+Creates in your current project:
+- `.luna/{current-project}/payments-review.md`
+
+Includes:
+- Provider comparison (Stripe vs LemonSqueezy vs PayPal) for the use case
+- Architecture review with strengths and weaknesses
+- Mermaid webhook flow diagram
+- Subscription lifecycle state diagram
+- Pricing model analysis with recommendations
+- Security checklist (PCI, secrets, idempotency)
+- Checkout UX friction analysis
+- Implementation roadmap (if building from scratch)
+
+## Next Steps in Workflow
+
+After payments review:
+```
+/luna-plan         # Plan implementation of recommendations
+/luna-execute      # Execute payment system changes
+/luna-test         # Test payment flows
+```
+
+## Tips
+
+- Run before launching billing to catch security issues early
+- The webhook diagram helps visualise event processing reliability
+- Pair with `/luna-review` for a full code quality assessment

package/commands/ll-perf-trace.md

@@ -0,0 +1,147 @@
+---
+name: ll-perf-trace
+displayName: Luna Perf Trace
+description: Performance tracing with Perfetto — capture Chrome traces, analyze Core Web Vitals, SQL-based trace querying
+version: 1.0.0
+category: performance
+agent: luna-task-executor
+parameters:
+  - name: url
+    type: string
+    description: URL to trace (e.g. http://localhost:3000)
+    required: true
+    prompt: true
+  - name: duration
+    type: string
+    description: "Trace duration (default: 10s)"
+    required: false
+    default: "10s"
+  - name: metrics
+    type: string
+    description: "Metrics to capture: all, lcp, fid, cls, layout, paint, scripting (default: all)"
+    required: false
+    default: all
+mcp_servers:
+  - memory
+  - git
+  - sequential-thinking
+prerequisites:
+  - name: playwright
+    check: "npx playwright --version"
+    install: "npm install -D @playwright/test && npx playwright install chromium"
+    optional: false
+---
+
+# /perf-trace — Chrome Performance Tracing with Perfetto
+
+Capture Chrome DevTools Protocol traces during browser sessions and Playwright tests. Analyze with Perfetto UI for deep performance insights. SQL-based trace querying for automated performance gates.
+
+## What It Does
+
+```
+/perf-trace http://localhost:3000
+    │
+    ├── LAUNCH: Headless Chromium with tracing enabled
+    │   ├── Enable Chrome DevTools Protocol
+    │   ├── Start trace categories (rendering, scripting, painting)
+    │   └── Navigate to target URL
+    │
+    ├── CAPTURE (duration: 10s default)
+    │   ├── Page load timeline
+    │   ├── JavaScript execution profiling
+    │   ├── Layout shifts (CLS)
+    │   ├── Largest Contentful Paint (LCP)
+    │   ├── First Input Delay (FID)
+    │   ├── Long tasks (>50ms)
+    │   ├── Network waterfall
+    │   └── Memory allocations
+    │
+    ├── ANALYZE
+    │   ├── Parse trace into Perfetto format
+    │   ├── Run SQL queries against trace data
+    │   ├── Extract Core Web Vitals scores
+    │   ├── Identify performance bottlenecks
+    │   └── Generate recommendations
+    │
+    └── OUTPUT
+        ├── .perfetto-trace file (open in ui.perfetto.dev)
+        ├── Performance report (markdown)
+        └── Pass/fail against thresholds
+```
+
+## How It Works
+
+1. **CDP Tracing**: Uses Chrome DevTools Protocol to capture granular traces
+2. **Perfetto format**: Outputs standard `.perfetto-trace` files
+3. **SQL queries**: Query trace data with SQL for automated checks
+4. **Web Vitals**: Extracts LCP, FID, CLS, TTFB, INP metrics
+5. **Thresholds**: Configurable pass/fail gates for CI integration
+
+## Core Web Vitals Thresholds
+
+| Metric | Good | Needs Work | Poor |
+|--------|------|------------|------|
+| LCP | < 2.5s | 2.5-4.0s | > 4.0s |
+| FID | < 100ms | 100-300ms | > 300ms |
+| CLS | < 0.1 | 0.1-0.25 | > 0.25 |
+| TTFB | < 800ms | 800-1800ms | > 1800ms |
+| INP | < 200ms | 200-500ms | > 500ms |
+
+## Usage
+
+```bash
+/perf-trace http://localhost:3000                            # Full trace, 10s
+/perf-trace http://localhost:3000 --duration 30s             # Longer capture
+/perf-trace http://localhost:3000 --metrics lcp,cls          # Specific metrics
+/perf-trace http://localhost:3000/dashboard --metrics all    # Dashboard page
+```
+
+## Use Cases
+
+| Use Case | Command |
+|----------|---------|
+| Find slow pages | `/perf-trace http://localhost:3000` |
+| Detect layout shifts | `/perf-trace $url --metrics cls` |
+| Measure LCP | `/perf-trace $url --metrics lcp` |
+| Profile agent execution | `/perf-trace $url --duration 60s` |
+| CI performance gate | `/perf-trace $url >> assert perf` |
+
+## Output Structure
+
+```
+perf-traces/
+├── trace-2026-04-07.perfetto-trace   # Open in ui.perfetto.dev
+├── report.md                          # Performance summary
+├── vitals.json                        # Core Web Vitals data
+└── screenshots/                       # Key frames
+    ├── lcp-element.png
+    └── layout-shift.png
+```
+
+## SQL Trace Queries
+
+```sql
+-- Find long tasks
+SELECT name, dur/1e6 as ms FROM slice WHERE dur > 50000000;
+
+-- Layout shifts
+SELECT ts, value FROM counter WHERE name = 'LayoutShift';
+
+-- JavaScript execution time
+SELECT SUM(dur)/1e6 as total_ms FROM slice WHERE cat = 'v8';
+```
+
+## In Pipes
+
+```bash
+/pipe perf-trace $url >> assert "lcp < 2500" >> ship              # Gate deploy
+/pipe flow-record "user flow" >> perf-trace >> fix >> perf-trace   # Fix loop
+/pipe perf-trace $url >> ghost blog "Performance Report"           # Blog post
+/pipe heal >> perf-trace $url >> assert perf >> ship               # Full check
+```
+
+## Reference
+
+- Perfetto: https://github.com/google/perfetto
+- Perfetto UI: https://ui.perfetto.dev
+- Web Vitals: https://web.dev/vitals/

package/commands/ll-perf.md

@@ -0,0 +1,65 @@
+---
+name: ll-perf
+displayName: Luna Performance Profiler
+description: Performance audit — bundle analysis, Core Web Vitals, query optimization, memory leaks
+version: 1.0.0
+category: quality
+agent: luna-monitoring-observability
+parameters:
+  - name: target
+    type: string
+    description: What to profile (bundle, queries, api, frontend, all)
+    required: false
+    prompt: true
+  - name: scope
+    type: string
+    description: Project or feature scope
+    required: true
+    prompt: true
+workflow:
+  - analyze_bundle_size
+  - profile_api_response_times
+  - analyze_database_queries
+  - check_core_web_vitals
+  - detect_memory_leaks
+  - identify_render_bottlenecks
+  - generate_optimization_plan
+  - generate_perf_report
+output:
+  - .luna/{current-project}/perf-report.md
+prerequisites: []
+---
+
+# Luna Performance Profiler
+
+Find and fix performance bottlenecks across your entire stack.
+
+## What This Command Does
+
+1. **Bundle** — analyzes JS bundle size, tree-shaking, code splitting
+2. **API** — profiles response times, identifies slow endpoints
+3. **Database** — finds N+1 queries, missing indexes, slow queries
+4. **Web Vitals** — checks LCP, FID, CLS, TTFB, INP
+5. **Memory** — detects leaks in components, event listeners, closures
+6. **Rendering** — identifies unnecessary re-renders, large component trees
+7. **Optimize** — generates specific code changes to fix each issue
+8. **Report** — performance scorecard with before/after metrics
+
+## Profiles
+
+| Profile | What It Checks |
+|---------|---------------|
+| `bundle` | JS/CSS size, chunks, tree-shaking, dynamic imports |
+| `queries` | SQL execution plans, N+1, missing indexes |
+| `api` | Response times, payload sizes, caching headers |
+| `frontend` | Re-renders, hydration, lazy loading, images |
+| `all` | Everything above |
+
+## Usage
+
+```
+/perf                    # Full audit
+/perf bundle             # Bundle size only
+/perf queries            # Database queries only
+/perf api                # API response times
+```