mango-lollipop 0.1.0 → 0.1.1

package/{skills → .claude/skills}/audit/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: Audit
+description: Deep analysis of existing lifecycle messaging with maturity scorecard
+---
+
 # Audit Existing Lifecycle Messaging
 
 You are a lifecycle messaging auditor. Your job is to perform a deep analysis of a company's existing messaging system, score its maturity, identify gaps, and provide actionable recommendations for improvement.
@@ -220,9 +225,9 @@ For each gap, suggest specific messages to fill it:
 
 ## File Output
 
-If an `analysis.json` exists in the project directory, update it with audit results in the `existing` field.
+If an `analysis.json` exists in the current directory, update it with audit results in the `existing` field.
 
-If running standalone (no existing project), write the audit results to `{project-directory}/audit-results.json` with this structure:
+If running standalone (no existing project), write the audit results to `audit-results.json` with this structure:
 
 ```json
 {
@@ -245,4 +250,6 @@ If running standalone (no existing project), write the audit results to `{projec
 
 After presenting the audit, ask: "Would you like me to generate a complete matrix that incorporates your existing messages and fills these gaps? I'll preserve what's working and improve what isn't."
 
-If yes, proceed to run the `generate-matrix` skill with the audit data.
+If yes, proceed to run `/generate-matrix` with the audit data.
+
+$ARGUMENTS

package/{skills → .claude/skills}/dev-handoff/SKILL.md

@@ -1,15 +1,18 @@
+---
+name: Dev Hand-Off
+description: Generate developer hand-off documents (introduction email + technical event spec)
+---
+
 # Generate Developer Hand-Off Documents
 
 You are a technical documentation specialist bridging the gap between lifecycle marketing and engineering. Your job is to extract all product events from the messaging matrix, infer their payload schemas, and produce two deliverables: an introduction email marketing can send to the dev team, and a detailed technical event implementation spec.
 
 ## Input
 
-Read from the project output directory:
+Read from the current directory:
 1. **`analysis.json`** -- Company info, channels, voice profile, event taxonomy
 2. **`matrix.json`** -- All messages with triggers, guards, suppressions
 
-Locate the project output directory by checking the current working directory or `output/*/` subdirectories.
-
 ---
 
 ## Step 1: Extract Events
@@ -167,7 +170,7 @@ The complete technical spec with payload schemas, code examples, and implementat
 [Friendly sign-off matching the brand voice]
 ```
 
-Write to `{project-directory}/dev-handoff-email.md`.
+Write to `dev-handoff-email.md`.
 
 ---
 
@@ -282,7 +285,7 @@ A table of all user profile attributes extracted from guard/suppression expressi
   </footer>
   ```
 
-Write to `{project-directory}/event-spec.html`.
+Write to `event-spec.html`.
 
 ---
 
@@ -293,3 +296,5 @@ After generating both files:
 1. Tell the user: "Your developer hand-off documents are ready."
 2. Summarize: "[N] events extracted, [N critical / N high / N medium / N low]. The email draft is in `dev-handoff-email.md` and the full technical spec is in `event-spec.html`."
 3. Suggest: "Open `event-spec.html` in a browser to review the full spec. Edit `dev-handoff-email.md` to customize the email before sending it to your engineering team."
+
+$ARGUMENTS

package/{skills → .claude/skills}/generate-dashboard/SKILL.md

@@ -1,16 +1,19 @@
+---
+name: Generate Dashboard
+description: Create journey map, interactive dashboard, and executive overview
+---
+
 # Generate Visual Deliverables
 
 You are a lifecycle messaging visualization specialist. Your job is to create three visual outputs from the messaging matrix: an interactive HTML dashboard, a message preview viewer, and a printable executive overview.
 
 ## Input
 
-Read from the project output directory:
+Read from the current directory:
 1. **`analysis.json`** -- Company info, channels, voice profile
 2. **`matrix.json`** -- All messages with triggers, guards, suppressions, channels, tags
 3. **`messages/`** directory -- Individual message files (for preview content in dashboard)
 
-Locate the project output directory by checking the current working directory or `output/*/` subdirectories.
-
 ---
 
 ## Output A: Interactive Dashboard (`dashboard.html`)
@@ -75,7 +78,7 @@ Filters across sections use AND logic (stage AND channel AND tag must match).
   </footer>
   ```
 
-Write the output to `{project-directory}/dashboard.html`.
+Write the output to `dashboard.html`.
 
 ---
 
@@ -107,7 +110,7 @@ Each message renders in a visual template matching its channel:
 - If copy hasn't been generated yet, the viewer shows a placeholder with the message's comments and a note to run `generate-messages`.
 - Content is parsed from markdown files: `## Email`, `## In-App`, `## SMS`, `## Push Notification` sections.
 
-Write the output to `{project-directory}/messages.html`.
+Write the output to `messages.html`.
 
 ---
 
@@ -171,7 +174,7 @@ Create a clean, printable HTML page designed for sharing with stakeholders.
   6. RF messages (growth)
   7. Remaining AC messages
 
-Write the output to `{project-directory}/overview.html`.
+Write the output to `overview.html`.
 
 ---
 
@@ -183,7 +186,7 @@ Generate all outputs by running the following commands:
 npm run build && node bin/mango-lollipop.js export visuals
 ```
 
-This creates three files in the project output directory:
+This creates three files in the project directory:
 - `dashboard.html` -- Interactive dashboard with filters and sorting
 - `messages.html` -- Channel-specific message previews with hash routing
 - `overview.html` -- Printable executive overview
@@ -193,3 +196,5 @@ After the command succeeds:
 1. Update `mango-lollipop.json` to set `stage: "visuals-generated"`
 2. Tell the user: "Your visual deliverables are ready. Open `dashboard.html` in a browser for the interactive view, click any message to see the full preview in `messages.html`, or share `overview.html` as a printable summary."
 3. Suggest: "You can run `mango-lollipop view` to open the dashboard in your default browser."
+
+$ARGUMENTS

package/{skills → .claude/skills}/generate-matrix/SKILL.md

@@ -1,7 +1,14 @@
+---
+name: Generate Matrix
+description: Build the AARRR lifecycle matrix from analysis.json
+---
+
 # Generate Lifecycle Matrix
 
 You are a lifecycle messaging architect. Your job is to build the complete messaging matrix from a business analysis, producing a structured JSON file that contains every message the business needs -- both transactional and lifecycle.
 
+Look for `analysis.json` in the current directory.
+
 ## CRITICAL RULE: One Channel Per Message
 
 **Every message entry must target exactly ONE channel.** Email and in-app are different mediums with different copy, length, and format. Never combine them.
@@ -16,15 +23,10 @@ This applies to all stages. Sequential IDs are assigned per stage across all cha
 
 ## Input
 
-Read `analysis.json` from the project output directory. This file was produced by the `start` skill and contains the company profile, channels, voice, events, tags, and (for PATH B) existing messages.
+Read `analysis.json` from the current directory. This file was produced by the `start` skill and contains the company profile, channels, voice, events, tags, and (for PATH B) existing messages.
 
 Also read `templates/copywriting-guide.md` for proven sequence patterns. Use the "Applying Patterns to AARRR Stages" section to choose the best pattern for each stage based on the product type. For example, use the Guided Training pattern for activation if the product has a clear step-by-step workflow, or the Progress Milestones pattern if the product has a checklist-style onboarding.
 
-Locate the project output directory by:
-1. Checking the current working directory for `analysis.json`
-2. Checking `output/*/analysis.json`
-3. If not found, ask the user where their project directory is
-
 ---
 
 ## Step 1: Generate Transactional Messages (TX) -- Always
@@ -239,7 +241,7 @@ Add any custom tags suggested in `analysis.tags` that are relevant.
 
 ## Output: matrix.json
 
-Write `matrix.json` to the project output directory (same directory as `analysis.json`).
+Write `matrix.json` to the current directory (same directory as `analysis.json`).
 
 Structure:
 
@@ -344,7 +346,7 @@ Run the following commands to compile the TypeScript library and generate `matri
 npm run build && node bin/mango-lollipop.js export excel
 ```
 
-This creates a 6-sheet Excel workbook in the project output directory alongside `matrix.json`:
+This creates a 6-sheet Excel workbook in the project directory alongside `matrix.json`:
 1. **Welcome** — Cover sheet with project info (company, channels, message count) and a guide to each tab
 2. **Transactional Messages** — TX messages with gray row fills
 3. **Lifecycle Matrix** — AARRR messages with stage-colored row fills (green=AQ, blue=AC, yellow=RV, orange=RT, purple=RF)
@@ -372,3 +374,5 @@ Show a summary table to the user:
 | RF    | 2     | email, in-app | 2 new                     |
 
 Mention that `matrix.xlsx` was generated and is ready to open.
+
+$ARGUMENTS

package/{skills → .claude/skills}/generate-messages/SKILL.md

@@ -1,21 +1,21 @@
+---
+name: Generate Messages
+description: Write full message copy in the brand's voice (batched by 10)
+---
+
 # Generate Message Copy
 
 You are a lifecycle messaging copywriter. Your job is to write full, production-ready message copy for every message in the lifecycle matrix, matching the brand's voice exactly and following channel-specific requirements.
 
 ## Input
 
-Read from the project output directory:
+Read from the current directory:
 1. **`analysis.json`** -- For voice profile, sender personas, company context, and channel preferences
 2. **`matrix.json`** -- For the list of messages to write, with their triggers, guards, channels, and metadata
 3. **`templates/copywriting-guide.md`** -- Reference guide with proven SaaS email patterns, copy rules, anti-patterns, and benchmarks. Read this before writing any copy and apply its principles throughout.
 
 The copywriting guide contains real-world sequence patterns (Guided Training, Behavior-Driven Nudging, Progress Milestones, etc.) and rules for structure, subject lines, CTAs, and tone. Follow these closely.
 
-Locate the project output directory by:
-1. Checking the current working directory for these files
-2. Checking `output/*/analysis.json`
-3. If not found, ask the user
-
 ---
 
 ## Voice Matching Rules
@@ -125,7 +125,7 @@ Each stage writes to its own directory (`messages/{STAGE}/`) — zero file confl
 1. **Prepare** — Read `matrix.json` and group messages by stage. Read `analysis.json` and `templates/copywriting-guide.md` for voice profile and copy rules.
 2. **Spawn team** — Use `TeamCreate` to create a team, then `TaskCreate` for each stage that has messages. Spawn one writer agent per stage using the `Task` tool with `subagent_type: "general-purpose"` and `team_name` set to the team.
 3. **Each agent's task description must include:**
-   - The project output directory path
+   - The project directory path
    - The list of message IDs to write for that stage
    - The full voice profile parameters (tone, formality, emoji usage, sample phrases, sender personas)
    - Channel-specific requirements (from the "Channel-Specific Requirements" section above)
@@ -178,7 +178,7 @@ For messages with `origin: "improved"`:
 
 For each message, create a markdown file at:
 ```
-{project-directory}/messages/{STAGE}/{ID}-{slug}.md
+messages/{STAGE}/{ID}-{slug}.md
 ```
 
 Where:
@@ -259,4 +259,6 @@ After all messages are generated:
 1. Present a final summary: total messages written, broken down by stage and channel
 2. Note any messages that were skipped (e.g., channel not available)
 3. Update `mango-lollipop.json` to set `stage: "messages-generated"`
-4. Tell the user: "All message copy has been generated. Run the `generate-dashboard` skill next to create the journey map and dashboard."
+4. Tell the user: "All message copy has been generated. Run `/generate-dashboard` next to create the dashboard and journey map."
+
+$ARGUMENTS

package/{skills → .claude/skills}/iterate/SKILL.md

@@ -1,3 +1,8 @@
+---
+name: Iterate
+description: Modify the lifecycle matrix conversationally (add, remove, change messages)
+---
+
 # Iterate on Lifecycle Matrix
 
 You are a lifecycle messaging architect helping the user refine their messaging matrix through conversation. You apply requested changes to the matrix, regenerate affected files, and show the user exactly what changed.
@@ -6,14 +11,12 @@ You are a lifecycle messaging architect helping the user refine their messaging
 
 ## Input
 
-Read from the project output directory:
+Read from the current directory:
 1. **`mango-lollipop.json`** -- Project config
 2. **`matrix.json`** -- Current message matrix
 3. **`analysis.json`** -- Business analysis (for voice profile, company context)
 4. **`messages/`** directory -- Existing message files
 
-Locate the project output directory by checking the current working directory or `output/*/` subdirectories.
-
 ---
 
 ## Supported Modifications
@@ -226,7 +229,7 @@ After any change that modifies `matrix.json`, regenerate the Excel export to kee
 npm run build && node bin/mango-lollipop.js export excel
 ```
 
-Do NOT regenerate visual files (dashboard.html, overview.html) automatically. Instead, tell the user: "Matrix and message files updated. Run the `generate-dashboard` skill to update the dashboard."
+Do NOT regenerate visual files (dashboard.html, overview.html) automatically. Instead, tell the user: "Matrix and message files updated. Run `/generate-dashboard` to update the dashboard."
 
 ---
 
@@ -237,6 +240,8 @@ After applying changes:
 2. Run `npm run build && node bin/mango-lollipop.js export excel` to regenerate the Excel file
 3. Show the diff summary
 4. Confirm: "matrix.xlsx has been updated to reflect the latest changes."
-5. If the changes affect the dashboard, suggest running `generate-dashboard`
+5. If the changes affect the dashboard, suggest running `/generate-dashboard`
 6. Remain available for additional changes -- do not close the conversation
 7. Ask: "Anything else you'd like to change?"
+
+$ARGUMENTS

package/{skills → .claude/skills}/start/SKILL.md

@@ -1,9 +1,16 @@
+---
+name: Start
+description: Start a new Mango Lollipop project — analyze your SaaS business for lifecycle messaging
+---
+
 # Analyze Business for Lifecycle Messaging
 
 You are a lifecycle marketing strategist analyzing a SaaS business to build a complete lifecycle messaging system. Your job is to gather all the information needed to generate a great messaging matrix using the AARRR pirate metrics framework.
 
 Before starting, read `templates/copywriting-guide.md` for the Three-Track Model (Quick Win → Hook → Conversion) and proven sequence patterns from real SaaS companies. Use this knowledge to inform your recommendations and event taxonomy suggestions.
 
+All output files go in the current working directory.
+
 ## Step 0: Determine User Path
 
 Ask the user:
@@ -214,12 +221,7 @@ Record their primary goal. This will drive prioritization in the matrix generati
 
 ## Output: analysis.json
 
-After completing all steps, write the analysis to the project output directory as `analysis.json`.
-
-Determine the project output directory by:
-1. Looking for an existing `mango-lollipop.json` config file in the current working directory or `output/` subdirectories
-2. If none exists, ask the user for the project name and use `output/{project-name}/`
-3. Create the directory structure if it doesn't exist: `output/{project-name}/messages/{TX,AQ,AC,RV,RT,RF}/`
+After completing all steps, write the analysis to `analysis.json` in the current working directory.
 
 Write `analysis.json` with this schema:
 
@@ -307,4 +309,6 @@ After writing the file, present a summary to the user:
 - For PATH A: Show the number of transactional + lifecycle messages that will be generated, broken down by stage and channel. Ask "Ready to generate?"
 - For PATH B: Show a maturity scorecard (score per AARRR stage 0-5), identified gaps, and the plan (how many messages to keep, improve, and add new). Ask "Ready to generate?"
 
-Also update the `mango-lollipop.json` config file in the project directory to set `stage: "analyzed"` and `path` to the chosen path.
+Also update the `mango-lollipop.json` config file to set `stage: "analyzed"` and `path` to the chosen path.
+
+$ARGUMENTS

package/CLAUDE.md

@@ -11,7 +11,7 @@ The authoritative spec is `mango-lollipop-spec.md` at the project root. Always c
 ## Architecture
 
 ### Skills-based design
-The core logic lives in Claude Code skills under `skills/`, each with a `SKILL.md`:
+The core logic lives in Claude Code skills under `.claude/skills/`:
 - **start** — Gather business info via dual-path onboarding (fresh vs. existing messaging)
 - **generate-matrix** — Build the AARRR lifecycle matrix from analysis output
 - **generate-messages** — Write full message copy in the brand's voice (batched by 10)
@@ -52,6 +52,7 @@ mango-lollipop audit                 # Audit existing messaging
 mango-lollipop view                  # Open dashboard.html in browser
 mango-lollipop export excel|html|messages
 mango-lollipop status                # Message counts per stage, channel distribution, tags
+mango-lollipop update                # Update to the latest version from npm
 
 ```
 

package/README.md

@@ -37,6 +37,9 @@ It builds on proven industry templates, copywriting frameworks, and lifecycle be
 # Install
 npm install -g mango-lollipop
 
+# Update to the latest version
+mango-lollipop update
+
 # Initialize a project
 mango-lollipop init my-company
 
@@ -217,14 +220,14 @@ This trigger/wait/guard/suppression model gives you precise control over when me
 ```
 mango-lollipop/
 ├── bin/                        # CLI entry point
-├── skills/                     # Claude Code skills
-│   ├── start/                  # Business analysis + onboarding
-│   ├── generate-matrix/        # Matrix generation
-│   ├── generate-messages/      # Message copy writing
-│   ├── generate-dashboard/     # Dashboard + journey maps
-│   ├── audit/                  # Existing messaging audit
-│   ├── dev-handoff/            # Developer hand-off documents
-│   └── iterate/                # Conversational refinement
+├── .claude/skills/             # Claude Code slash commands (skills)
+│   ├── start/SKILL.md         # Business analysis + onboarding
+│   ├── generate-matrix/SKILL.md     # Matrix generation
+│   ├── generate-messages/SKILL.md   # Message copy writing
+│   ├── generate-dashboard/SKILL.md  # Dashboard + journey maps
+│   ├── audit/SKILL.md         # Existing messaging audit
+│   ├── dev-handoff/SKILL.md   # Developer hand-off documents
+│   └── iterate/SKILL.md       # Conversational refinement
 ├── templates/                  # Output templates + event taxonomies
 │   └── events/                 # Industry-specific event templates
 ├── lib/                        # Shared utilities (schema, excel, html, mermaid)

package/bin/mango-lollipop.js

@@ -1,7 +1,8 @@
 #!/usr/bin/env node
 
 import { Command } from 'commander';
-import { existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync } from 'fs';
+import { execSync } from 'child_process';
+import { cpSync, existsSync, mkdirSync, readFileSync, readdirSync, writeFileSync } from 'fs';
 import { resolve, join, dirname } from 'path';
 import { fileURLToPath } from 'url';
 import open from 'open';
@@ -105,7 +106,7 @@ function countBy(arr) {
 program
   .name('mango-lollipop')
   .description('AI-powered lifecycle messaging generator')
-  .version('0.1.0');
+  .version(JSON.parse(readFileSync(join(__dirname, '..', 'package.json'), 'utf-8')).version);
 
 // --- init -------------------------------------------------------------------
 
@@ -113,7 +114,7 @@ program
   .command('init [name]')
   .description('Initialize a new Mango Lollipop project')
   .action((name = 'my-project') => {
-    const dir = resolve(`output/${name}`);
+    const dir = resolve(name);
     mkdirSync(dir, { recursive: true });
 
     // Create message folders per stage
@@ -121,6 +122,22 @@ program
       mkdirSync(`${dir}/messages/${stage}`, { recursive: true });
     }
 
+    // Copy skills, templates, and Claude Code commands from the package
+    const pkgRoot = resolve(__dirname, '..');
+    const toCopy = [
+      ['templates', 'templates'],
+      ['.claude/skills', '.claude/skills'],
+      ['CLAUDE.md', 'CLAUDE.md'],
+    ];
+
+    for (const [src, dest] of toCopy) {
+      const srcPath = join(pkgRoot, src);
+      const destPath = join(dir, dest);
+      if (existsSync(srcPath)) {
+        cpSync(srcPath, destPath, { recursive: true });
+      }
+    }
+
     // Create initial config
     const config = {
       name,
@@ -137,9 +154,9 @@ program
 
     console.log(`Mango Lollipop project "${name}" initialized at ${dir}`);
     console.log();
-    console.log('Next step: Run the start skill in Claude Code:');
-    console.log(`  cd ${dir}`);
-    console.log('  claude "Read the start skill and help me set up lifecycle messaging"');
+    console.log('Next step:');
+    console.log(`  cd ${name}`);
+    console.log('  /start');
   });
 
 // --- generate ---------------------------------------------------------------
@@ -380,6 +397,43 @@ program
     }
   });
 
+// --- update -----------------------------------------------------------------
+
+program
+  .command('update')
+  .description('Update mango-lollipop to the latest version')
+  .action(() => {
+    const pkg = JSON.parse(readFileSync(join(__dirname, '..', 'package.json'), 'utf-8'));
+    const current = pkg.version;
+
+    let latest;
+    try {
+      latest = execSync('npm view mango-lollipop@latest version', { encoding: 'utf-8' }).trim();
+    } catch {
+      console.log('Could not reach the npm registry. Check your internet connection.');
+      return;
+    }
+
+    if (current === latest) {
+      console.log(`Already on the latest version (${current}).`);
+      return;
+    }
+
+    console.log(`Current version: ${current}`);
+    console.log(`Latest version:  ${latest}`);
+    console.log();
+    console.log('Updating...');
+
+    try {
+      execSync('npm install -g mango-lollipop@latest', { stdio: 'inherit' });
+      console.log();
+      console.log(`Updated to ${latest}.`);
+    } catch {
+      console.log('Update failed. Try running manually:');
+      console.log('  npm install -g mango-lollipop@latest');
+    }
+  });
+
 // --- parse ------------------------------------------------------------------
 
 program.parse();

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mango-lollipop",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "description": "AI-powered lifecycle messaging generator for SaaS companies",
   "license": "MIT",
@@ -23,7 +23,7 @@
   "files": [
     "bin/",
     "dist/",
-    "skills/",
+    ".claude/skills/",
     "templates/",
     "lib/",
     "CLAUDE.md"