# Higgsfield production package

**Product:** Premiere Pro MCP
**Market:** Professional Adobe Premiere Pro workflow automation
**Date:** 2026-08-22
**Research scope:** Copy/paste-ready candidate prompts for future production; no media was generated and no provider credits were used.
**Status:** Human-review-only production brief; requires exact batch, cost, rights, and product-fidelity approval before generation.

## Production invariants

- Use only real, approved product recordings and screenshots captured from an identified Premiere version and connector build (`CRE-001`, `INS-003`).
- Never synthesize a Premiere interface, result receipt, customer logo, testimonial, marketplace badge, or editing outcome.
- Preserve all visible product text exactly. Do not add “production-ready,” “approved,” “hours saved,” or pricing claims.
- Keep the local-first qualification: the selected AI client has separate privacy settings (`CRE-002`, `SRC-001`).
- Any generated texture or abstract transition is illustrative only and must not impersonate the product UI.

## CRE-001 — Evidence receipt

**Use:** 10–15 second activation/consideration video.
**Evidence:** `INS-001`, `INS-003`.
**Required supplied references:** Approved screen recording of the read-only safe-check, host/version label, approved text transcript.

### Image prompt

```text
Create a polished editorial-tech key visual using ONLY the supplied approved product screenshot as the UI source. Show a real Premiere Pro MCP workflow receipt beside a restrained dark-neutral post-production workspace. Composition: ample negative space for headline, crisp typography-safe margins, subtle warm monitor glow, documentary product-photography feeling. Preserve every word, value, icon, and layout in the supplied screenshot exactly; do not invent menus, timelines, success badges, customer logos, metrics, or Adobe endorsement. Add no readable text except the supplied screenshot. 16:9.
```

### Video prompt

```text
Create a 12-second product-led edit using ONLY supplied real screen recordings and approved screenshots. Start with the exact read-only safe connection check, then show the real plan/preview state, then explicit confirmation, then the real structured verification receipt. Use slow, precise cuts and a calm dark-neutral editorial treatment. Overlay only this approved copy: “Inspect. Preview. Approve. Verify.” End with: “Run the safe connection check.” Preserve all UI exactly; do not synthesize Premiere controls, edit results, customer logos, testimonials, security claims, marketplace badges, or claims about hours saved. Include a small host/version label from supplied footage. 16:9.
```

| Time | Shot | Copy | Requirement |
|---:|---|---|---|
| 0–3s | Real safe-check prompt and response | “Inspect.” | Exact product capture |
| 3–6s | Real workflow plan | “Preview.” | No fabricated plan data |
| 6–9s | Real explicit confirmation | “Approve.” | Only if workflow genuinely requires it |
| 9–12s | Real result receipt | “Verify. Run the safe connection check.” | Host/version label visible |

## CRE-002 — Local control path

**Use:** 8–12 second awareness video / architecture still.
**Evidence:** `INS-001`, `INS-007`.
**Required supplied references:** Approved architecture wording and brand colors.

### Image prompt

```text
Create a refined dark-neutral editorial diagram, not a product UI. Four clearly separated nodes: “AI client”, “Local MCP server”, “Local Premiere connector”, “Premiere Pro”. Connect them with thin directional lines labeled “structured request” and “structured result”. Place a clear, small footnote: “Your AI client has separate privacy settings.” Use understated technical typography, generous spacing, high contrast, no gradients that reduce readability, no Adobe logo, no cloud icon implying a privacy guarantee. 16:9.
```

### Video prompt

```text
Create a 10-second high-clarity motion diagram. Reveal the nodes in this exact order: AI client, Local MCP server, Local Premiere connector, Premiere Pro; animate a structured request moving right and a structured result moving left. Use quiet, precise motion and dark-neutral post-production styling. On-screen copy: “Local-first workflow control.” Then: “Your AI client has separate privacy settings.” Do not show media files, cloud claims, security badges, Adobe logos, fabricated application windows, pricing, or performance claims. 16:9.
```

| Time | Shot | Copy | Requirement |
|---:|---|---|---|
| 0–3s | Node reveal | “Local-first workflow control.” | Exact topology |
| 3–7s | Request/result animation | None | Direction labels remain readable |
| 7–10s | Privacy qualification | “Your AI client has separate privacy settings.” | Required qualification |

## CRE-003 — Workflow pack

**Use:** 12–15 second team/consideration video.
**Evidence:** `INS-005`, `INS-006`.
**Required supplied references:** Host-tested workflow card data, maturity labels, and approved compatibility notes.

### Image prompt

```text
Create a premium editorial workflow-pack graphic with three factual cards only: “Project Intake”, “Platform Cutdowns”, and “Delivery Preflight”. Each card includes neutral placeholders labeled “Supported host/version”, “Plan”, “Confirm”, and “Verify”; replace placeholders only from supplied approved workflow data. Use a dark-neutral post-production aesthetic, simple hierarchy, and room for real compatibility labels. Do not claim team adoption, time saved, automation success, Adobe Marketplace availability, or production readiness. 16:9.
```

### Video prompt

```text
Create a 15-second product concept video using supplied host-tested workflow cards. Show one card at a time: Project Intake, Platform Cutdowns, Delivery Preflight. For each, animate the same sequence: inspect, plan, confirm, verify. Overlay only: “Make repeatable work reviewable.” End: “Start with the safe connection check.” Use supplied factual host/version labels. Do not fabricate workflow results, customer evidence, marketplace listing, prices, or claims that every host supports every workflow. 9:16 and 16:9 versions.
```

| Time | Shot | Copy | Requirement |
|---:|---|---|---|
| 0–4s | Project Intake card | “Inspect.” | Approved host data |
| 4–8s | Platform Cutdowns card | “Plan. Confirm.” | Mark planned/beta if unverified |
| 8–12s | Delivery Preflight card | “Verify.” | Approved result language |
| 12–15s | Three-card recap | “Make repeatable work reviewable.” | No adoption/time claim |

## Variant register

| ID | Concept | Meaningful variable | State |
|---|---|---|---|
| CRE-001A | Evidence receipt | Starts with safe-check prompt | pending approval |
| CRE-001B | Evidence receipt | Starts with verification receipt | pending approval |
| CRE-002A | Local control path | Topology-first opening | pending approval |
| CRE-003A | Workflow pack | Project Intake first | pending approval |
| CRE-003B | Workflow pack | Delivery Preflight first | pending approval |

## Next actions

1. Obtain approved host recordings and factual workflow-card data before any prompt is used (`INS-003`).
2. Get an exact paid-provider batch, cost, rights, and review approval before Higgsfield generation.
3. Conduct product-fidelity, accessibility, brand, and legal review on every output (`CRE-001`–`CRE-003`).

**Owner:** Creative operations lead
**Approval needed:** Explicit batch-and-credit approval, input-asset rights approval, product fidelity approval, and final publication approval.
**Completion criteria:** All production inputs are approved, every output passes the invariant checklist, and no candidate asset is published without human sign-off.