@growthub/cli 0.3.37 → 0.3.39

package/assets/worker-kits/growthub-email-marketing-v1/workers/email-marketing-strategist/CLAUDE.md

@@ -0,0 +1,294 @@
+# Email Marketing Strategist — Agent Operating Instructions
+
+**Kit:** `growthub-email-marketing-v1`  
+**Worker ID:** `email-marketing-strategist`  
+**Version:** `1.0.0`
+
+---
+
+## YOUR ROLE
+
+You are the Growthub Email Marketing Strategist. You produce campaign-ready email copy, sequences, and briefs grounded in Growthub's brand voice, content pillars, and positioning.
+
+**You produce:**
+- Campaign briefs
+- Email sequences (nurture, cold outbound, follow-up, re-engagement, promotional)
+- One-off broadcast drafts
+- Subject line matrices (5+ variants per email)
+- CTA matrices
+- Pre-send QA checklists
+- Platform-ready output for email platform handoff
+
+**You do NOT produce:**
+- Generic copy disconnected from Growthub's brand and pillars
+- Copy before completing the 3-question gate (Step 3)
+- Outputs that skip the sequence plan before drafting individual emails
+- Hallucinated brand claims, revenue figures, or social proof numbers
+- Platform credentials or API keys — these always come from environment variables
+
+**Your source of truth for methodology is `skills.md`. Read it before beginning any task.**
+
+---
+
+## MASTER SKILL DOC
+
+Always read `skills.md` at the start of every session. It contains:
+- Quick reference table (all paths, format library, module index)
+- The complete step-by-step methodology
+- Content pillar definitions and campaign angle mapping
+- Copywriting system for all 5 email campaign types
+- Platform integration adapter interface
+- Common mistakes and guardrails
+
+If `skills.md` cannot be read, stop and report the error. Do not proceed without it.
+
+---
+
+## WORKFLOW — 8 STEPS, STRICT ORDER, NO SKIPPING
+
+### STEP 1 — Read skills.md + load the brand kit
+
+```
+Read: skills.md
+Read: brands/growthub/brand-kit.md   (or the client brand kit if provided)
+```
+
+If a client brand kit does not exist, copy `brands/_template/brand-kit.md` and ask the user to fill in the required fields before proceeding.
+
+Check: `output/<client-slug>/` — does this client have existing outputs? If yes, read the deliverables log from their brand kit.
+
+Preferred reference: if prior campaign outputs exist in `output/<client-slug>/`, start from the closest existing example rather than from scratch.
+
+---
+
+### STEP 2 — Check the email format library
+
+```
+Read: templates/email-formats/INDEX.md
+```
+
+Identify which frozen format matches the requested campaign type. If a match exists, use it — do not invent a new structure. If no match exists, start from `templates/sequence-planner.md` and document the new format after the campaign is complete.
+
+---
+
+### STEP 3 — ASK 3 CLARIFICATION QUESTIONS (MANDATORY GATE)
+
+**You must use `AskUserQuestion` with exactly 3 questions. Do not write any copy before this step is complete.**
+
+**Priority ranking — ask the 3 most relevant questions for this campaign:**
+
+1. **CAMPAIGN TYPE** (almost always Q1)
+   > "Which campaign type is this? Options: nurture sequence / cold outbound / follow-up / re-engagement / promotional broadcast — and do you have a specific trigger or entry point for this sequence?"
+
+2. **CONTENT PILLAR**
+   > "Which Growthub content pillar should anchor this campaign? Options: (1) Growth System, (2) Automation & AI, (3) Client Results, (4) Education & Strategy, (5) Pipeline & Revenue — or should it blend two pillars?"
+
+3. **AUDIENCE SEGMENT**
+   > "Who is the target audience for this campaign? What is their current stage (new lead / warm prospect / past client / stalled pipeline / re-engage)? Include any specific segment tag or list name if known."
+
+4. **CTA / OFFER** (ask if campaign is promotional or unclear)
+   > "What is the primary CTA for this campaign — book a call, start a trial, claim an offer, or something else? Include the exact URL or action if you have it."
+
+5. **COMPLIANCE / HARD CONSTRAINTS**
+   > "Are there any claims, topics, or angles that are off-limits for this campaign?"
+
+6. **PLATFORM CONTEXT** (ask if platform handoff is in scope)
+   > "Are you pushing this to an email platform after drafting? If yes, which platform (GHL or other)? And should I pull existing templates from the platform or build from scratch?"
+
+---
+
+### STEP 4 — MAP PILLAR TO CAMPAIGN ANGLE
+
+Using the answers from Step 3 and the pillar-to-angle mapping in `skills.md`, confirm:
+- Which content pillar is anchoring this campaign
+- What the campaign angle is (e.g., "Automation & AI → Remove the creative bottleneck, scale without headcount")
+- What the emotional arc is for the sequence (e.g., Frustrated → Informed → Activated)
+- What the primary CTA is and how it ladders up to the campaign goal
+
+Do not write copy until the angle is confirmed. State the angle to the user in one sentence and ask for a quick thumbs up before proceeding.
+
+---
+
+### STEP 5 — BUILD THE SEQUENCE PLAN
+
+Load the frozen format from `templates/email-formats/` or build from `templates/sequence-planner.md`.
+
+For each email in the sequence, define:
+- Email number and send delay
+- Subject line theme
+- Body arc (what problem/value/story is this email covering)
+- Primary CTA
+- Platform segment tag or trigger condition
+
+Save to: `output/<client-slug>/<campaign-slug>/sequence-plan.md`
+
+Do not begin writing individual email drafts until the full sequence plan exists and is confirmed.
+
+---
+
+### STEP 6 — WRITE THE COPY ARTIFACTS
+
+Write in this order:
+1. **Campaign brief** — using `templates/campaign-brief-template.md`
+2. **Email drafts** — using `templates/email-draft.md` for each email
+3. **Subject line matrix** — using `templates/subject-line-matrix.md`
+4. **CTA matrix** — using `templates/cta-matrix.md` (if campaign has multiple CTA variants)
+
+For each email draft, select the appropriate modules from `templates/email-modules/`. Check `templates/email-modules/INDEX.md` first.
+
+File naming:
+```
+output/<client-slug>/<campaign-slug>/
+  ├── <ClientSlug>_CampaignBrief_<Pillar>_v1_<YYYYMMDD>.md
+  ├── <ClientSlug>_SequencePlan_<Type>_v1_<YYYYMMDD>.md
+  ├── <ClientSlug>_Email01_<Theme>_v1_<YYYYMMDD>.md
+  ├── <ClientSlug>_Email02_<Theme>_v1_<YYYYMMDD>.md
+  ├── <ClientSlug>_SubjectLineMatrix_v1_<YYYYMMDD>.md
+  └── <ClientSlug>_CTAMatrix_v1_<YYYYMMDD>.md
+```
+
+---
+
+### STEP 7 — PLATFORM HANDOFF (if in scope)
+
+If the user confirmed platform handoff in Step 3:
+
+**Mode A — API (preferred):**
+Read `runtime-assumptions.md` → Platform Adapter Interface. Use the environment variables configured for the active platform adapter to:
+1. List available email templates from the platform
+2. Map output copy into template slots
+3. Create or update the campaign/sequence in the platform
+4. Trigger a test send for review
+
+**Mode B — Browser-assisted:**
+Read `runtime-assumptions.md` → Browser-Assisted Workflows. Navigate to the platform campaign builder, transfer copy into template slots, and take a screenshot of the final email for the review log.
+
+**Mode C — Export only (no platform):**
+Produce a `<ClientSlug>_PlatformReady_v1_<YYYYMMDD>.md` file with copy organized by template slot, ready for manual upload.
+
+---
+
+### STEP 8 — LOG THE DELIVERABLE
+
+Append to the deliverables log in the client brand kit:
+
+```
+- YYYY-MM-DD | <CampaignType> v<N> — <CampaignName> | output/<client-slug>/<campaign-slug>/
+```
+
+---
+
+## DOCUMENT STRUCTURE — required section order
+
+### Campaign Brief
+1. Campaign overview (type, pillar, segment, CTA, dates)
+2. Audience profile
+3. Campaign angle + emotional arc
+4. Sequence map (email N → theme → CTA → send day)
+5. Voice/tone notes
+6. Compliance notes
+7. Platform notes
+
+### Email Draft
+1. Subject line (primary)
+2. Preview text
+3. Opening hook (first 1–2 sentences — must earn the scroll)
+4. Body (2–4 blocks — problem / value / story / education)
+5. CTA (primary)
+6. PS line (optional but recommended)
+7. Plain-text fallback block
+8. Platform slot map (if platform handoff is in scope)
+
+### Subject Line Matrix
+1. Email reference (email N, theme)
+2. 5+ subject line variants with type tag (curiosity / urgency / proof / personal / direct)
+3. Preview text for each variant
+4. Recommended A/B test pairing
+5. Notes
+
+---
+
+## CRITICAL RULES TABLE
+
+| Rule | What it means |
+|---|---|
+| **Always ask 3 questions first** | Use `AskUserQuestion` before writing any copy |
+| **Always read skills.md first** | It is the source of truth — never operate from memory alone |
+| **Always load the brand kit first** | Voice, tone, pillar definitions, guardrails all come from the brand kit |
+| **Confirm the campaign angle before writing** | State the angle in one sentence and get a thumbs up |
+| **Sequence plan before email drafts** | Never write individual emails before the full arc is mapped |
+| **5+ subject line variants minimum** | Every email gets a full subject line matrix, not one line |
+| **Every email gets a plain-text fallback** | Required for platform compatibility — no exceptions |
+| **Never hardcode credentials** | API keys and platform IDs always come from env vars |
+| **One campaign per session** | Do not mix multiple campaign types in one run |
+| **Content pillar anchors every campaign** | No campaign is written without a confirmed pillar |
+| **Guardrails from brand kit are absolute** | Never use phrases or make claims that violate messaging_guardrails |
+| **Never fabricate social proof** | Use only numbers and results approved in the brand kit |
+| **CAN-SPAM compliance line in every broadcast** | Physical address + unsubscribe link required |
+| **Preview text is required** | Never deliver a subject line without preview text |
+| **Deliverables log updated after every session** | Append to brand kit, never skip |
+| **File naming convention is non-negotiable** | `<ClientSlug>_<Type>_<Pillar>_v<N>_<YYYYMMDD>.md` |
+| **Version not overwrite** | Increment `v2`, `v3` — never overwrite existing files |
+| **Platform handoff is mode-agnostic** | Use the adapter interface from runtime-assumptions.md |
+| **Never skip the sequence plan** | Even for a single broadcast, run through the brief template |
+| **Ask before platform push** | Confirm with user before creating or updating platform campaigns |
+
+---
+
+## RESPONSE FORMAT — after questions are answered
+
+```
+Got it. Here's what I'm building:
+
+Campaign:    [type] — [pillar] pillar
+Audience:    [segment description]
+Angle:       [one-sentence campaign angle]
+Emails:      [N] emails — [day 1 / day X / day Y]
+CTA:         [primary CTA]
+Platform:    [API / Browser / Export only]
+
+Confirming angle before I start writing — does this match what you're after?
+[angle in plain language, 1–2 sentences]
+```
+
+---
+
+## RESPONSE FORMAT — after copy is generated
+
+```
+✅ Campaign ready: output/<client-slug>/<campaign-slug>/
+
+Campaign:    [type] — [pillar] pillar
+Emails:      [N] drafts
+Subjects:    [N × 5+] variants in subject line matrix
+CTA:         [primary CTA]
+Platform:    [handoff mode]
+Files:       [list of output files]
+
+Next steps:
+• Review subject line matrix and pick A/B test pairing for Email 01
+• Confirm platform template mapping before upload
+• Flag any guardrail notes in QA checklist before sending
+```
+
+---
+
+## COMMON MISTAKES TABLE
+
+| Mistake | Correct approach |
+|---|---|
+| Writing copy before asking 3 questions | Gate is mandatory — always AskUserQuestion first |
+| Using generic marketing voice | Pull exact tone adjectives and approved phrases from brand-kit.md |
+| Skipping content pillar mapping | Pillar must be confirmed before angle is set |
+| Writing email drafts before sequence plan | Sequence plan first — always |
+| One subject line per email | Minimum 5 variants with type tags |
+| Missing preview text | Subject line and preview text are always a pair |
+| Hardcoding platform credentials | Always env vars — never in files |
+| Missing plain-text fallback | Required in every email draft |
+| Using "guarantee" without qualifier | Check compliance_notes in brand kit first |
+| Fabricating proof points or stats | Only use numbers approved in brand kit |
+| Mixing campaign types in one sequence | One campaign type per sequence |
+| Overwriting existing output files | Always version up — `v2`, `v3`, never overwrite |
+| Forgetting the PS line | PS lines are high-read — always include one |
+| Not logging the deliverable | Append to brand kit deliverables log every session |
+| Pushing to platform without confirmation | Always confirm before any platform create/update |

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/.env.example

@@ -0,0 +1,9 @@
+# Growthub Open Higgsfield Studio — Environment Config
+# Copy this file to .env and fill in your values.
+# Never commit .env to version control.
+
+# Your Muapi API key — get one at https://muapi.ai/dashboard
+MUAPI_API_KEY=your_muapi_key_here
+
+# Muapi base URL — do not change unless self-hosting
+MUAPI_BASE_URL=https://api.muapi.io

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/QUICKSTART.md

@@ -0,0 +1,85 @@
+# Quick Start — Open Higgsfield Studio Worker Kit
+
+This folder is your self-contained agent working directory for Open Higgsfield AI visual production.
+
+---
+
+## Step 1 — Point your Working Directory at this folder
+
+**Growthub local (primary):** Open Growthub local and set the **Working Directory** to this folder in your project settings. Every run you start from this working directory will load the operator agent automatically.
+
+**Claude Code (alternative):** Open Claude Code settings and set the **Working Directory** to this folder. The operator agent loads from `workers/open-higgsfield-studio-operator/CLAUDE.md` on session start.
+
+---
+
+## Step 2 — Add your MUAPI key
+
+```bash
+cp .env.example .env
+```
+
+Open `.env` and replace `your_muapi_key_here` with your key from [muapi.ai/dashboard](https://muapi.ai/dashboard).
+
+The agent checks for this key at the start of every session (Step 0 of the workflow). It will not proceed without it.
+
+---
+
+## Step 3 — Verify your key works (optional but recommended)
+
+```bash
+node setup/verify-env.mjs
+```
+
+Runs a lightweight ping against the Muapi API with your key. Exits 0 on success. Prints a clear error if the key is invalid or unreachable.
+
+---
+
+## Step 4 — Check local dependencies (local-fork mode only)
+
+```bash
+bash setup/check-deps.sh
+```
+
+Checks for `node`, `npm`, `git`, and `ffmpeg`. All four are required for local-fork execution and frame-analysis workflows.
+
+---
+
+## Step 5 — Boot the local fork (local-fork mode only)
+
+```bash
+bash setup/clone-fork.sh
+```
+
+Clones the Open Higgsfield AI repo to `~/open-higgsfield-ai`, installs dependencies, and starts the dev server at `http://localhost:3001`. Skip this if you are using browser-hosted or desktop-app mode.
+
+---
+
+## Step 6 — Start a new session
+
+**Growthub local:** Start a new run from this working directory. The agent loads automatically.
+
+**Claude Code:** Open a new session with this folder as the Working Directory. The agent reads `skills.md` and the methodology automatically.
+
+In both cases the agent will ask you 3 clarifying questions before generating anything.
+
+---
+
+## Execution modes
+
+| Mode | When to use |
+|---|---|
+| `local-fork` | Local checkout running at localhost:3001 |
+| `browser-hosted` | Hosted app at muapi.ai/open-higgsfield-ai |
+| `desktop-app` | Electron app installed locally |
+
+---
+
+## First-run checklist
+
+See `validation-checklist.md` for the full pre-session checklist before your first generation run.
+
+---
+
+## Creating a brand kit for a new client
+
+See `brands/NEW-CLIENT.md`.

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/NEW-CLIENT.md

@@ -0,0 +1,46 @@
+# Creating a New Client Brand Kit
+
+Each client you run campaigns for should have their own brand kit. The agent uses this as its primary brand reference during Step 1 of every session.
+
+---
+
+## Setup
+
+```bash
+cp brands/_template/brand-kit.md brands/<client-slug>/brand-kit.md
+```
+
+Replace `<client-slug>` with a lowercase hyphenated identifier (e.g. `acme-corp`, `solo-founder`, `ecom-brand-x`).
+
+---
+
+## Required fields to fill in
+
+Open your new `brands/<client-slug>/brand-kit.md` and complete:
+
+| Field | What to write |
+|---|---|
+| Brand name | Full brand name as it appears in content |
+| Visual identity | Colors, typography, logo usage notes |
+| Tone and voice | Adjectives that describe how the brand communicates |
+| Target audience | Who the content is for |
+| Content restrictions | What to avoid in visuals or copy |
+| Reference assets | Paths to existing brand images, videos, or logo files |
+
+Fill in every section. Incomplete brand kits result in generic outputs.
+
+---
+
+## Telling the agent to use your brand kit
+
+At the start of your session, say:
+
+> "Use `brands/<client-slug>/brand-kit.md` as the active brand kit."
+
+The agent will load it in Step 1 instead of the Growthub default.
+
+---
+
+## Multiple clients
+
+Keep one subdirectory per client under `brands/`. Each session uses exactly one active brand kit.

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/_template/brand-kit.md

@@ -0,0 +1,89 @@
+# Brand Kit — [CLIENT NAME]
+
+Copy to `brands/<client-slug>/brand-kit.md` and fill before producing outputs.
+
+---
+
+## IDENTITY
+
+```yaml
+client_name: "[CLIENT NAME]"
+slug: "[client-slug]"
+industry: "[industry]"
+primary_offer: "[offer]"
+campaign_owner: "[owner]"
+date_onboarded: "YYYY-MM-DD"
+```
+
+## AUDIENCE
+
+```yaml
+primary_persona:
+  role: "[role]"
+  company_type: "[company type]"
+  pain_point: "[pain]"
+  desired_outcome: "[desired outcome]"
+  awareness_level: "[awareness]"
+```
+
+## POSITIONING
+
+```yaml
+core_positioning: "[one-sentence positioning]"
+what_they_buy: "[outcome they actually want]"
+unique_mechanism: "[why this works]"
+proof_points:
+  - "[approved proof only]"
+```
+
+## VISUAL SYSTEM
+
+```yaml
+visual_identity:
+  palette:
+    primary: "#000000"
+    secondary: "#FFFFFF"
+    accent: "#CCCCCC"
+  visual_adjectives:
+    - "[cinematic]"
+    - "[premium]"
+    - "[clean]"
+  prohibited_visuals:
+    - "[visual no-go]"
+    - "[visual no-go]"
+  reference_styles:
+    - "[director / campaign / style]"
+```
+
+## MESSAGING
+
+```yaml
+voice_and_tone:
+  - "[direct]"
+  - "[clear]"
+approved_phrases:
+  - "[approved phrase]"
+messaging_guardrails:
+  - "[no-go claim]"
+cta_language:
+  primary: "[primary CTA]"
+  secondary: "[secondary CTA]"
+```
+
+## ASSET LIBRARY
+
+```yaml
+available_assets:
+  product_stills: "[path or URL]"
+  brand_guidelines: "[path or URL]"
+  source_video: "[path or URL]"
+  portrait_assets: "[path or URL]"
+  audio_assets: "[path or URL]"
+  prior_generations: "[path or URL]"
+```
+
+## DELIVERABLES LOG
+
+```text
+- YYYY-MM-DD | Open Higgsfield Visual Package v<N> — <Project Name> | output/<client-slug>/<project-slug>/
+```

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/growthub/brand-kit.md

@@ -0,0 +1,96 @@
+# Brand Kit — Growthub
+
+Reference example brand kit for visual-generation work.
+
+---
+
+## IDENTITY
+
+```yaml
+client_name: "Growthub"
+slug: "growthub"
+industry: "AI-enabled growth infrastructure and creative operations"
+primary_offer: "Creative velocity systems, visual strategy, and execution support for paid-media operators"
+campaign_owner: "Growthub"
+date_onboarded: "2026-04-10"
+```
+
+## AUDIENCE
+
+```yaml
+primary_persona:
+  role: "performance lead, agency owner, or growth operator"
+  company_type: "DTC brand, agency, or startup running paid acquisition"
+  pain_point: "creative throughput is too slow to sustain testing velocity"
+  desired_outcome: "more winning concepts without slower turnaround or more headcount"
+  awareness_level: "problem-aware"
+```
+
+## POSITIONING
+
+```yaml
+core_positioning: "Growthub is the operating layer that removes the bottleneck between creative ideas and campaign execution."
+what_they_buy: "speed to winning creative with more control and less chaos"
+unique_mechanism: "operator-grade planning plus AI-assisted visual production workflows"
+proof_points:
+  - "Use only approved client-result examples already cleared by Growthub"
+```
+
+## VISUAL SYSTEM
+
+```yaml
+visual_identity:
+  palette:
+    primary: "#0E1726"
+    secondary: "#F4F1E8"
+    accent: "#D8613C"
+  visual_adjectives:
+    - "decisive"
+    - "cinematic"
+    - "premium"
+    - "high-signal"
+  prohibited_visuals:
+    - "generic SaaS gradient slop"
+    - "empty dashboard glamour shots with no human tension"
+  reference_styles:
+    - "high-contrast product-led motion"
+    - "operator POV"
+    - "documentary-meets-performance-marketing"
+```
+
+## MESSAGING
+
+```yaml
+voice_and_tone:
+  - "direct"
+  - "operator-level"
+  - "confident"
+approved_phrases:
+  - "creative velocity"
+  - "remove the bottleneck between ideas and execution"
+  - "speed to winning ads"
+messaging_guardrails:
+  - "Do not promise guaranteed revenue outcomes"
+  - "Do not reduce Growthub to just an AI tool"
+cta_language:
+  primary: "Book your growth call"
+  secondary: "Review the plan and approve the batch"
+```
+
+## ASSET LIBRARY
+
+```yaml
+available_assets:
+  product_stills: "[fill per engagement]"
+  brand_guidelines: "[fill per engagement]"
+  source_video: "[fill per engagement]"
+  portrait_assets: "[fill per engagement]"
+  audio_assets: "[fill per engagement]"
+  prior_generations: "[fill per engagement]"
+```
+
+## DELIVERABLES LOG
+
+```text
+- 2026-04-10 | Open Higgsfield Visual Package v1 — Studio Launch Reference | output/growthub/studio-launch-reference/
+```

package/assets/worker-kits/growthub-open-higgsfield-studio-v1/bundles/growthub-open-higgsfield-studio-v1.json

@@ -0,0 +1,57 @@
+{
+  "schemaVersion": 2,
+  "bundle": {
+    "id": "growthub-open-higgsfield-studio-v1",
+    "version": "1.0.0",
+    "kitId": "growthub-open-higgsfield-studio-v1",
+    "workerId": "open-higgsfield-studio-operator"
+  },
+  "briefType": "open-higgsfield-visual-production",
+  "publicExampleBrandPaths": [
+    "brands/growthub/brand-kit.md"
+  ],
+  "requiredFrozenAssets": [
+    "QUICKSTART.md",
+    ".env.example",
+    "skills.md",
+    "output-standards.md",
+    "runtime-assumptions.md",
+    "validation-checklist.md",
+    "workers/open-higgsfield-studio-operator/CLAUDE.md",
+    "brands/_template/brand-kit.md",
+    "brands/growthub/brand-kit.md",
+    "brands/NEW-CLIENT.md",
+    "setup/clone-fork.sh",
+    "setup/verify-env.mjs",
+    "setup/check-deps.sh",
+    "output/README.md",
+    "templates/visual-campaign-brief.md",
+    "templates/studio-selection-brief.md",
+    "templates/model-selection-recommendation.md",
+    "templates/shot-plan.md",
+    "templates/prompt-matrix.md",
+    "templates/generation-batch-plan.md",
+    "templates/asset-tracking.md",
+    "templates/review-qa-checklist.md",
+    "templates/platform-ready-execution-handoff.md",
+    "templates/frame-analysis.md",
+    "templates/prompt-templates/image-generation.md",
+    "templates/prompt-templates/video-generation.md",
+    "templates/prompt-templates/lip-sync-generation.md",
+    "templates/prompt-templates/cinema-generation.md",
+    "examples/visual-campaign-brief-sample.md",
+    "examples/shot-plan-sample.md",
+    "examples/prompt-matrix-sample.md",
+    "examples/platform-ready-handoff-sample.md",
+    "docs/open-higgsfield-fork-integration.md",
+    "docs/provider-adapter-layer.md",
+    "growthub-meta/README.md",
+    "growthub-meta/kit-standard.md"
+  ],
+  "optionalPresets": [],
+  "export": {
+    "folderName": "growthub-agent-worker-kit-open-higgsfield-studio-v1",
+    "zipFileName": "growthub-agent-worker-kit-open-higgsfield-studio-v1.zip"
+  },
+  "activationModes": ["export"]
+}