@growthub/cli 0.7.0 → 0.7.2

package/assets/shared-templates/marketing-frameworks/competitor-positioning.md

@@ -0,0 +1,46 @@
+# Competitor Analysis — Positioning Gap Framework
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (competitor-alternatives skill) — MIT license
+
+## When to Use
+
+Apply when analyzing competitors, building positioning strategy, or creating comparison content. Also use before pricing decisions, launch strategy, or content strategy to understand the competitive landscape.
+
+## Analysis Components
+
+### 1. Competitor Classification
+- **Direct**: Same category, same audience, head-to-head competition
+- **Secondary**: Adjacent category, partial audience overlap
+- **Indirect**: Different approach to the same underlying problem
+
+### 2. Feature Matrix
+Compare capabilities across your product and 2-4 key competitors. Focus on features that matter to your target audience, not exhaustive lists.
+
+### 3. Messaging Teardown
+For each competitor, analyze:
+- **Headline**: What promise do they lead with?
+- **Value proposition**: How do they describe their differentiation?
+- **Primary CTA**: What action do they push visitors toward?
+- **Trust signals**: What proof do they show?
+- **Objection handling**: What concerns do they preemptively address?
+
+### 4. Positioning Gaps
+Where competitors are weak or silent = your opportunity. Look for:
+- Features they lack that your audience needs
+- Messaging angles they don't own
+- Audience segments they ignore
+- Pricing tiers they don't serve
+
+### 5. Pricing Comparison
+Map pricing across tiers (free, entry, mid, enterprise) to identify:
+- Price anchoring opportunities
+- Tier structuring gaps
+- Feature-to-price value positioning
+
+## Output Structure
+
+1. Competitor overview table
+2. Feature matrix
+3. Messaging teardown per competitor
+4. Positioning gaps and opportunities
+5. Recommended positioning adjustments

package/assets/shared-templates/marketing-frameworks/cro-7-dimensions.md

@@ -0,0 +1,48 @@
+# CRO Analysis — 7-Dimension Framework
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (page-cro skill) — MIT license
+
+## When to Use
+
+Apply when auditing any marketing page for conversion optimization: homepage, landing page, pricing page, feature page, or blog post.
+
+## The 7 Dimensions
+
+### 1. Value Proposition Clarity
+Can the visitor understand what the product does and who it's for within 5 seconds of landing? The value proposition should be specific, benefit-driven, and immediately visible above the fold.
+
+### 2. Headline Effectiveness
+Does the headline match the messaging from the traffic source (ad, email, social post)? Message match between traffic source and landing page is one of the highest-impact conversion factors.
+
+### 3. CTA Placement & Copy
+Is there a single, clear primary action? Is the CTA benefit-driven (not "Submit" or "Get Started" but what the user gets)? Is it visible without scrolling?
+
+### 4. Visual Hierarchy
+Is the page scannable? Does whitespace guide the eye from headline → benefit → proof → CTA? Can a visitor understand the page structure in a 3-second scan?
+
+### 5. Trust Signals
+Are logos, testimonials, case studies, reviews, and security badges positioned near decision points (especially near CTAs and pricing)? Trust signals reduce anxiety at the moment of conversion.
+
+### 6. Objection Handling
+Are the top 3-5 objections (price, fit, difficulty, risk, timing) addressed before the visitor reaches the CTA? Unaddressed objections cause abandonment.
+
+### 7. Friction Points
+Are there unnecessary form fields, confusing navigation paths, broken mobile layouts, slow load times, or unclear next steps that create friction in the conversion path?
+
+## Scoring
+
+| Score | Meaning |
+|---|---|
+| Strong (3) | Optimized, no issues found |
+| Adequate (2) | Functional but improvement opportunities exist |
+| Weak (1) | Significant issues impacting conversions |
+| Missing (0) | Not present or fundamentally broken |
+
+Composite: sum of 7 dimensions (0-21 scale).
+
+## Output Structure
+
+1. Quick Wins (implement immediately, low effort)
+2. High-Impact Changes (prioritized by effort vs. impact)
+3. A/B Test Hypotheses (grounded in findings)
+4. Copy Alternatives (2-3 headline and CTA options)

package/assets/shared-templates/marketing-frameworks/email-sequence-architecture.md

@@ -0,0 +1,50 @@
+# Email Sequence — 5-Type Architecture
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (email-sequence skill) — MIT license
+
+## When to Use
+
+Apply when designing any email sequence. Start by identifying which of the 5 types matches the use case, then follow the architecture for that type.
+
+## The 5 Standard Types
+
+| Type | Emails | Duration | Key Focus |
+|---|---|---|---|
+| Welcome | 5-7 | 12-14 days | Activation and initial conversion |
+| Lead Nurture | 6-8 | 2-3 weeks | Trust-building via expertise demonstration |
+| Re-engagement | 3-4 | 2 weeks | Win-back or list cleaning |
+| Onboarding | 5-7 | 14 days | Feature adoption and aha moments |
+| Event-based | Variable | Trigger-dependent | Behavioral automation |
+
+## Core Principles
+
+1. **One email, one job** — Each message has a single primary purpose with one main CTA
+2. **Value before ask** — Build trust through content before requesting conversion
+3. **Relevance over volume** — Quality messaging outperforms send frequency
+
+## Sequence Design Process
+
+1. **Identify type** — Which of the 5 types matches the use case?
+2. **Define emotional arc** — What emotional journey from Email 1 to Email N?
+3. **Map individual purposes** — Each email gets a theme, body arc, and CTA
+4. **Set timing** — Send delays based on type (see table above)
+5. **Write subject line matrix** — 5+ variants per email with type tags
+6. **Define segments and triggers** — Entry conditions and platform configuration
+
+## Subject Line Types
+
+| Type | When to Use |
+|---|---|
+| Curiosity | Opening unknown, creating information gap |
+| Social proof | Leveraging others' behavior or results |
+| Direct | Clear benefit statement, no mystery |
+| Personal | Conversational, feels one-to-one |
+| Urgency | Time or availability constraint (use sparingly) |
+
+## Quality Bar
+
+- Every email gets 5+ subject line variants with type tags
+- Every email gets preview text (subject line and preview are always a pair)
+- Every email gets a plain-text fallback
+- PS lines recommended (high-read position)
+- CAN-SPAM compliance line in every broadcast

package/assets/shared-templates/marketing-frameworks/launch-playbook.md

@@ -0,0 +1,62 @@
+# Launch Strategy — Phased Playbook Framework
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (launch-strategy skill) — MIT license
+
+## When to Use
+
+Apply when planning any product launch, feature release, rebrand, or campaign with a specific go-live date.
+
+## The 3 Phases
+
+### Pre-Launch (T-minus 2-4 weeks)
+**Goal:** Build audience, prepare assets, validate messaging.
+
+Key activities:
+- Finalize product-marketing context
+- Build landing page / announcement page
+- Prepare email sequences (announcement + follow-up)
+- Draft social content calendar
+- Build press / community outreach list
+- Set up analytics tracking (events, goals, UTMs)
+- Brief internal team on messaging and positioning
+- Prepare FAQ and objection handling
+- Create paid ad creative and targeting (if applicable)
+- Collect and incorporate beta feedback
+
+### Launch Day
+**Goal:** Coordinated execution across all channels.
+
+Key activities:
+- Send announcement email
+- Publish social posts (all channels, staggered timing)
+- Post community announcements
+- Send press / outreach emails
+- Activate paid ads (if applicable)
+- Monitor real-time (analytics, social, support)
+- Keep team available for rapid response
+
+### Post-Launch (T-plus 1-4 weeks)
+**Goal:** Iterate based on data, activate retention.
+
+Key activities:
+- Day 1 metrics review (traffic, signups, conversion rate)
+- Week 1 performance report
+- User feedback collection and categorization
+- Quick win implementation from feedback
+- Follow-up email sequence activation
+- Retargeting campaigns (if applicable)
+- Content iteration based on top-performing angles
+- Week 4 full retrospective
+
+## Channel Plan Matrix
+
+Map each channel across all 3 phases to ensure nothing is missed:
+
+| Channel | Pre-Launch | Launch Day | Post-Launch |
+|---|---|---|---|
+| Email | Build sequences | Send announcement | Nurture + follow-up |
+| Social | Tease + build anticipation | Coordinated launch posts | Ongoing content |
+| Blog/SEO | Publish supporting content | Launch post | Update based on feedback |
+| Community | Seed conversations | Announcement thread | Engage and iterate |
+| Paid | Prepare creative | Activate campaigns | Optimize based on data |
+| Press | Pitch and outreach | Publish coverage | Follow-up relationships |

package/assets/shared-templates/marketing-frameworks/product-marketing-context.md

@@ -0,0 +1,62 @@
+# Product Marketing Context — Foundation Framework
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (product-marketing-context skill) — MIT license
+
+## When to Use
+
+This is the foundational framework. Use it before any other marketing skill. Every marketing deliverable should be grounded in a completed product-marketing context.
+
+## The 12 Sections
+
+### 1. Product Overview
+One-liner, category, product type, pricing model, starting price.
+
+### 2. Target Audience
+Company type (B2B/B2C), company size, industry verticals, decision-maker titles, primary and secondary use cases.
+
+### 3. Personas
+Stakeholder roles with key motivations and primary objections per persona.
+
+### 4. Problems & Pain Points
+Core problem, cost of inaction, emotional tension, and failed alternatives.
+
+### 5. Competitive Landscape
+Direct, secondary, and indirect competitors with key differentiators.
+
+### 6. Differentiation
+Top 3 differentiators and the core "why customers choose you" statement.
+
+### 7. Objections & Anti-Personas
+Common objections with handling strategies, plus who is NOT the right customer.
+
+### 8. Switching Dynamics (Push/Pull/Habit/Anxiety)
+- **Push**: What pushes users away from the status quo
+- **Pull**: What pulls them toward your product
+- **Habit**: What keeps them where they are
+- **Anxiety**: What they fear about switching
+
+### 9. Customer Language
+Verbatim phrases from customer interviews, reviews, support tickets, or sales calls. These are more valuable than any polished positioning statement.
+
+### 10. Brand Voice
+Tone, style, personality, words to use, words to avoid.
+
+### 11. Proof Points
+Key metrics, testimonials, case studies, awards — only verifiable data.
+
+### 12. Goals
+Primary conversion action, secondary goals, revenue targets with specific metrics.
+
+## Key Principle
+
+**Customer language over marketing jargon.** The product-marketing context captures exact customer phrases because verbatim language makes marketing copy resonate with actual customer thinking. Every downstream skill should prefer customer language over polished positioning statements.
+
+## Auto-Draft Capability
+
+If the product context doesn't exist yet, it can be auto-drafted by scanning:
+- README.md
+- package.json
+- Landing page content
+- Existing marketing materials
+
+The auto-draft provides a starting point that the user then validates and refines.

package/assets/shared-templates/marketing-frameworks/seo-audit-eeat.md

@@ -0,0 +1,44 @@
+# SEO Audit — E-E-A-T Framework
+
+> Source: [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills) (seo-audit skill) — MIT license
+
+## When to Use
+
+Apply when auditing content quality for search performance. E-E-A-T is Google's quality assessment framework used by Search Quality Raters. It applies to all content but is critical for YMYL (Your Money or Your Life) topics.
+
+## The 4 Signals
+
+### Experience
+Does the content demonstrate first-hand experience with the topic? This includes personal use of products, direct involvement in processes, or real-world application of the advice given.
+
+### Expertise
+Does the content demonstrate depth and accuracy? Is the author qualified to write about this topic? Expertise signals include detailed analysis, correct terminology, and nuanced understanding.
+
+### Authoritativeness
+Is the source recognized as a credible authority? Authority signals include external citations, industry recognition, author credentials, and domain reputation.
+
+### Trustworthiness
+Is the content accurate, transparent, and safe? Trust signals include proper attribution, clear disclosure, accurate claims, contact information, and secure browsing experience.
+
+## Audit Priority Order
+
+1. **Crawlability & Indexation** — Can search engines find and index the content?
+2. **Technical Foundations** — Core Web Vitals, mobile, HTTPS, site speed
+3. **On-Page Optimization** — Titles, metas, headings, keyword targeting
+4. **Content Quality** — Depth, E-E-A-T signals, search intent alignment
+5. **Authority & Links** — Internal linking, external citations, backlink profile
+
+## Priority Matrix
+
+| Level | Criteria |
+|---|---|
+| Critical | Blocking indexation or causing ranking penalties |
+| High | Significant ranking impact, moderate effort to fix |
+| Medium | Incremental improvement, low-moderate effort |
+| Low | Nice-to-have, minimal ranking impact |
+
+## Output Structure
+
+1. Executive Summary (top 3-5 priorities)
+2. Findings by section (Issue / Impact / Evidence / Fix / Priority)
+3. Prioritized Action Plan (critical → quick wins → long-term)

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

@@ -0,0 +1,7 @@
+# Growthub Hyperframes Studio — Environment Config
+# Copy this file to .env and fill in your local values.
+# Never commit .env to version control.
+
+# Absolute path to your local Hyperframes clone.
+# Example: /Users/<you>/dev/hyperframes
+HYPERFRAMES_LOCAL_PATH=

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

@@ -0,0 +1,21 @@
+# Hyperframes Studio Quickstart
+
+## 1) Prepare environment
+
+```bash
+cp .env.example .env
+bash setup/check-deps.sh
+node setup/verify-env.mjs
+```
+
+## 2) Clone Hyperframes locally
+
+```bash
+bash setup/clone-fork.sh
+```
+
+## 3) Start work
+
+- Point your agent Working Directory to this exported folder.
+- Follow `workers/hyperframes-studio-operator/CLAUDE.md`.
+- Write outputs to `output/<client-slug>/<project-slug>/`.

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

@@ -0,0 +1,3 @@
+# NEW CLIENT
+
+Copy `brands/_template/brand-kit.md` into a new client folder before planning.

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

@@ -0,0 +1,7 @@
+# Brand Kit Template
+
+- Brand:
+- Audience:
+- Voice:
+- Visual style:
+- Must avoid:

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

@@ -0,0 +1,6 @@
+# Growthub Brand Kit
+
+- Brand: Growthub
+- Audience: operators and builders
+- Voice: direct, practical
+- Visual style: clear typography and high contrast

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

@@ -0,0 +1,47 @@
+{
+  "schemaVersion": 2,
+  "bundle": {
+    "id": "growthub-hyperframes-studio-v1",
+    "version": "1.0.0",
+    "kitId": "growthub-hyperframes-studio-v1",
+    "workerId": "hyperframes-studio-operator"
+  },
+  "briefType": "hyperframes-video-production",
+  "publicExampleBrandPaths": [
+    "brands/growthub/brand-kit.md"
+  ],
+  "requiredFrozenAssets": [
+    "QUICKSTART.md",
+    ".env.example",
+    "skills.md",
+    "output-standards.md",
+    "runtime-assumptions.md",
+    "validation-checklist.md",
+    "workers/hyperframes-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/video-brief.md",
+    "templates/composition-spec.md",
+    "templates/render-plan.md",
+    "templates/qa-checklist.md",
+    "examples/video-brief-sample.md",
+    "docs/hyperframes-fork-integration.md",
+    "docs/provider-adapter-layer.md",
+    "docs/hyperframes-discovery-path.md",
+    "growthub-meta/README.md",
+    "growthub-meta/kit-standard.md"
+  ],
+  "optionalPresets": [],
+  "export": {
+    "folderName": "growthub-agent-worker-kit-hyperframes-studio-v1",
+    "zipFileName": "growthub-agent-worker-kit-hyperframes-studio-v1.zip"
+  },
+  "activationModes": [
+    "export"
+  ]
+}

package/assets/worker-kits/growthub-hyperframes-studio-v1/docs/hyperframes-discovery-path.md

@@ -0,0 +1,12 @@
+# Hyperframes Discovery Path
+
+Discovery path:
+
+- `growthub discover` → `Worker Kits` → `Custom Workspaces`
+- `growthub kit list --family studio`
+- `growthub kit download hyperframes`
+
+Feature branch demo checks:
+
+- `zsh /Users/antonio/growthub-local/scripts/demo-cli.sh cli kit list --family studio`
+- `zsh /Users/antonio/growthub-local/scripts/demo-cli.sh cli kit inspect hyperframes`

package/assets/worker-kits/growthub-hyperframes-studio-v1/docs/hyperframes-fork-integration.md

@@ -0,0 +1,11 @@
+# Hyperframes Fork Integration
+
+Upstream repository:
+
+- `https://github.com/heygen-com/hyperframes`
+
+Primary execution flow:
+
+1. Clone with `setup/clone-fork.sh`
+2. Install and preview with Hyperframes CLI
+3. Render deterministic outputs

package/assets/worker-kits/growthub-hyperframes-studio-v1/docs/provider-adapter-layer.md

@@ -0,0 +1,9 @@
+# Provider Adapter Layer
+
+This kit is a custom workspace package and does not add a new server adapter or agent harness.
+
+It relies on:
+
+- Worker kit export contract
+- Working Directory execution
+- Upstream Hyperframes repository

package/assets/worker-kits/growthub-hyperframes-studio-v1/examples/video-brief-sample.md

@@ -0,0 +1,15 @@
+# Sample Video Brief
+
+- Goal: Explain Hyperframes architecture in 30 seconds
+- Audience: product and engineering teams
+- Duration: 00:30
+- Aspect ratio: 16:9
+- Delivery format: MP4
+# Sample Video Brief
+
+- Objective: Explain Hyperframes architecture in 45 seconds.
+- Audience: Technical PMs and agent operators.
+- Duration: 45s
+- Aspect ratio: 16:9
+- Core message: HTML-native video compositions with deterministic rendering.
+- CTA: Clone the repo and render your first composition.

package/assets/worker-kits/growthub-hyperframes-studio-v1/growthub-meta/README.md

@@ -0,0 +1,3 @@
+# Hyperframes Workspace Meta
+
+This directory stores metadata and standards for `growthub-hyperframes-studio-v1`.

package/assets/worker-kits/growthub-hyperframes-studio-v1/growthub-meta/kit-standard.md

@@ -0,0 +1,6 @@
+# Kit Standard
+
+- schemaVersion: 2
+- family: studio
+- executionMode: export
+- activationModes: export

package/assets/worker-kits/growthub-hyperframes-studio-v1/kit.json

@@ -0,0 +1,97 @@
+{
+  "schemaVersion": 2,
+  "kit": {
+    "id": "growthub-hyperframes-studio-v1",
+    "version": "1.0.0",
+    "name": "Growthub Agent Worker Kit — Hyperframes Studio",
+    "description": "Self-contained local execution environment for Hyperframes video production. Produces implementation-ready video briefs, composition specs, render plans, and QA handoff artifacts for HTML-native rendering workflows.",
+    "type": "worker",
+    "visibility": "public-open-source",
+    "sourceRepo": "growthub-local",
+    "family": "studio"
+  },
+  "entrypoint": {
+    "workerId": "hyperframes-studio-operator",
+    "path": "workers/hyperframes-studio-operator/CLAUDE.md"
+  },
+  "workerIds": [
+    "hyperframes-studio-operator"
+  ],
+  "agentContractPath": "workers/hyperframes-studio-operator/CLAUDE.md",
+  "brandTemplatePath": "brands/_template/brand-kit.md",
+  "publicExampleBrandPaths": [
+    "brands/growthub/brand-kit.md"
+  ],
+  "frozenAssetPaths": [
+    "QUICKSTART.md",
+    ".env.example",
+    "skills.md",
+    "output-standards.md",
+    "runtime-assumptions.md",
+    "validation-checklist.md",
+    "workers/hyperframes-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/video-brief.md",
+    "templates/composition-spec.md",
+    "templates/render-plan.md",
+    "templates/qa-checklist.md",
+    "examples/video-brief-sample.md",
+    "docs/hyperframes-fork-integration.md",
+    "docs/provider-adapter-layer.md",
+    "docs/hyperframes-discovery-path.md",
+    "growthub-meta/README.md",
+    "growthub-meta/kit-standard.md"
+  ],
+  "setupPaths": {
+    "quickstart": "QUICKSTART.md",
+    "envExample": ".env.example",
+    "setupDir": "setup/",
+    "outputDir": "output/"
+  },
+  "outputStandard": {
+    "type": "working-directory",
+    "description": "Exported folder is intended to be pointed at directly by the agent Working Directory. All outputs are markdown files written to output/<client-slug>/<project-slug>/.",
+    "requiredPaths": [
+      "QUICKSTART.md",
+      ".env.example",
+      "kit.json",
+      "bundles/growthub-hyperframes-studio-v1.json",
+      "skills.md",
+      "workers/hyperframes-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",
+      "docs",
+      "growthub-meta"
+    ]
+  },
+  "bundles": [
+    {
+      "id": "growthub-hyperframes-studio-v1",
+      "version": "1.0.0",
+      "path": "bundles/growthub-hyperframes-studio-v1.json"
+    }
+  ],
+  "executionMode": "export",
+  "activationModes": [
+    "export"
+  ],
+  "compatibility": {
+    "cliMinVersion": "0.4.3"
+  },
+  "provenance": {
+    "sourceRepo": "growthub-local",
+    "frozenAt": "2026-04-17T00:00:00.000Z"
+  }
+}

package/assets/worker-kits/growthub-hyperframes-studio-v1/output/README.md

@@ -0,0 +1,5 @@
+# Output Directory
+
+Save outputs under:
+
+- `output/<client-slug>/<project-slug>/`

package/assets/worker-kits/growthub-hyperframes-studio-v1/output-standards.md

@@ -0,0 +1,12 @@
+# Output Standards
+
+Write all deliverables to:
+
+- `output/<client-slug>/<project-slug>/`
+
+Minimum required artifacts:
+
+- `video-brief.md`
+- `composition-spec.md`
+- `render-plan.md`
+- `qa-checklist.md`

package/assets/worker-kits/growthub-hyperframes-studio-v1/runtime-assumptions.md

@@ -0,0 +1,6 @@
+# Runtime Assumptions
+
+- Upstream project: `https://github.com/heygen-com/hyperframes`
+- Node.js `>=22`
+- `ffmpeg` available in PATH
+- Commands run from an exported working directory

package/assets/worker-kits/growthub-hyperframes-studio-v1/setup/check-deps.sh

@@ -0,0 +1,14 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+need_cmd() {
+  command -v "$1" >/dev/null 2>&1 || {
+    echo "Missing dependency: $1" >&2
+    exit 1
+  }
+}
+
+need_cmd node
+need_cmd npm
+need_cmd git
+need_cmd ffmpeg

package/assets/worker-kits/growthub-hyperframes-studio-v1/setup/clone-fork.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+REPO_URL="${HYPERFRAMES_REPO_URL:-https://github.com/heygen-com/hyperframes}"
+LOCAL_PATH="${HYPERFRAMES_LOCAL_PATH:-./.hyperframes}"
+
+if [ -d "${LOCAL_PATH}/.git" ]; then
+  git -C "${LOCAL_PATH}" fetch origin
+  git -C "${LOCAL_PATH}" pull --ff-only
+else
+  git clone "${REPO_URL}" "${LOCAL_PATH}"
+fi

package/assets/worker-kits/growthub-hyperframes-studio-v1/setup/verify-env.mjs

@@ -0,0 +1,16 @@
+import fs from "node:fs";
+import path from "node:path";
+
+const envPath = path.resolve(process.cwd(), ".env");
+if (!fs.existsSync(envPath)) {
+  console.error(".env not found. Run: cp .env.example .env");
+  process.exit(1);
+}
+
+const raw = fs.readFileSync(envPath, "utf8");
+if (!raw.includes("HYPERFRAMES_LOCAL_PATH=")) {
+  console.error("HYPERFRAMES_LOCAL_PATH is required in .env");
+  process.exit(1);
+}
+
+console.log("Environment check passed.");