UGC.md: Your Content Operating System

The file that makes every Claude prompt specific to your offer, your audience, and your proven content

UGC.md is the file that makes every Claude prompt in this course specific to your offer, your audience, and your proven content. Without it Claude writes generic UGC scripts. With it Claude writes scripts in your voice, targeting your exact audience, referencing your actual proof, and building on hook angles that have already worked for you.

This lesson builds the complete file.

Why UGC.md Works

Claude has no memory between conversations. Each session starts fresh. UGC.md is the context that resolves this because it carries everything Claude needs to write content that sounds like it belongs to your business and not any business.

After 2 to 3 months of use, UGC.md contains your hook bank, your winning scripts, your tested angles, and your content performance log. This is not something you can recreate from memory in a prompt. It compounds.

The Complete UGC.md Template

Copy this template and fill in every section:

# UGC.md — Content Operating System
Last updated: [DATE]
## What I'm Selling and for Whom

Primary offer: [One paragraph describing exactly what you build, for whom,

and what the outcome is. Be specific — not "web development services" but

"I build booking systems, client portals, and process automations for UK

local service businesses: salons, physios, consultants, tradespeople.

Fixed price, delivered in 1 to 5 days, client owns the code."]

Secondary offers: [Other services you offer, if any]

Landing page / booking process: [Where UGC viewers should be sent and

what happens after they click]

Price range: [Be honest — this helps Claude calibrate the CTA appropriately]

## Target Audience

Who sees this content:

• Role/type: [e.g. Owner or manager of a UK local service business —

salon, clinic, consultancy, trade]

• Company size: [e.g. 1 to 10 staff, solo to small team]
• Geography: [e.g. UK, primarily England]
• Age range: [e.g. 28 to 52]

Their specific frustration right now:

• [Write 3 to 5 sentences in their language and not your language. What
• would they say if complaining to a friend about the problem you solve?

Include the specific pain: "I spend half my Sunday doing admin for the

week ahead — confirming bookings by text, reminding people, chasing

no-shows, re-entering everything into the calendar by hand."]

What they want:

• [What does success look like to them? Not "efficiency" but the specific
• thing: "Clients booking online, reminders going out automatically, no
• calls to answer, no no-shows to chase."]

What makes them distrust people like me:

• [What has burned them before? "Previous web developer went silent
• mid-project. Quoted £5,000 for something they later found on Fiverr
• for £400. Paid for a website that didn't convert."]

## Platforms I'm Publishing On

Primary: [e.g. Instagram Reels]

Secondary: [e.g. Facebook Reels / TikTok / YouTube Shorts]

Running as ads: [Yes / No / Planned]

## Proof Points

[This section grows over time as you collect client results. Start with

what you have.]

Proof 1:

• Client context: [Type of business, not name]
• Problem: [Specific situation before]
• Result: [Specific measurable outcome]
• Time frame: [How long after implementation]

Example: "Hair salon, 20 appointments per week, 22% no-show rate

dropped to 4% no-show rate, £380 per week recovered. First 30 days."

Proof 2:

[Same format]

Own experience (if no client results yet):

[Describe something you built for yourself or a process proof]

## Hook Bank

[Empty when you start. Populated as you write and test hooks. Mark

performance when available.]

Format: Hook text | Type | Status | CTR if tested

Hook 1: [TEXT] | [TYPE] | Untested
Hook 2: [TEXT] | [TYPE] | Untested

[Add confirmed winners with CTR data as you get it]

## Scripts

[Store finalised scripts here for reference and variation requests]

Script 01:

• Title: [Short descriptor]
• Format: [Talking Head / Screen Recording / Tutorial]
• Platform: [Instagram Reels / Meta Ad]
• Length: [duration]
• Hook angle: [Problem / Outcome / Question / etc.]
• Performance: [Organic views / CTR if run as ad]

Script:

[PASTE SCRIPT TEXT]
## Content Log

[One line per piece of content produced or published]

Format: Date | Format | Hook type | Platform | Organic performance |

Ad performance if run

[DATE] | Talking Head | Problem hook | Instagram Reels |

1,240 views 12 saves | —

[DATE] | Screen Recording | Outcome hook | Meta Ad |

— | 2.8% CTR £31 CPL

## Claude Prompt Templates

For a new script:

Using @UGC.md and @SALES.MD — write a UGC script in the [FORMAT] format
for [PLATFORM]. Use the proof points from UGC.md, the audience language

from SALES.MD, and build on hook angles that have worked as listed in

the Hook Bank.

For a new hook batch:

• Using @UGC.md — write 10 new video hooks. Two in each of the five styles
• from the hooks lesson. Use audience language from the Target Audience
• section. Rate each 1 to 10 for pattern interrupt strength.

For a creator brief:

Using @UGC.md and @SALES.MD — write a UGC creator brief for a [FORMAT]

video. Include brand overview, objective, script guidelines not

word-for-word, proof to mention, CTA, technical specs, and usage rights

required.

For reviewing performance and planning next content:

Using @UGC.md — here is my content performance from this week:

[PASTE DATA]

Tell me which angles are working, which to retire, what format to try

next, and write 5 hook variations of the angle with the best results.

Maintaining UGC.md Over Time

Update it after every piece of content you publish. Add the hook to the Hook Bank. Add the script to the Scripts section. Add one line to the Content Log.

Update it every time you get performance data. Mark tested hooks with their CTR in the Hook Bank. Mark scripts with organic views and ad metrics. Add new proof points when clients give you results.

After 3 months UGC.md contains a tested hook bank with actual performance data, scripts that have converted, your best proof points ready to reference, and a clear picture of which formats work for your audience.

Every session where you write new content becomes faster and more targeted. You spend less time briefing Claude and more time on the content itself.

Linking UGC.md to Your Other Files

UGC.md works alongside the other operating system files from this track.

MARKETING.md provides audience voice and brand positioning. SALES.md provides offer details, objections, and client language. EMAIL.md provides prospect communication style. ADS.md which you build in the next course provides paid campaign metrics and hook performance.

When you start a UGC session that is going to be run as an ad, reference all four. Claude then has the complete picture: who the audience is, what the offer is, what the ad metrics look like, and which content has already worked.