Claude Code-native · AI-UGC system

AI-UGC videos that learn from every post.

Every reel is revenue or data.

UGC Engine produces, scores, and iteratively improves AI short-form video and carousels — so every piece of content compounds into a smarter system. For founders running short-form at volume without a content team.

See how it works

The Loop

A self-improving content engine

Each cycle feeds the next. Performance data from published content shapes every future generation.

Research

Competitor hooks, trending audio, winning formats

Generate

8 parallel Higgsfield renders per campaign

Score

Hook rate, watch-time, engagement — logged to DB

Improve

Insights feed next iteration — every cycle compounds

revenue → data → better content → more revenue

Features

Built for compounding returns

Every component was designed to feed the next. The longer it runs, the better it gets.

Compounding performance DB

Every published piece feeds a structured Obsidian + filesystem database. Hook rates, watch-time, and engagement scores accumulate — each generation starts smarter than the last.

filesystem + Obsidian

Higgsfield generation

8 parallel renders per campaign. Variations in hook, pacing, and visual treatment — scored before you ever touch the publish button.

8 parallel renders

Multi-platform output

TikTok, Reels, Shorts, and carousels — each format tuned for its platform's algorithm, aspect ratio, and caption conventions.

TikTok · Reels · Shorts · Carousels

Claude Code-native

Runs entirely inside Claude Code. Slash commands and agents orchestrate every stage — no separate dashboard, no context switching.

slash commands + agents

How it works

Intentionally simple

No new tools to learn. The complexity lives in the system — the interface is files, folders, and a few commands.

01

Project = directory

Every UGC Engine project is a plain directory. Config, scripts, templates, and outputs live alongside your Claude Code session — no external app, no database to spin up.

one directory, one project
02

Filesystem + Obsidian = DB

Performance data is structured markdown — hook scores, watch-time breakdowns, format wins. Obsidian is the query layer. No SQL, no schema migrations.

portable · auditable · queryable
03

Never auto-publish

UGC Engine generates and scores — it never posts. Every publish is a deliberate human tap. This keeps accounts safe and keeps you in control of brand, timing, and quality.

human tap required · zero auto-posting

Core principles

Precision

Targeted hooks, formats, and audiences — not spray and pray.

Compounding

Every output makes the next output better. That's the only moat.

Decoupled modules

Research, generation, scoring, distribution — each replaceable independently.

Human in the loop

Automate the craft, not the judgment. You decide what ships.

Filesystem-first

Data that lives in files is data you own, audit, and query forever.