ai-personalisted

Create, replace or adjust a consistent AI-generated persona (the recurring face of a UGC account, a carousel series or a video ad) and verify it with a test shot through the real pipeline prompt. Covers the dense English face description, the reference portrait sent as an image on every face shot, the "plain but pretty, girl or boy next door, not a model" calibration, adults only, generating two portraits for the user to pick, and the known pitfalls (a phone drawn in the frame, the too-beautiful AI face, the too-tired face, identity drift). Use it whenever the user wants "a girl" or "a guy" for an account, a reference face, a portrait, asks to make someone "prettier", "plainer", "blonde", "less tired", starts a new selfie-style account, wants the same person across several images, or complains that a generated person "looks AI", even if they never say "persona" or "face reference".
josephbedminster/indie-marketing-skills · ★ 1 · AI & Automation · score 74

Install: claude install-skill josephbedminster/indie-marketing-skills

# AI persona: one face, kept consistent A persona is a fictional adult who appears in many images: the hook selfie of a carousel, the struggling student of a video ad, the parent of a parenting account. Two things keep them the same person from one image to the next, and nothing else does: 1. **A face text**: one dense English sentence, sent in every prompt that shows the face. 2. **A reference portrait**: an image file sent to the image model **as an image input** on every shot where the face is visible. Text alone drifts after two or three images. A reference alone drifts on hair color and age. Use both, and keep them consistent with each other. ## Before you start Read `.claude/ugc-config.md` in the user's project: where the image pipeline lives, how scripts run, which accounts show a face, the image model, the brand invariants, where decisions are logged. If `.claude/posthog-funnel-map.md` exists, read its **Business profile** and **Project conventions** too (audience, language, report style). No `ugc-config.md`? Ask at most five questions in one message, each with a default guessed from the repo: where the image pipeline is and how it runs; the image model and the env var holding the API key; which accounts or series show a face and which never do (first-person POV, hands only); the brand rules the founder already set; where to log decisions. Then write the file from `references/config-template.md` (in this skill's folder) and show it. ## Hard rules - **Adu