PROD. SECOND UNIT UGC/RUNNING GLOSSARY — DEFINITION SOURCE/Explain on first use/Owned by Module 1.5 · verified 2026-08-14

Referencecross-cutting-reference1,163 words  ·  four sections, one avoid-list

Glossary

The shared definition source for every term the guide introduces. Don’t read it front to back — come back when a word turns up that you half-recognise.

filters as you type

One plain line per term, plus where it is properly explained. Don't read this front to back. Come back to it when a word turns up that you half-recognise.

This exists because of a rule in blueprint §1: terms are explained on first use, never avoided. A guide that dodges the vocabulary leaves you fluent in nothing and unable to read anyone else's documentation. This file is what makes that rule enforceable instead of a matter of each writer's judgement.

Adding to it is not optional. Anything the guide introduces gets a line here, in the pass that introduces it.


1Using the tools

TermIn one lineExplained in
ClaudeThe app you type into, and the model behind it. Made by Anthropic1.5 §1
ModelSoftware trained on a lot of text until it got good at continuing text sensibly1.5 §1
Chat / conversationOne continuous exchange. Start a new one and it knows nothing about the last1.5 §3
ContextEverything the model can currently see — this conversation, plus anything loaded. Not in context, doesn't exist1.5 §3
PromptWhat you type. An instruction, not a search query — the most load-bearing definition in the guide1.5 §4
BriefThis guide's preferred word for a prompt: the request plus every constraint attached to it2 §1
MemoryOpt-in. A best-effort synthesis carried between chats. Useful; never where guardrails live1.5 §3
Incognito chatA chat saved to neither memory nor history1.5 §3
Usage limitsCaps on how much you can do in a period. Apply on every plan, free included. They reset1.5 §2
Extended thinkingThe model working longer on a harder problem before answering1.5 §2

2Organising work

TermIn one lineExplained in
ProjectA self-contained workspace with its own chats and its own knowledge base. One per client2 §8
Knowledge baseThe files inside a project that every chat in it can see. The shared part2 §8
Project instructionsStanding behavioural rules applied to every chat in one project. Not the same as the knowledge base2 §8
RAGRetrieval-augmented generation. Relevant parts of a large knowledge base get pulled in as needed. You don't configure it2 §8
SkillA folder with a SKILL.md in it — standing instructions for a job, written once. No plan gate2 skills
ConnectorLets Claude reach into an app you already use, instead of you copy-pasting between windows2 §7
PluginA bundle of skills and connectors installed together. Paid plans only2 §7
MCPModel Context Protocol. The plumbing behind custom connectors. You almost certainly don't need it2 §7
CoworkThe agentic surface — describe an outcome, walk away, come back to finished work. Paid plans only2 §6
AgenticSomething acting on your behalf across several steps, rather than answering one message2 §2
Hand-offThis guide's word for agentic work: you describe the finished thing, the tool holds the loop2 §2

3The craft

TermIn one lineExplained in
UGCUser-generated content. Content made by a creator that a brand pays for and uses as its own0A
NicheThe specific thing you're known for. Noticed from what you already use, not invented — the whole point of Module 0B0B
Content pillarA recurring shape of post you can make repeatedly without a new idea each time. Not a topic0A §4
Spec workSomething you made unpaid and uncommissioned, to show what you can do. Fine to show; must be labelled4 §3
HookThe opening line. The thing that decides whether the rest is watched2 §1
BeatA job a piece has to do, not a unit of time. Adjacent beats can share a shot2 templates
TakeOne recorded attempt. Numbered, kept, and shown — including the ones that failed4
DeliverableThe thing the brand is actually buying, defined in the contract, not in the vibe0A
Rate cardWhat you charge, written down before someone asks0A
Usage rightsWhat a brand may do with your work, for how long, and where. Priced separately from making it0A
The tellThe signs a piece was machine-made — stacked adjectives, even stress, symmetry nobody speaks in2 §1, §3

4Keeping it honest

TermIn one lineExplained in
Intake / BV-01The brand voice and guardrails form. One per client. The source of what a brand will and won't say3
Experience fileYour own record of what you actually did with the product. Every claim traces back to it2 skills
Barred claimSomething a client is legally or contractually forbidden from saying. A hard constraint, not a style note3
Off-limits listWords and phrases a client bans. Matched literally. Also a de-genericiser3
GuardrailAny recorded rule that constrains output. Lives in a file, never only in a conversation3
ProvenanceThe honest record of how something was made: what generated it, when, from what, and what a human changed4
UnsupportedA claim with no source behind it. Not the same as wrong — you don't know it's wrong, you know it isn't sourced2 skills
DisclosureTelling the audience a piece is paid or gifted. Requirements change — confirm, never assume3

5Terms this guide deliberately avoids

Not because they're too hard. Because they're imprecise, and precision is the point.

Not used Used instead Why
"AI-powered" Name what it does Says nothing. Every tool is AI-powered now
"Prompt engineering" Writing a brief Makes an ordinary skill sound like a specialism
"Content" (as a mass noun) Scripts, videos, posts Vague enough to hide what's actually being made
"Automate" Hand off, or batch Implies nobody is watching. Somebody should be

Source: content/glossary.md