vibebusiness 1.2.38 → 1.2.39

package/dist/scripts/implement.js

@@ -152,6 +152,7 @@ var ROADMAP_FILE = path2.join(DATA_DIR, "roadmap.json");
 var COMPETITORS_FILE = path2.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path2.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path2.join(DATA_DIR, "pages.json");
+var PAYMENTS_FILE = path2.join(DATA_DIR, "payments.json");
 var TEMPLATES_DIR = path2.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path2.join(TEMPLATES_DIR, "commands");
 

package/dist/scripts/init.js

@@ -442,6 +442,7 @@ var ROADMAP_FILE = path6.join(DATA_DIR, "roadmap.json");
 var COMPETITORS_FILE = path6.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path6.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path6.join(DATA_DIR, "pages.json");
+var PAYMENTS_FILE = path6.join(DATA_DIR, "payments.json");
 var TEMPLATES_DIR = path6.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path6.join(TEMPLATES_DIR, "commands");
 

package/dist/scripts/scan.js

@@ -299,6 +299,7 @@ var ROADMAP_FILE = path2.join(DATA_DIR, "roadmap.json");
 var COMPETITORS_FILE = path2.join(DATA_DIR, "competitors.json");
 var POSITIONING_FILE = path2.join(DATA_DIR, "positioning.json");
 var PAGES_FILE = path2.join(DATA_DIR, "pages.json");
+var PAYMENTS_FILE = path2.join(DATA_DIR, "payments.json");
 var TEMPLATES_DIR = path2.join(__dirname, "..", "..", "templates");
 var COMMAND_TEMPLATES_DIR = path2.join(TEMPLATES_DIR, "commands");
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vibebusiness",
-  "version": "1.2.38",
+  "version": "1.2.39",
   "description": "AI-powered autonomous business analyst. Research. Build. Ship. Grow.",
   "license": "SEE LICENSE IN LICENSE",
   "private": false,

package/templates/commands/email-marketing.md

@@ -0,0 +1,201 @@
+# /email-marketing — Email Marketing Setup & Campaign Generator
+
+## Usage
+```
+/email-marketing setup                # Guided Loops.so setup wizard
+/email-marketing campaign welcome     # Generate a welcome email campaign
+/email-marketing campaign onboarding  # Generate an onboarding drip email
+/email-marketing campaign feature-announcement  # New feature announcement
+/email-marketing campaign re-engagement         # Win-back inactive users
+/email-marketing campaign milestone             # User achievement celebration
+/email-marketing sequence {name}      # Design a multi-email drip sequence
+/email-marketing blast {slug}         # Draft a one-off announcement email
+```
+
+## Input
+- `$ARGUMENTS` — required: one of the modes above
+
+## Process
+
+Parse `$ARGUMENTS` to determine mode. The first word is the mode, the rest are arguments.
+
+---
+
+### Mode: `setup`
+
+Interactive Loops.so setup wizard.
+
+1. **Check API Key**: Verify `LOOPS_API_KEY` is set in the environment
+   - If not set: print instructions to add it to `.env` and stop
+   - If set: call `GET /api/v1/api-key` to verify it's valid
+
+2. **Audit Current State**:
+   - List existing mailing lists via the Loops API
+   - List existing contact properties
+   - List existing transactional email templates
+   - Print a summary of what's already configured
+
+3. **Set Up Contact Properties**: Create recommended properties if they don't exist:
+   - `source` (string) — where the contact came from (e.g., "website", "twitter", "producthunt")
+   - `userGroup` (string) — segment (e.g., "beta_tester", "waitlist", "customer")
+   - `plan` (string) — pricing plan (e.g., "free", "pro", "enterprise")
+
+4. **Configure KPI Adapter**: Read `data/business-context.json` and check if a `loops` KPI adapter is configured. If not, add one:
+   ```json
+   {
+     "id": "loops",
+     "type": "loops",
+     "field_mapping": {
+       "kpi-waitlist-signups": "total_contacts"
+     }
+   }
+   ```
+
+5. **Print Summary**: What was set up, what was already configured, next steps (run `/email-marketing campaign welcome` to create first email).
+
+---
+
+### Mode: `campaign {type}`
+
+Generate an email campaign draft using positioning data and business context.
+
+Supported types: `welcome`, `onboarding`, `feature-announcement`, `re-engagement`, `milestone`
+
+1. **Load Context**:
+   - Read `data/positioning.json` — headlines, CTAs, pain points, objection handlers, brand voice
+   - Read `data/business-context.json` — product info, audience, value proposition
+   - Read `data/goals.json` — current business goals for relevance
+
+2. **Generate Campaign** based on type:
+
+   **`welcome`** — First email after signup:
+   - Subject line (3 variations)
+   - Preview text
+   - Body: warm greeting → what they signed up for → what to expect → single CTA
+   - Tone: enthusiastic but professional, use brand voice from positioning
+   - Include personalization tokens: `{{firstName}}`, `{{source}}`
+
+   **`onboarding`** — Guide new users to first value:
+   - Subject line (3 variations)
+   - Body: acknowledge signup → quickstart steps → link to docs → CTA to first action
+   - Focus on time-to-value messaging from positioning
+   - Include personalization: `{{firstName}}`
+
+   **`feature-announcement`** — New feature shipped:
+   - Subject line (3 variations)
+   - Body: what's new → why it matters → how to use it → CTA to try it
+   - Pull differentiators from positioning data
+   - If $ARGUMENTS includes an idea ID, load that idea for specific feature details
+
+   **`re-engagement`** — Win back inactive users:
+   - Subject line (3 variations)
+   - Body: we miss you → what's new since they left → special offer/incentive → CTA
+   - Use objection handlers from positioning to address likely reasons for leaving
+
+   **`milestone`** — Celebrate user achievements:
+   - Subject line (3 variations)
+   - Body: congratulations → what they achieved → what's next → CTA to share/upgrade
+   - Keep it short and celebratory
+
+3. **Write Output**: Save to `data/email-campaigns/{type}-{YYYY-MM-DD}.md` as structured markdown:
+   ```markdown
+   # {Type} Email Campaign — {Date}
+
+   ## Metadata
+   - Type: {type}
+   - Generated: {date}
+   - Positioning version: {last_updated from positioning.json}
+
+   ## Subject Lines
+   1. {subject1}
+   2. {subject2}
+   3. {subject3}
+
+   ## Preview Text
+   {preview}
+
+   ## Body
+
+   {full email body in markdown}
+
+   ## Loops Integration Notes
+   - Suggested event trigger: {event_name}
+   - Recommended mailing list: {list_name}
+   - Personalization tokens used: {list}
+   ```
+
+4. **Print Summary**: Preview of subject lines, word count, file path, suggestion to set up in Loops dashboard.
+
+---
+
+### Mode: `sequence {name}`
+
+Design a multi-email drip sequence.
+
+1. **Load Context**: Same as campaign mode — positioning, business context, goals.
+
+2. **Design Sequence**:
+   - Generate 3-5 emails with recommended timing (e.g., Day 0, Day 2, Day 5, Day 10, Day 14)
+   - Each email has: subject line, preview text, body, CTA
+   - Map a Loops event name to trigger each email
+   - Ensure narrative arc: introduce → educate → demonstrate value → convert → reinforce
+
+3. **Write Output**: Save to `data/email-campaigns/sequences/{name}.md`:
+   ```markdown
+   # {Name} Email Sequence
+
+   ## Overview
+   - Emails: {count}
+   - Duration: {total days}
+   - Goal: {sequence goal}
+   - Trigger event: {initial trigger}
+
+   ## Email 1: {title} (Day 0)
+   **Trigger:** {event_name}
+   **Subject:** {subject}
+   **Preview:** {preview}
+
+   {body}
+
+   ---
+
+   ## Email 2: {title} (Day 2)
+   ...
+   ```
+
+4. **Print Summary**: Sequence overview, timing chart, event names to configure in Loops.
+
+---
+
+### Mode: `blast {slug}`
+
+Draft a one-off announcement email.
+
+1. **Load Context**: Positioning data, business context. If slug matches an idea ID in `data/ideas.json`, load that idea for specific details.
+
+2. **Generate Email**:
+   - Subject line (3 variations)
+   - Preview text
+   - Body: announcement → details → why it matters → CTA
+   - Keep it concise — one-off emails should be scannable
+
+3. **Write Output**: Save to `data/email-campaigns/blasts/{slug}.md`
+
+4. **Print Summary**: Preview of subject lines, file path.
+
+---
+
+## Directory Structure
+
+Ensure these directories exist before writing (create if needed):
+```
+data/email-campaigns/
+├── sequences/
+└── blasts/
+```
+
+## Output Files
+- `data/email-campaigns/{type}-{date}.md` — campaign drafts
+- `data/email-campaigns/sequences/{name}.md` — drip sequences
+- `data/email-campaigns/blasts/{slug}.md` — one-off emails
+- `data/business-context.json` — updated with Loops KPI adapter (setup mode only)