No face. No team. No two-year grind. One operator, three tools, one system - Higgsfield + Claude Code + YouTube. This is the full setup, the content engine, every prompt, and the code where you need it.

Section 0

THE FULL SETUP

Get this stack live before you write a single script. Budget one afternoon.

Accounts & tools

Claude Code - install the CLI. This is your scriptwriter, researcher, packager, and pipeline brain. npm i -g @anthropic-ai/claude-code

Higgsfield - create an account and load credits. Your intro stings, b-roll, animated overlays, and thumbnail variants come from here (30+ generative models).

YouTube / Google account - create the channel, set the handle, banner, and "about". Enable 2FA.

Google Cloud project - needed only if you automate uploads/metadata via the YouTube Data API (Section 4). Optional but powerful.

Capture + edit - OBS (free) for gameplay capture; any NLE you like (DaVinci Resolve is free and strong). FFmpeg for compression/frame work.

Wire Higgsfield into Claude Code (MCP)

Connecting Higgsfield as an MCP server lets Claude request and pull visual assets directly instead of you exporting by hand. Add it to your Claude Code MCP config:

{

"mcpServers": {

"higgsfield": {
 
  "command": "npx",
 
  "args": ["-y", "higgsfield-mcp"],
 
  "env": {
 
    "HIGGSFIELD_API_KEY": "YOUR_KEY_HERE"
 
  }
 
}

}

}

Project scaffold

Create one folder per channel so Claude Code has persistent context. Inside, keep a CHANNEL.md that defines your format, tone, and rules - Claude reads it every session.

gaming-channel/

├─ CHANNEL.md # format, tone, audience, do/don't

├─ scripts/ # generated video scripts

├─ packaging/ # titles, descriptions, thumbnail briefs

├─ assets/ # higgsfield exports, gameplay clips

├─ pipeline/ # upload + metadata scripts (Section 4)

└─ log.csv # every video: title, CTR, retention, subs

Section 1

POSITIONING - THE PART EVERYONE SKIPS AND LOSES

You don't beat IGN. You out-angle them. A channel that "reviews games" is invisible. A channel with a format is a brand.

Pick ONE wedge and commit for 90 days:

Section 2

THE CONTENT ENGINE

The daily loop. Once dialed, a finished, packaged video takes hours - not days.

Section 3

THE PROMPT LIBRARY

Copy-paste these into Claude Code. Fill the [brackets]. They build on each other across one session.

Prompt 0 - CHANNEL.md (set context once)

You are the producer for my YouTube game-review channel.

CHANNEL: [name]

FORMAT: [e.g. 90-second verdict reviews — sharp buy/skip calls]

AUDIENCE: [e.g. 18–30 core gamers short on time and money]

TONE: confident, fast, a little contrarian. No filler, no "hey guys".

VIDEO LENGTH: 8–12 min for full reviews, 30–45s for Shorts.

RULES:

• Every script opens with a 5-second hook stating the stakes or the verdict.

• Plant at least one open loop that pays off later.

• End every video with a specific CTA (subscribe + next video tease).

• Never pad. If a section doesn't earn its seconds, cut it.

When I give you a game, follow this unless I say otherwise.

Prompt 1 - Topic selection

Here are [10] games I'm considering: [list].

Rank them for my channel by: (1) current search/interest momentum,

(2) recency or a timely hook, (3) how saturated coverage already is.

For the top 3, give me the exact angle that would stand out and a

one-line hook I could open the video with.

Prompt 2 - Full script

Write a [10-minute] review script for [GAME].

Context to use: [paste patch notes / your impressions / key facts].

Structure:

• HOOK (≤5s): state the verdict or the stakes, no intro fluff.

• CONTEXT (30-45s): what it is, who it's for, why now.

• THE MEAT: 3–4 sections (gameplay, content, value, the catch).

  Open a loop early and pay it off in the verdict.

• VERDICT: clear buy / wait / skip with the one reason that decides it.

• CTA: subscribe + tease the next video.

Mark [B-ROLL] cues where I should drop Higgsfield motion or gameplay.

Write it as spoken VO - short sentences, punchy, no corporate tone.

Prompt 3 - Higgsfield visual brief

From this script, build a Higgsfield shot list:

• 1 cinematic intro sting (3-5s) matching the channel mood: [mood].

• A b-roll clip for each [B-ROLL] cue - give me the text prompt for each,

  3–6 seconds, high contrast, readable at small size.

• 3 thumbnail concepts: each must make ONE bold claim, big readable subject,

high emotion. Describe the image prompt + the 2-4 word text overlay.

Prompt 4 - Packaging (titles, description, chapters)

For this video, give me:

• 8 title options ranked by curiosity + searchability (≤60 chars).

  Mix a clear-keyword title and a curiosity-gap title.

• A description: hooked first line, 2-3 sentence summary, timestamped

  chapters from the script, and 8-10 relevant tags/keywords.

• A pinned comment that seeds a debate to drive replies.

Prompt 5 - Shorts cutdown

Find the single sharpest 30-40 seconds in this script for a vertical Short.

Rewrite it to stand alone: hook in the first 2 seconds, one punchy payoff,

end on a line that makes them want the full review. Give me the on-screen

captions too.

Prompt 6 - Weekly retrospective

Here's my log.csv [paste rows: title, CTR, avg view duration, subs gained].

Tell me: which hook style and thumbnail style are winning, which topics

overperform, and what to make MORE of next week. Be blunt. If something's

dead, tell me to kill it.

Section 4

CODE & CONFIG - ONLY WHERE IT EARNS ITS KEEP

You can run the whole channel with zero code. But three small scripts remove the most boring manual work: compression, frame extraction, and bulk uploads.

A · Compress + extract frames (FFmpeg)

Higgsfield exports are high-res. Compress before editing, and pull stills for thumbnails. Claude Code can run these for you.

compress a clip for the timeline (smaller, still crisp)

ffmpeg -i intro_raw.mp4 -vcodec libx264 -crf 23 -preset slow \

-vf "scale=1920:-2" intro.mp4

extract a frame at 2s as a thumbnail base

ffmpeg -i hero.mp4 -ss 00:00:02 -vframes 1 thumb_base.png

make a vertical 9:16 crop for a Short

ffmpeg -i clip.mp4 -vf "crop=ih*9/16:ih,scale=1080:1920" short.mp4

B · Auto-generate metadata files

Have Claude Code write each video's packaging to a JSON the upload script reads. Keeps titles/descriptions versioned in your repo.

{

"file": "assets/elden_ring_review.mp4",

"title": "Is Elden Ring Still Worth It in 2026?",

"description": "The honest verdict...\n\n00:00 Hook\n00:30 What changed\n...",

"tags": ["elden ring","souls","review","2026","worth it"],

"categoryId": "20",

"privacyStatus": "private",

"publishAt": "2026-07-01T17:00:00Z"

}

C · Upload to YouTube (Data API v3)

Optional but a real time-saver once you're shipping 4-5/week. Set up a Google Cloud project, enable the YouTube Data API v3, create OAuth credentials, then:

pip install google-api-python-client google-auth-oauthlib

import json, sys

from google_auth_oauthlib.flow import InstalledAppFlow

from googleapiclient.discovery import build

from googleapiclient.http import MediaFileUpload

SCOPES = ["https://www.googleapis.com/auth/youtube.upload"]

def service():

flow = InstalledAppFlow.from_client_secrets_file("client_secret.json", SCOPES)
 
creds = flow.run_local_server(port=0)
 
return build("youtube", "v3", credentials=creds)

def upload(meta_path):

m = json.load(open(meta_path))
 
yt = service()
 
body = {
 
    "snippet": {
 
        "title": m["title"],
 
        "description": m["description"],
 
        "tags": m.get("tags", []),
 
        "categoryId": m.get("categoryId", "20"),  # 20 = Gaming
 
    },
 
    "status": {
 
        "privacyStatus": m.get("privacyStatus", "private"),

        "publishAt": m.get("publishAt"),  # schedules the drop
 
        "selfDeclaredMadeForKids": False,
 
    },
 
}
 
media = MediaFileUpload(m["file"], chunksize=-1, resumable=True)
 
req = yt.videos().insert(part="snippet,status", body=body, media_body=media)
 
res = req.execute()
 
print("Uploaded:", res["id"])

if name == "main":

upload(sys.argv[1])   # python upload.py packaging/elden_ring_review.json

Section 5

THE 90-DAY SPRINT

100K in three months is the aggressive-case target. You hit it by stacking the right inputs, then letting one video break out. Cadence beats perfection.

Section 6

THE METRICS THAT ACTUALLY MOVE THE NUMBER

Forget vanity. Three numbers decide everything - and they tell you exactly what to fix.

Section 7

MONETIZATION - DON'T WAIT FOR IT

YouTube Partner Program - 1,000 subs + 4,000 watch hours, or the Shorts path. On this cadence you clear it inside 90 days.

Affiliates - game stores, hardware, peripherals. Reviews convert because the viewer is already in buying mode.

Sponsorships - studios and publishers pay for coverage once you have reach. A focused 50K niche channel often out-earns a scattered 200K one.

Your own funnel - Discord, newsletter, eventually a product. The channel is the top of it.

The honest part: 100K in 90 days is the ceiling, not the guarantee. What's guaranteed is that the cost and time that used to gatekeep a polished gaming channel are gone. One operator with Claude Code + Higgsfield ships studio-grade reviews daily for the price of a coffee per video.

The pipeline was the moat. It just became a prompt.

Save it & build today.

Links

• www.googleapis.com/auth/youtube.upload
• flow.run
• upload.py