@growthub/cli 0.3.55 → 0.3.57

package/README.md

@@ -1,12 +1,6 @@
 # @growthub/cli
 
-`@growthub/cli` is the published CLI for Growthub Local. It covers five shipped user flows:
-
-- full local app discovery and onboarding
-- worker kit discovery, export, inspection, and validation
-- shared template discovery and extraction
-- hosted workflows, capabilities, dynamic pipelines, and artifacts
-- hosted Growthub auth + machine profile bridge
+`@growthub/cli` is the public CLI for Growthub Local.
 
 ## Install
 
@@ -14,201 +8,107 @@
 npm install -g @growthub/cli
 ```
 
-You can also install through the guided installer:
+Or use the guided installer:
 
 ```bash
 npm create growthub-local@latest
 ```
 
-Or jump directly to a profile:
-
-```bash
-npm create growthub-local@latest -- --profile gtm
-npm create growthub-local@latest -- --profile dx
-```
-
-## CLI Editions
+## At a Glance
 
-The current CLI exposes five user-facing flows through `growthub discover` and direct subcommands.
+The CLI ships these user flows:
 
-### 1. Full Local App
+- `Agent Harness` (Paperclip Local App, Open Agents, Qwen Code CLI)
+- `Worker Kits`
+- `Templates`
+- `Workflows`
+- `Local Intelligence`
+- `Hosted Auth Bridge`
 
-Use this when you want to create or reopen a full Growthub local surface.
+## Quick Commands
 
 ```bash
+# Discovery
 growthub
-growthub list
 growthub discover
+
+# Agent Harness
 growthub onboard
 growthub run
-```
-
-User flow:
-
-1. Open the discovery hub.
-2. Choose `Full Local App`.
-3. Create a new `gtm` or `dx` profile, or load an existing local profile.
-4. Complete onboarding.
-5. Start the local server and finish the hosted authentication bridge.
+growthub open-agents
+growthub qwen-code
 
-### 2. Worker Kits
-
-Use this when you want a working-directory-ready environment for an agent.
-
-### Discovery
-
-```bash
-# Interactive discovery hub
-growthub list
-
-# Interactive browser — type filter → kit selector → actions
+# Worker Kits
 growthub kit
-
-# All kits grouped by family with descriptions and inline commands
 growthub kit list
+growthub kit inspect <kit-id>
+growthub kit download <kit-id>
+growthub kit validate <path>
 
-# Filter by family
-growthub kit list --family studio
-growthub kit list --family studio,operator
+# Templates
+growthub template
+growthub template list
+growthub template get <slug>
 
-# Machine-readable output
-growthub kit list --json
+# Workflows
+growthub workflow
+growthub workflow saved
+growthub pipeline assemble
 
-# Family taxonomy
-growthub kit families
+# Hosted Auth Bridge
+growthub auth login
+growthub auth whoami
+growthub auth logout
 ```
 
-### Inspect, download, and validate
+## Worker Kit Command Surface
 
 ```bash
+growthub kit list
 growthub kit inspect creative-strategist-v1
 growthub kit inspect growthub-open-higgsfield-studio-v1
-growthub kit inspect growthub-email-marketing-v1 --json
-
 growthub kit download creative-strategist-v1
 growthub kit download growthub-open-higgsfield-studio-v1
-growthub kit download higgsfield --yes
-
 growthub kit path creative-strategist-v1
 growthub kit validate /absolute/path/to/kit
 ```
 
-### After download
-
-1. Point Growthub local or your local adapter `Working directory` at the exported folder.
-2. Add runtime-only environment variables required by the kit.
-3. Start a new session so the operator contract loads from `CLAUDE.md`.
-
-### Available bundled kits
-
-| Kit | Family | Description |
-|---|---|---|
-| `creative-strategist-v1` | workflow | Video creative briefs and campaign strategy |
-| `growthub-email-marketing-v1` | operator | Brand-aware email campaigns, sequences, and campaign planning |
-| `growthub-open-higgsfield-studio-v1` | studio | Open Higgsfield visual production workflows |
-
 ### How local adapters use worker kits
 
-Local adapters execute inside the agent `Working directory` path. Worker kits are designed to plug into that path directly:
+1. Download or resolve a kit path from the CLI.
+2. Point the agent working directory at the exported folder.
+3. Start a new session so the kit contract loads from `CLAUDE.md`.
 
-1. `growthub kit download <id>` exports the kit as a folder plus zip.
-2. Point the agent `Working directory` at the exported folder.
-3. Start a new session so the agent reads the kit contract from `CLAUDE.md`.
+## Harness Notes
 
-### 3. Shared Templates
+### Open Agents
 
-Use this when you need a reusable artifact primitive without exporting a full kit.
+- upstream: [vercel-labs/open-agents](https://github.com/vercel-labs/open-agents)
+- secure auth mode support: `none`, `api-key`, `vercel-managed`
+- prompt/chat commands: `growthub open-agents prompt`, `growthub open-agents chat`
 
-```bash
-growthub template
-growthub template list
-growthub template list --type ad-formats
-growthub template list --type scene-modules --subtype hooks
-growthub template get villain-animation
-growthub template get meme-overlay --out ~/kit/hooks/
-growthub template get villain-animation --json
-```
+### Qwen Code CLI
 
-User flow:
+- upstream: [QwenLM/qwen-code](https://github.com/QwenLM/qwen-code)
+- secure local key setup from `growthub qwen-code` configure flow
+- prompt/chat session commands: `growthub qwen-code prompt`, `growthub qwen-code session`
 
-1. Browse by family and artifact group.
-2. Preview the selected artifact.
-3. Print it, copy it to a local workspace, or use the slug in another workflow.
+## Extension Model
 
-### 4. Hosted Workflows
+Content extensions:
 
-Use this when you want CMS node contract discovery, dynamic hosted pipeline creation, and saved workflow lifecycle management.
+- worker kits: `cli/assets/worker-kits/`
+- shared templates: `cli/assets/shared-templates/`
 
-```bash
-growthub workflow
-growthub workflow saved
-growthub pipeline assemble
-```
-
-### 5. Hosted Auth Bridge
-
-Use this when you want the hosted Growthub account to remain the top-level identity while syncing safe local-machine metadata into the CLI runtime.
-
-```bash
-growthub auth login
-growthub auth whoami
-growthub auth logout
-growthub profile status
-growthub profile pull
-growthub profile push
-```
-
-Contract:
-
-1. Hosted Growthub auth remains the source of truth for the user identity.
-2. Local workspace config stays local-first and is not overwritten by hosted state.
-3. Hosted machine linkage is stored separately from `instances/<id>/config.json`.
-4. `growthub` and `paperclipai` remain intentional side-by-side surfaces rather than auto-loading one another.
-
-## Workflows Discovery V1
-
-The public CLI now supports a hosted workflow discovery flow inside the interactive hub for all Growthub Auth Users:
-
-```bash
-growthub discover
-growthub workflow
-growthub workflow saved
-```
-
-Use this when you want to:
-
-- inspect CMS node contracts from the interactive contracts browser
-- list hosted saved workflows and inspect detail
-- create/save hosted workflows through Dynamic Pipelines
-- execute a hosted saved workflow from the CLI
-- manage workflow lifecycle actions (archive/delete) from CLI
-
-The full public usage and architecture notes live here:
+Governance/reference docs:
 
+- [Worker Kits](../docs/WORKER_KITS.md)
 - [CLI Workflows Discovery V1](../docs/CLI_WORKFLOWS_DISCOVERY_V1.md)
-
-## Contribution Model
-
-The CLI has two extension surfaces for content:
-
-- worker kits in `cli/assets/worker-kits/`
-- shared templates in `cli/assets/shared-templates/`
-
-Use shared templates for reusable cross-kit primitives. Use worker kits for full opinionated environments with prompts, standards, examples, and runtime assumptions.
-
-For the agent-facing extension workflow, see [docs/CLI_TEMPLATE_CONTRIBUTION_EXTENSION_WORKFLOWS.md](../docs/CLI_TEMPLATE_CONTRIBUTION_EXTENSION_WORKFLOWS.md).
-
-## Development Notes
-
-- `@growthub/cli` version: `0.3.49`
-- Node.js: `>=20`
-- Source of truth repo: [Growthub Local](https://github.com/Growthub-ai/growthub-local)
+- [Agent Harness Auth Primitive](../docs/AGENT_HARNESS_AUTH_PRIMITIVE.md)
+- [Kernel Packet Registry](../docs/kernel-packets/README.md)
 
 ## Links
 
-- [GitHub README](https://github.com/Growthub-ai/growthub-local#readme)
+- [Growthub Local Repository](https://github.com/Growthub-ai/growthub-local)
+- [Root README](https://github.com/Growthub-ai/growthub-local#readme)
 - [Contributing](https://github.com/Growthub-ai/growthub-local/blob/main/CONTRIBUTING.md)
-- [Growthub Authentication Bridge](https://github.com/Growthub-ai/growthub-local/blob/main/docs/GROWTHUB_AUTH_BRIDGE.md)
-- [CLI Workflows Discovery V1](https://github.com/Growthub-ai/growthub-local/blob/main/docs/CLI_WORKFLOWS_DISCOVERY_V1.md)
-- [Worker Kits](https://github.com/Growthub-ai/growthub-local/blob/main/docs/WORKER_KITS.md)
-- [CLI Template Contribution Extension Workflows](https://github.com/Growthub-ai/growthub-local/blob/main/docs/CLI_TEMPLATE_CONTRIBUTION_EXTENSION_WORKFLOWS.md)

package/assets/worker-kits/growthub-zernio-social-v1/QUICKSTART.md

@@ -0,0 +1,209 @@
+# Growthub Zernio Social Media Studio — Quickstart
+
+**Kit:** `growthub-zernio-social-v1`
+**Worker:** `zernio-social-operator`
+**Platform:** [Zernio](https://zernio.com) — unified social media REST API for developers and AI agents
+
+---
+
+## What This Kit Does
+
+The Growthub Zernio Social Media Studio is a self-contained AI agent environment for planning, drafting, scheduling, and analyzing social media campaigns against the Zernio REST API. It produces:
+
+- Social campaign briefs (objective, platforms, audience, KPIs)
+- 30/60/90-day content calendars with theme pillars
+- Platform publishing plans for 14 social networks
+- Caption copy decks with A/B/C variants per post
+- Zernio-shaped scheduling manifests (`POST /api/v1/posts`) + recurring queue definitions
+- Analytics briefings (engagement, reach, growth signals)
+- Client-ready proposals with platform mix and ROI projections
+
+Supported platforms: X/Twitter, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Bluesky, Threads, Google Business, Telegram, Snapchat, WhatsApp. See `docs/platform-coverage.md` for the full list.
+
+---
+
+## Setup — One Command (Mac / Windows / Linux)
+
+From the exported kit folder:
+
+```bash
+node setup/setup.mjs
+```
+
+That single command:
+
+1. Detects your host OS (macOS / Windows / Linux)
+2. Checks dependencies (Node 18+ required; `curl` and `git` optional)
+3. Ensures `.env` exists — if `.env.example` is present it copies it; otherwise prints the exact vars you need to add manually
+4. Runs `setup/verify-env.mjs` to validate your `ZERNIO_API_KEY` format and live-reachability against `GET /api/v1/profiles`
+5. Prints the exact next step for your OS
+
+**No bash required on Windows.** Everything runs under Node. PowerShell, cmd, WSL, git-bash all work identically.
+
+### After the first run
+
+Open `.env` and fill in:
+
+
+| Variable            | Required?            | What to put                                                                                                             |
+| ------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `ZERNIO_API_KEY`    | Yes (for live mode)  | `sk_` + 64 hex characters — create one at [zernio.com/signup](https://zernio.com/signup) or via `POST /api/v1/api-keys` |
+| `ZERNIO_API_URL`    | Yes                  | Default `https://zernio.com/api/v1` — override only for regional / proxy deployments                                    |
+| `ZERNIO_PROFILE_ID` | Yes (for scheduling) | The profile you'll post from — find it in the Zernio dashboard                                                          |
+| `ZERNIO_TIMEZONE`   | Optional             | IANA tz name (e.g. `America/New_York`); defaults to the profile's timezone                                              |
+| `ANTHROPIC_API_KEY` | Optional             | Only for enhanced caption drafting in hybrid mode                                                                       |
+
+
+Re-run `node setup/setup.mjs` after editing `.env` to confirm everything is valid.
+
+### Agent-only mode (no Zernio key needed)
+
+If you just want to plan, write captions, and produce dry-run manifests without touching the Zernio API, skip the key entirely:
+
+```bash
+node setup/setup.mjs --skip-verify
+```
+
+The operator falls back cleanly to `agent-only` mode and produces manifests with `"dryRun": true` that you can submit manually later.
+
+---
+
+## Open Your IDE
+
+Point your IDE's Working Directory at this exported folder. The agent entrypoint is `workers/zernio-social-operator/CLAUDE.md`.
+
+### macOS
+
+```bash
+open .
+# or specifically:
+open -a "Claude" .                 # Claude Desktop with this folder
+code .                             # VS Code / Cursor
+```
+
+### Windows (PowerShell)
+
+```powershell
+start .
+# or specifically:
+code .                             # VS Code / Cursor
+```
+
+### Linux
+
+```bash
+xdg-open .
+code .
+```
+
+Any of these IDEs can drive the operator from this folder:
+
+- Claude Code (CLI)
+- Claude Desktop
+- Codex
+- Cursor
+- Gemini CLI
+- OpenCode
+- Qwen Code CLI
+- Open Agents
+
+See `docs/local-adapters.md` for per-IDE setup notes + optional MCP server install.
+
+---
+
+## What the per-OS paths look like
+
+
+| OS      | Exported kit path after `growthub kit download`                                    |
+| ------- | ---------------------------------------------------------------------------------- |
+| macOS   | `~/paperclip/kits/exports/growthub-agent-worker-kit-zernio-social-v1/`             |
+| Linux   | `~/paperclip/kits/exports/growthub-agent-worker-kit-zernio-social-v1/`             |
+| Windows | `%USERPROFILE%\paperclip\kits\exports\growthub-agent-worker-kit-zernio-social-v1\` |
+
+
+Override the export path with `--out <path>` on `growthub kit download`.
+
+---
+
+## Execution Modes
+
+
+| Mode              | Requirements                                                                 | Use When                                                                                                                                                          |
+| ----------------- | ---------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `api-live`        | Valid `ZERNIO_API_KEY` + at least one connected account on a profile         | You want to schedule posts and queues via the live Zernio API                                                                                                     |
+| `agent-only`      | Nothing — Claude Code handles everything                                     | You need campaign planning, calendars, and captions without touching the Zernio API                                                                               |
+| `hybrid`          | `ANTHROPIC_API_KEY` + valid `ZERNIO_API_KEY`                                 | Enhanced caption drafting via Anthropic plus live Zernio scheduling                                                                                               |
+| `postiz-ui-shell` | `api-live` / `hybrid` + the Postiz kit (`growthub-postiz-social-v1`) running | You want Postiz's UI (calendar, compose, analytics shell) with Zernio as the transport engine. See `docs/postiz-ui-shell-integration.md` for the 7-module bridge. |
+
+
+**Agent-only mode is always valid.** Zernio reachability never blocks campaign planning.
+
+---
+
+## First Run
+
+1. Tell the operator: **"Plan a 30-day Instagram + LinkedIn campaign for [your brand]"**
+2. The operator asks the 4-question gate (client, platforms, objective, cadence)
+3. The operator runs the 10-step workflow and produces all campaign artifacts
+4. Output is saved to `output/<client-slug>/<project-slug>/`
+
+---
+
+## New Client Setup
+
+See `brands/NEW-CLIENT.md` for instructions on adding a new client brand kit.
+
+Quick version:
+
+```bash
+cp brands/_template/brand-kit.md brands/<client-slug>/brand-kit.md
+# Then fill in the fields in the new file
+```
+
+---
+
+## Available Commands
+
+Tell the operator which you need:
+
+
+| Command             | What It Does                                                         |
+| ------------------- | -------------------------------------------------------------------- |
+| `/zernio campaign`  | Full campaign brief + content calendar + publishing plan             |
+| `/zernio calendar`  | Content calendar only — existing brief provided                      |
+| `/zernio captions`  | Caption copy deck for a specific platform or batch                   |
+| `/zernio schedule`  | Generate Zernio-shaped scheduling manifest (`POST /api/v1/posts`)    |
+| `/zernio queue`     | Define or update a recurring Zernio queue (time slots)               |
+| `/zernio analytics` | Analytics briefing from Zernio API metrics or provided data          |
+| `/zernio inbox`     | Draft replies for DMs, comments, reviews in the Zernio unified inbox |
+| `/zernio proposal`  | Client-ready proposal with platform mix and ROI projection           |
+| `/zernio platforms` | Platform coverage report for a specific client context               |
+| `/zernio quick`     | 30-second campaign snapshot for a domain or brand                    |
+
+
+---
+
+## Key Files
+
+
+| File                                       | Purpose                                                                                                |
+| ------------------------------------------ | ------------------------------------------------------------------------------------------------------ |
+| `setup/setup.mjs`                          | **One-command cross-platform bootstrap — start here**                                                  |
+| `setup/verify-env.mjs`                     | Validates `ZERNIO_API_KEY` + live reachability                                                         |
+| `setup/check-deps.mjs`                     | Cross-platform Node dependency check (Windows parity)                                                  |
+| `setup/check-deps.sh`                      | Legacy Unix bash dependency check (Mac / Linux)                                                        |
+| `setup/install-mcp.mjs`                    | Prints per-IDE MCP config JSON for plugging in Zernio's official MCP server                            |
+| `workers/zernio-social-operator/CLAUDE.md` | Agent operating instructions                                                                           |
+| `skills.md`                                | Full methodology — read at every session                                                               |
+| `brands/_template/brand-kit.md`            | Blank brand kit template                                                                               |
+| `brands/growthub/brand-kit.md`             | Growthub reference example                                                                             |
+| `output/README.md`                         | Output directory structure and naming                                                                  |
+| `docs/zernio-api-integration.md`           | How this kit integrates with Zernio (REST contract + plans + capability surface)                       |
+| `docs/platform-coverage.md`                | All 14 supported platforms with format specs                                                           |
+| `docs/ai-caption-layer.md`                 | AI caption generation methodology                                                                      |
+| `docs/posts-and-queues-layer.md`           | Scheduling manifest + queue format for Zernio API                                                      |
+| `docs/local-adapters.md`                   | Per-IDE setup matrix (Claude Code / Desktop / Codex / Cursor / Gemini / OpenCode / Qwen / Open Agents) |
+| `docs/postiz-ui-shell-integration.md`      | Optional — run this kit as the engine under the Postiz UI shell                                        |
+| `validation-checklist.md`                  | Pre-session checklist                                                                                  |
+
+

package/assets/worker-kits/growthub-zernio-social-v1/brands/NEW-CLIENT.md

@@ -0,0 +1,74 @@
+# Adding a New Client
+
+This guide explains how to create a brand kit for a new client in the Zernio Social Media Studio.
+
+---
+
+## Steps
+
+### 1. Copy the Template
+
+```bash
+cp brands/_template/brand-kit.md brands/<client-slug>/brand-kit.md
+```
+
+Replace `<client-slug>` with a lowercase, hyphenated version of the client name. Examples:
+- "Urban Cycle" → `urban-cycle`
+- "Acme SaaS Corp" → `acme-saas`
+- "The Bloom Studio" → `bloom-studio`
+
+### 2. Fill in the Brand Kit
+
+Open the new file and fill in every section:
+
+- **Client Identity** — name, slug, industry, website
+- **Zernio Account Context** — profile id, timezone, API key scope
+- **Social Media Presence** — existing accounts with Zernio platform ids and account ids
+- **Target Audience** — primary and secondary audience profiles
+- **Campaign Objectives** — metrics, targets, and timelines
+- **Brand Voice** — tone, personality, approved/blocked words, emoji usage
+- **Content Theme Pillars** — 3–5 recurring themes with platform assignments
+- **Competitor Reference Accounts** — 2–3 accounts to reference for format benchmarking
+- **Benchmark Reference** (optional) — baseline engagement rates per platform
+- **Agency Context** — engagement stage, retainer, reporting cadence
+
+### 3. Verify the Brand Kit
+
+Before using the brand kit in a session, confirm:
+
+- [ ] `client-slug` in the filename matches the `Client Slug` field in the kit
+- [ ] At least one platform is listed in `Social Media Presence` with a Zernio platform id from `docs/platform-coverage.md`
+- [ ] At least one campaign objective has a measurable target
+- [ ] Brand voice section is complete — no empty `[fill in]` placeholders
+- [ ] At least 3 content theme pillars are defined
+- [ ] `Zernio profile id` either references a real `prof_...` or is tagged `placeholder` (agent-only mode)
+
+### 4. Tell the Operator
+
+Start your Claude Code session and say:
+
+> "Load the brand kit for [client-name] and begin a [campaign objective] campaign."
+
+The operator will read the brand kit and ask the 4-question gate before producing any output.
+
+---
+
+## Brand Kit Naming Rules
+
+| Rule | Correct | Incorrect |
+|---|---|---|
+| Directory name is lowercase kebab-case | `brands/urban-cycle/` | `brands/UrbanCycle/` |
+| Filename is always `brand-kit.md` | `brands/urban-cycle/brand-kit.md` | `brands/urban-cycle/UrbanCycle.md` |
+| Slug contains no spaces | `acme-saas` | `acme saas` |
+| Slug contains no special chars | `bloom-studio` | `bloom/studio` |
+
+---
+
+## Note on Public Brand Kits
+
+Brand kits are **not included in kit exports by default**. The only brand kits included in exports are:
+
+- `brands/_template/brand-kit.md` — the blank template
+- `brands/growthub/brand-kit.md` — the public reference example
+
+Client brand kits you create live in your local kit installation only. They are not bundled into the export zip or submitted to any external service.

package/assets/worker-kits/growthub-zernio-social-v1/brands/_template/brand-kit.md

@@ -0,0 +1,131 @@
+# Brand Kit — [Client Name]
+
+<!-- Replace [Client Name] with the actual client name and rename this file to brands/<client-slug>/brand-kit.md -->
+
+---
+
+## Client Identity
+
+| Field | Value |
+|---|---|
+| Client Name | [Client Name] |
+| Client Slug | [client-slug] |
+| Industry | [e.g., SaaS / E-commerce / Hospitality / Fintech] |
+| Website | [https://...] |
+| Primary Contact | [Name, email] |
+
+---
+
+## Zernio Account Context
+
+| Field | Value |
+|---|---|
+| Zernio profile id | [prof_...] or `placeholder` in agent-only mode |
+| Default posting timezone | [IANA tz, e.g., America/New_York] |
+| API key scope | [read | read-write] |
+| Profile-specific key? | [yes | no] |
+
+---
+
+## Social Media Presence
+
+| Platform | Zernio platform id | Account id / handle | Followers | Current Status |
+|---|---|---|---|---|
+| Instagram | `instagram` | [acc_ig_... or @handle] | [N] | [Active / Inactive / New] |
+| LinkedIn | `linkedin` | [page id] | [N] | [Active / Inactive] |
+| TikTok | `tiktok` | [acc_tt_...] | [N] | [Active / Inactive] |
+| X/Twitter | `twitter` | [acc_x_...] | [N] | [Active / Inactive] |
+| [Other] | [id] | [handle] | [N] | [Active / Inactive] |
+
+---
+
+## Target Audience
+
+### Primary Audience
+
+| Attribute | Description |
+|---|---|
+| Age Range | [e.g., 25–40] |
+| Gender | [e.g., 55% female, 45% male] |
+| Location | [e.g., North America, English-speaking markets] |
+| Interests | [e.g., entrepreneurship, productivity, design] |
+| Pain Points | [e.g., too many disconnected tools, manual social media posting] |
+| Content Preferences | [e.g., educational how-tos, success stories, data-driven insights] |
+
+### Secondary Audience
+
+| Attribute | Description |
+|---|---|
+| Age Range | [e.g., 18–25] |
+| Interests | [e.g., tech, side projects] |
+| Platform | [e.g., TikTok, Reddit] |
+
+---
+
+## Campaign Objectives
+
+| Objective | Metric | Target | Timeline |
+|---|---|---|---|
+| [Brand awareness] | [Impressions] | [50,000/month] | [Q2 2026] |
+| [Lead generation] | [Link clicks] | [200/month] | [Q2 2026] |
+| [Community growth] | [Follower growth] | [+500] | [Q2 2026] |
+
+---
+
+## Brand Voice
+
+| Attribute | Spec |
+|---|---|
+| Tone | [e.g., Professional but approachable. Data-driven without being dry. Never salesy.] |
+| Personality | [e.g., Smart, helpful, occasionally witty] |
+| Words to Use | [e.g., "build", "grow", "automate", "team", "results"] |
+| Words to Avoid | [e.g., "hack", "guru", "crush it", "cheap", "amazing"] |
+| Emoji Usage | [e.g., Minimal on LinkedIn; moderate on Instagram; more on TikTok] |
+| CTA Style | [e.g., Direct action verbs: "Start today", "Learn more", "Join the team"] |
+
+---
+
+## Content Theme Pillars
+
+| Pillar | Description | Platforms | % of Calendar |
+|---|---|---|---|
+| [Industry Insights] | [What we know that others don't — data, trends, analysis] | [All] | [40%] |
+| [Product Value] | [Feature spotlights, use cases, ROI stories] | [LinkedIn, Instagram] | [30%] |
+| [Social Proof] | [Customer testimonials, case studies, results] | [All] | [20%] |
+| [Community] | [Q&A, behind the scenes, team moments] | [Instagram, TikTok] | [10%] |
+
+---
+
+## Competitor Reference Accounts
+
+| Platform | Account | Why Reference |
+|---|---|---|
+| [Instagram] | [@competitor] | [Strong visual brand, good engagement format] |
+| [LinkedIn] | [competitor company page] | [Industry leader, consistent posting cadence] |
+
+---
+
+## Agency Context
+
+| Field | Value |
+|---|---|
+| Engagement Stage | [Prospect / Onboarding / Retained] |
+| Monthly Retainer | [e.g., $X,XXX/month or "not established"] |
+| Campaign Budget | [e.g., $X,XXX / campaign or "TBD"] |
+| Reporting Cadence | [e.g., Monthly analytics brief] |
+
+---
+
+## CRM Notes
+
+<!-- Internal notes for agency context. Not included in client-facing outputs. -->
+
+[Add internal notes here: key contacts, relationship history, upsell opportunities, account health signals]
+
+---
+
+## DELIVERABLES LOG
+
+<!-- Append a line for each completed deliverable. -->
+
+<!-- - YYYY-MM-DD | Social Media Campaign Package v1 — [Project Name] | output/<client-slug>/<project-slug>/ -->