vibebusiness 1.2.80 → 1.2.83

package/.next/standalone/templates/commands/setup-payments.md

@@ -0,0 +1,107 @@
+# /setup-payments — Stripe Payment Integration Wizard
+
+## Usage
+```
+/setup-payments              # Full setup wizard (detect framework → install SDK → validate key → create products → generate code)
+/setup-payments checkout     # Generate only checkout session endpoint
+/setup-payments webhook      # Generate only webhook handler
+/setup-payments portal       # Generate only customer portal redirect
+/setup-payments status       # Check integration completeness
+```
+
+## Input
+- `$ARGUMENTS` — optional: one of the modes above (defaults to full setup)
+
+## Process
+
+Parse `$ARGUMENTS` to determine mode. If empty or "setup", run the full wizard.
+
+---
+
+### Mode: Full Setup (default)
+
+Runs the complete Stripe integration wizard:
+
+1. **Detect Framework**: Reads `package.json` to identify Next.js (App/Pages Router), Express, Fastify, Remix, or generic Node.js. Checks for TypeScript and `src/` directory.
+
+2. **Install Stripe SDK**: If `stripe` is not in `node_modules`, runs `npm install stripe`.
+
+3. **Validate API Key**: Reads `STRIPE_SECRET_KEY` from `.env` or environment. Calls `stripe.accounts.retrieve()` to validate.
+   - If missing: prints instructions to add it and stops.
+   - If invalid: prints error and stops.
+
+4. **Create Products**: Searches for existing products to avoid duplicates. If none found, creates a default "Pro Plan" ($29/mo).
+
+5. **Generate Code**: Creates framework-appropriate files:
+   - Checkout session endpoint
+   - Webhook handler (with `constructEvent` signature verification)
+   - Customer portal redirect
+   - Checkout button component (Next.js only)
+   - **Never overwrites existing files** — skips with a warning.
+
+6. **Update .env**: Appends `STRIPE_SECRET_KEY` and `STRIPE_WEBHOOK_SECRET` if not present. Ensures `.env` is in `.gitignore`.
+
+7. **Save State**: Writes integration status to `data/payments.json`.
+
+---
+
+### Mode: `checkout`
+
+Generates only the checkout session creation endpoint for the detected framework.
+
+---
+
+### Mode: `webhook`
+
+Generates only the webhook handler with Stripe signature verification.
+
+---
+
+### Mode: `portal`
+
+Generates only the customer portal redirect endpoint.
+
+---
+
+### Mode: `status`
+
+Audits the current integration:
+- Is Stripe SDK installed?
+- Is the API key valid?
+- Do products exist in Stripe?
+- Are checkout/webhook/portal endpoints generated?
+- Is the webhook secret configured?
+
+Reports completeness as a percentage.
+
+---
+
+## State File
+
+`data/payments.json` tracks:
+```json
+{
+  "last_updated": "2025-01-15T...",
+  "integration_status": {
+    "sdk_installed": true,
+    "api_key_valid": true,
+    "products_created": true,
+    "checkout_endpoint": true,
+    "webhook_endpoint": true,
+    "portal_endpoint": false
+  },
+  "framework": { "framework": "nextjs", "typescript": true, "appRouter": true, "srcDir": true },
+  "products": [
+    { "name": "Pro Plan", "stripe_product_id": "prod_...", "stripe_price_id": "price_...", "amount_cents": 2900, "currency": "usd", "interval": "month" }
+  ],
+  "generated_files": ["src/app/api/checkout/route.ts", "src/app/api/webhook/route.ts"]
+}
+```
+
+## Error Handling
+
+- Missing `STRIPE_SECRET_KEY` → return instructions to add it to `.env`
+- Invalid key → return `success: false` with "check your key" message
+- Products already exist → skip creation, use existing IDs
+- Target file exists → skip with warning (don't overwrite user code)
+- Framework not detected → fall back to generic Node.js templates

package/.next/standalone/templates/commands/setup-posthog.md

@@ -0,0 +1,116 @@
+# /setup-posthog — PostHog Analytics Integration Wizard
+
+## Usage
+```
+/setup-posthog              # Full setup (detect → install → validate → generate → configure KPI adapter → suggest events)
+/setup-posthog provider     # Generate only PostHogProvider + pageview tracker
+/setup-posthog events       # Generate only event tracking helper
+/setup-posthog status       # Check integration completeness
+/setup-posthog connect-kpis # Scan codebase for events, map them to KPIs
+```
+
+## Input
+- `$ARGUMENTS` — optional: one of the modes above (defaults to full setup)
+
+## Process
+
+Parse `$ARGUMENTS` to determine mode. If empty or "setup", run the full wizard.
+
+---
+
+### Mode: Full Setup (default)
+
+Runs the complete PostHog analytics integration wizard:
+
+1. **Detect Framework**: Reads `package.json` to identify Next.js (App/Pages Router), Express, Fastify, Remix, or generic Node.js. Checks for TypeScript and `src/` directory.
+
+2. **Install SDK**: If `posthog-js` is not in `node_modules`, runs `npm install posthog-js`. For non-Next.js frameworks, also installs `posthog-node`.
+
+3. **Validate API Key**: Reads `NEXT_PUBLIC_POSTHOG_KEY` (Next.js) or `POSTHOG_API_KEY` (other) from `.env` or environment. Validates key format (must start with `phc_`).
+   - If missing: prints instructions to add it and continues (key can be added later).
+   - If invalid format: prints warning.
+   - If valid: calls PostHog API to verify the key works.
+
+4. **Generate Tracking Code**: Creates framework-appropriate files:
+   - **Next.js App Router**: `PostHogProvider.tsx`, `PostHogPageview.tsx`, `posthog-events.ts`
+   - **Next.js Pages Router**: `lib/posthog.ts`, `_app.tsx` integration instructions
+   - **Generic (Express, etc.)**: `lib/posthog.ts` (posthog-node client)
+   - **Never overwrites existing files** — skips with a warning.
+
+5. **Update .env**: Appends PostHog key and host variables if not present. Ensures `.env` is in `.gitignore`.
+
+6. **Configure KPI Adapter**: Adds a `posthog` adapter entry to `data/business-context.json` so the KPI dashboard can pull metrics from PostHog. Skips if already configured.
+
+7. **Suggest Starter Events**: Recommends framework-specific events to track (e.g., `signed_up`, `feature_used`, `upgrade_clicked`, `cta_clicked`). Provides code snippets for adding them.
+
+---
+
+### Mode: `provider`
+
+Generates only the PostHogProvider component and pageview tracker for the detected framework. Useful if you already have the SDK installed and key configured but need the React components.
+
+---
+
+### Mode: `events`
+
+Generates only the event tracking helper file (`posthog-events.ts` or `lib/posthog.ts`). Useful for adding typed event tracking to an existing PostHog setup.
+
+---
+
+### Mode: `status`
+
+Audits the current integration:
+- Is PostHog SDK installed?
+- Is the API key configured?
+- Is the key format valid?
+- Are generated files present (Provider, Pageview, events helper)?
+- Is the KPI adapter configured in business-context.json?
+
+Reports completeness as a percentage.
+
+---
+
+### Mode: `connect-kpis`
+
+Scans the user's codebase for PostHog event calls and maps them to KPIs:
+
+1. **Find Events**: Searches for `posthog.capture('...')`, `trackEvent('...')`, and `client.capture({ event: '...' })` patterns across `.ts`, `.tsx`, `.js`, `.jsx` files. Ignores `node_modules`, `dist`, and `$`-prefixed internal events.
+
+2. **Read Existing KPIs**: Loads KPI definitions from `data/goals.json`.
+
+3. **Generate Mappings**: Creates `kpi-{event-name}` → `event_name` field mappings.
+
+4. **Update Adapter**: Writes the field mappings to the PostHog adapter in `data/business-context.json`. Creates the adapter if it doesn't exist.
+
+5. **Report**: Lists detected events, existing KPIs, and suggested mappings.
+
+---
+
+## State File
+
+`data/posthog.json` tracks:
+```json
+{
+  "last_updated": "2026-01-15T...",
+  "integration_status": {
+    "sdk_installed": true,
+    "api_key_valid": true,
+    "provider_generated": true,
+    "pageview_tracker": true,
+    "event_helper": false
+  },
+  "framework": { "framework": "nextjs", "typescript": true, "appRouter": true, "srcDir": true },
+  "generated_files": ["src/components/PostHogProvider.tsx", "src/components/PostHogPageview.tsx"]
+}
+```
+
+## Error Handling
+
+- Missing `NEXT_PUBLIC_POSTHOG_KEY` → prints instructions to add it to `.env`, continues setup
+- Invalid key format (not `phc_...`) → prints warning, continues
+- API key validation fails → prints error, continues (key can be fixed later)
+- SDK install fails → returns failure with manual install instructions
+- Target file already exists → skips with warning (never overwrites user code)
+- Framework not detected → falls back to generic Node.js templates
+- `business-context.json` missing → skips KPI adapter step with hint to run `vibebusiness init`
+- No PostHog events found in codebase → reports zero and suggests running `posthog-setup` first

package/.next/standalone/templates/commands/social-media.md

@@ -0,0 +1,47 @@
+# Social Media — Twitter/X Build-in-Public
+
+Run social media tasks for your project. This skill manages Twitter/X tweet drafts in a draft-then-confirm workflow.
+
+## Available actions: $ARGUMENTS
+
+### Setup
+```
+social-setup-x
+```
+Validates X API credentials from .env and saves the connected username.
+
+### Generate Drafts
+```
+social-draft-ship       # Tweet about the most recently shipped feature
+social-draft-update     # Product update from positioning data
+social-draft-milestone  # Celebrate a KPI that hit its target
+social-draft-digest     # Weekly recap of activity
+```
+
+### Check Status
+```
+social-check-status     # Audit credentials, draft count, post streak
+```
+
+## Instructions
+
+1. Read `data/social.json` to understand current state
+2. Based on the user's request ($ARGUMENTS), execute the appropriate task by running:
+   ```
+   npx tsx scripts/heartbeat.ts --execute-task <task-id>
+   ```
+   Or if that flag doesn't exist, call the skill directly:
+   ```typescript
+   import { executeSocialTask } from './scripts/skills/social-media';
+   const result = await executeSocialTask('<task-id>', '<description>');
+   ```
+3. Report the result back to the user
+4. If generating drafts, remind the user they can review and publish from the /social dashboard
+
+## Environment Variables Required
+- `X_API_KEY` — Consumer API key
+- `X_API_SECRET` — Consumer API secret
+- `X_ACCESS_TOKEN` — User access token
+- `X_ACCESS_SECRET` — User access token secret
+
+Get these at https://developer.x.com/en/portal/dashboard

package/.next/standalone/templates/commands/status-summary.md

@@ -0,0 +1,103 @@
+# /status-summary — State Overview Dashboard
+
+## Usage
+```
+/status-summary              # Full overview of all data
+/status-summary ideas        # Ideas breakdown only
+/status-summary goals        # Goals progress only
+/status-summary hypotheses   # Hypotheses status only
+/status-summary stale        # Only show stale/attention items
+```
+
+## Input
+- `$ARGUMENTS` — optional: specific section to focus on (`ideas`, `goals`, `hypotheses`, `stale`)
+
+## Process
+
+### Step 1: Load Data
+Read the relevant data files based on `$ARGUMENTS`:
+- If no argument or `stale`: read `data/ideas.json`, `data/goals.json`, `data/hypotheses.json`
+- If `ideas`: read only `data/ideas.json`
+- If `goals`: read only `data/goals.json`
+- If `hypotheses`: read only `data/hypotheses.json`
+
+### Step 2: Generate Summary
+
+#### Ideas Section
+Count ideas by stage and format as a pipeline:
+
+```
+📦 Ideas Pipeline (N total)
+───────────────────────────
+inbox:        N  ██░░░░░░
+under_review: N  █░░░░░░░
+approved:     N  ██░░░░░░
+in_progress:  N  ███░░░░░
+testing:      N  █░░░░░░░
+shipped:      N  █████░░░
+deferred:     N
+rejected:     N
+```
+
+Also show:
+- **Critical priority items**: list any ideas with `priority: "critical"`
+- **Stale inbox items**: ideas in `inbox` stage where `created_at` is more than 7 days ago
+- **In-progress without updates**: ideas in `in_progress` where `updated_at` is more than 14 days ago
+
+#### Goals Section
+For each goal, show progress:
+
+```
+🎯 Goals (N total)
+───────────────────
+[status emoji] goal-001: "Lawyer Success"
+   Category: activation | Status: behind
+   Progress: 0 / 25 (0%)
+   KPIs:
+     • First Response Rate: 56.9% → target 90% ⚠️
+     • Response Time: 64.45h → target 4h ⚠️
+```
+
+Status emojis: ✅ on_track, ⚠️ at_risk, 🔴 behind, 🏆 achieved
+
+#### Hypotheses Section
+Count hypotheses by status:
+
+```
+🧪 Hypotheses (N total)
+───────────────────────
+stated:      N
+testing:     N
+validated:   N
+invalidated: N
+deferred:    N
+```
+
+List any hypotheses in `stated` status older than 14 days (not yet tested).
+
+#### Stale Data Alerts
+Flag data freshness issues:
+- `data/business-context.json` → check `last_manual_update`, alert if > 30 days ago
+- `data/competitors.json` → check `last_updated`, alert if > 30 days ago
+- `data/sessions.json` → check most recent session date, alert if > 7 days ago
+
+```
+⏰ Freshness Alerts
+───────────────────
+⚠️ Business context last updated 45 days ago (2026-01-02)
+✅ Competitors data is fresh (updated 3 days ago)
+⚠️ No analysis sessions in the last 7 days
+```
+
+### Step 3: Output
+Print the full dashboard. This is a **read-only** command — no files are modified.
+
+If issues are found, suggest `/manage` commands to fix them:
+```
+💡 Suggested actions:
+  /manage move idea-old-001 to deferred (stuck in inbox 30 days)
+  /manage update goal-001 status to at_risk
+```
+
+## Output Files
+- None (read-only command)

package/.next/standalone/templates/commands/validate-idea.md

@@ -0,0 +1,102 @@
+# /validate-idea — Pre-Build Validation
+
+## Usage
+```
+/validate-idea "Add a referral program for existing users"
+/validate-idea "Build an API for third-party integrations"
+/validate-idea "Launch a mobile app"
+```
+
+## Input
+- `$ARGUMENTS` — **required**: the idea to validate
+
+## Process
+
+### Step 1: Parse Idea
+Extract from `$ARGUMENTS`:
+- Core idea description
+- Implied audience (if mentioned)
+- Implied scope (feature, product, channel)
+
+### Step 2: Codebase Check
+Search the codebase to see if this (or something similar) already exists:
+- Use Glob to search for related file names
+- Use Grep to search for related functionality
+- Check `data/ideas.json` for similar existing ideas
+- Check `data/hypotheses.json` for related hypotheses
+
+If something similar exists, note it and assess whether the idea is:
+- **Duplicate** — already exists or already proposed
+- **Extension** — builds on existing functionality
+- **New** — genuinely novel
+
+### Step 3: Competitor Check
+Load `data/competitors.json` and check:
+- Do competitors offer this? Which ones?
+- How do they implement it?
+- Is it a differentiator or table stakes?
+
+If no competitor data, WebSearch:
+- `"[competitor name] [idea keyword]"` for top 3 competitors
+
+### Step 4: Market Demand Check
+WebSearch for demand signals:
+- `"[idea keyword] demand"` or `"[idea keyword] need"`
+- `"[product category] users want [idea]"`
+- Check for feature request patterns on review sites, forums
+
+### Step 5: Score the Idea
+Score on three dimensions (1-5 each):
+
+1. **Desirability** (Do users want it?)
+   - Evidence from search results, competitor adoption, user feedback
+   - Score 5: strong demand signals
+   - Score 1: no evidence of demand
+
+2. **Feasibility** (Can we build it?)
+   - Technical complexity assessment from codebase check
+   - Dependencies and prerequisites
+   - Score 5: straightforward with existing tech
+   - Score 1: requires major new infrastructure
+
+3. **Viability** (Will it make money?)
+   - Revenue potential or retention impact
+   - Alignment with current business model
+   - Score 5: direct revenue impact
+   - Score 1: no clear business case
+
+### Step 6: Recommendation
+Based on scores, recommend:
+
+- **GO** (avg score >= 4): Strong idea, proceed to implementation
+- **INVESTIGATE** (avg score 2.5-3.9): Promising but needs more data
+- **STOP** (avg score < 2.5): Evidence doesn't support this idea
+
+### Step 7: Create Artifacts
+If GO or INVESTIGATE:
+- Create a hypothesis in `data/hypotheses.json`:
+  ```json
+  {
+    "title": "[Idea title]",
+    "statement": "If we [build this], then [metric] will [change] because [evidence]",
+    "funnel_stage": "[appropriate stage]",
+    "priority": "[based on score]",
+    "effort_to_test": "[estimate]",
+    "tags": ["validation"]
+  }
+  ```
+
+### Step 8: Output
+Print:
+- Idea summary
+- Codebase check results (existing / extension / new)
+- Competitor landscape (who does this, how)
+- Demand evidence
+- Score breakdown (desirability / feasibility / viability)
+- **Recommendation: GO / INVESTIGATE / STOP**
+- Evidence summary
+- Hypothesis created (if applicable)
+- Suggested next steps
+
+## Output Files
+- `data/hypotheses.json` — validation hypothesis (if GO or INVESTIGATE)

package/.next/standalone/templates/emails/__tests__/validate-templates.test.ts

@@ -0,0 +1,147 @@
+import * as fs from "fs";
+import * as path from "path";
+
+const TEMPLATES_DIR = path.resolve(__dirname, "..");
+
+describe("day3-activation-feedback.txt", () => {
+  const filePath = path.join(TEMPLATES_DIR, "day3-activation-feedback.txt");
+  let content: string;
+
+  beforeAll(() => {
+    if (!fs.existsSync(filePath)) {
+      throw new Error(
+        `Template file missing: ${filePath}. Expected file to exist at templates/emails/day3-activation-feedback.txt`
+      );
+    }
+    content = fs.readFileSync(filePath, "utf-8");
+  });
+
+  it("has a non-empty Subject line", () => {
+    const match = content.match(/^Subject:\s*(.+)$/m);
+    expect(match).not.toBeNull();
+    const subject = match![1].trim();
+    expect(subject.length).toBeGreaterThan(0);
+  });
+
+  it("contains the {{first_name}} placeholder", () => {
+    expect(content).toContain("{{first_name}}");
+  });
+
+  it("has a word count under 150", () => {
+    // Strip the Subject line before counting body words
+    const body = content.replace(/^Subject:.*$/m, "").trim();
+    const wordCount = body.split(/\s+/).filter((w) => w.length > 0).length;
+    expect(wordCount).toBeLessThan(150);
+  });
+});
+
+describe("day30-pmf-feedback.txt", () => {
+  const filePath = path.join(TEMPLATES_DIR, "day30-pmf-feedback.txt");
+  let content: string;
+
+  beforeAll(() => {
+    if (!fs.existsSync(filePath)) {
+      throw new Error(
+        `Template file missing: ${filePath}. Expected file to exist at templates/emails/day30-pmf-feedback.txt`
+      );
+    }
+    content = fs.readFileSync(filePath, "utf-8");
+  });
+
+  it("has the required Subject line", () => {
+    const match = content.match(/^Subject:\s*(.+)$/m);
+    if (!match) {
+      throw new Error(
+        "Missing required element: Subject line not found. Expected a line starting with 'Subject:'"
+      );
+    }
+    const subject = match[1].trim();
+    if (subject.length === 0) {
+      throw new Error(
+        "Missing required element: Subject line is empty. Expected non-empty subject text"
+      );
+    }
+    expect(subject.length).toBeGreaterThan(0);
+  });
+
+  it("contains the {{first_name}} placeholder", () => {
+    if (!content.includes("{{first_name}}")) {
+      throw new Error(
+        "Missing required element: {{first_name}} placeholder not found in template"
+      );
+    }
+    expect(content).toContain("{{first_name}}");
+  });
+
+  it("contains Sean Ellis option a) Very disappointed", () => {
+    if (!content.includes("a) Very disappointed")) {
+      throw new Error(
+        "Missing required element: Sean Ellis answer option 'a) Very disappointed' not found in template"
+      );
+    }
+    expect(content).toContain("a) Very disappointed");
+  });
+
+  it("contains Sean Ellis option b) Somewhat disappointed", () => {
+    if (!content.includes("b) Somewhat disappointed")) {
+      throw new Error(
+        "Missing required element: Sean Ellis answer option 'b) Somewhat disappointed' not found in template"
+      );
+    }
+    expect(content).toContain("b) Somewhat disappointed");
+  });
+
+  it("contains Sean Ellis option c) Not disappointed", () => {
+    if (!content.includes("c) Not disappointed")) {
+      throw new Error(
+        "Missing required element: Sean Ellis answer option 'c) Not disappointed' not found in template"
+      );
+    }
+    expect(content).toContain("c) Not disappointed");
+  });
+
+  it("has a word count under 200", () => {
+    const body = content.replace(/^Subject:.*$/m, "").trim();
+    const wordCount = body.split(/\s+/).filter((w) => w.length > 0).length;
+    if (wordCount >= 200) {
+      throw new Error(
+        `Missing required element: word count constraint violated. Body has ${wordCount} words but must be under 200`
+      );
+    }
+    expect(wordCount).toBeLessThan(200);
+  });
+});
+
+describe("feedback-playbook.md", () => {
+  const playbookPath = path.resolve(__dirname, "../../../docs/feedback-playbook.md");
+  let content: string;
+
+  const REQUIRED_HEADINGS = [
+    "## Purpose",
+    "## Templates",
+    "## Trigger",
+    "## Sending Instructions",
+    "## Reading Responses",
+    "## Future Automation",
+  ];
+
+  beforeAll(() => {
+    if (!fs.existsSync(playbookPath)) {
+      throw new Error(
+        `Playbook file missing: ${playbookPath}. Expected file to exist at docs/feedback-playbook.md`
+      );
+    }
+    content = fs.readFileSync(playbookPath, "utf-8");
+  });
+
+  it("contains all required section headings", () => {
+    for (const heading of REQUIRED_HEADINGS) {
+      if (!content.includes(heading)) {
+        throw new Error(
+          `Missing required section heading: "${heading}" not found in docs/feedback-playbook.md`
+        );
+      }
+      expect(content).toContain(heading);
+    }
+  });
+});

package/.next/standalone/templates/emails/day3-activation-feedback.txt

@@ -0,0 +1,14 @@
+Subject: Quick question about your first days with VibeBusiness
+
+Hi {{first_name}},
+
+I'm the founder of VibeBusiness and I wanted to reach out personally.
+
+One quick question: what were you originally trying to accomplish when you signed up?
+
+Even a one-line answer helps me make VibeBusiness more useful for people like you.
+
+Just hit reply — I read every response.
+
+— Luis
+Founder, VibeBusiness

package/.next/standalone/templates/emails/day30-pmf-feedback.txt

@@ -0,0 +1,19 @@
+Subject: One question about VibeBusiness
+
+Hi {{first_name}},
+
+Quick question — it'll take 30 seconds.
+
+How would you feel if you could no longer use VibeBusiness?
+
+a) Very disappointed
+b) Somewhat disappointed
+c) Not disappointed
+
+If VibeBusiness disappeared tomorrow, what would you use instead?
+
+Just hit reply with your answer — no forms, no links.
+
+Thanks,
+Luís
+Founder, VibeBusiness