Turn a content creator's AI stack into a factory that sounds like THEM. One voice spine (CONTENT.md) governs every format — FB/blog posts, TikTok carousels, YouTube Shorts, covers — so the output stops smelling like AI and comes out consistent every run. Use when a creator (not a dev) wants to set up Claude Code / an AI agent for content production across channels, or fix output that reads generic, breaks Thai fonts, or looks different every gen. Triggers: "setup AI for content", "brandbook for AI", "AI writes generic", "content creator claude md", "carousel/shorts pipeline", "cover generator".
Keep an AI character's face and voice identical across every clip. Lock the identity ONCE (train a face, lock a voice), then reuse it — never re-generate the face. Use when a recurring AI character drifts between clips, looks like a different person each render, or the brand face is never consistent.
Split AI content into two layers — AI generates raw material (backgrounds, characters, clips), code assembles the deliverable (text, layout, render). Use when AI-generated carousels/cards come out inconsistent, Thai fonts break, or every re-gen is a gamble.
Pump the brakes — clarify before acting. Use when a request is exploratory, mid-decision, or underspecified and the AI is about to edit, commit, hand off, deploy, or run a workflow on a partial picture. Fires on /hold-up or "just talk", "don't action this", "let's think first" — or auto-fires when the AI catches discuss-mode cues right as it was about to take a non-trivial action.
Game-theory review loop for AI drafts: tit-for-tat trust tracking across review rounds. Review depth adapts to the author's track record of addressing feedback, so clean drafts earn lighter reviews and ignored flags trigger deep audits. Use for recurring content or code review loops.
Personal commitments tracker with escalating confrontation. Use when the user wants accountability on recurring commitments, training, habits, or deadlines they keep deferring. Reviews the track record and escalates tone based on the avoidance pattern, not the excuses.
Run multiple AI coding agents in parallel without collisions. Use when setting up parallel-agent workflows: defines file boundaries, a written contract between agents, and conflict rules so agents stop overwriting each other's work.
Give your AI long-term and short-term memory: keyword-searchable session history (FTS5 index) plus a hot cache of current project state loaded at session start. Use when AI should remember past sessions and know project state without re-explaining.