How this brain saves, syncs, and clones itself on GitHub — the required procedure for EVERY git push, pull, fetch, clone, commit, or gh command in a Parker Brain repo. Covers the credentials (the setup_parker_brain tool, never the user's own login, never gh), submodules, merge conflicts, and the rare self-hosted exception. Use whenever saving work to GitHub, syncing or updating the repo, cloning the brain, fixing a failed push or auth error, or when asked to save, back up, or share the brain.
The front door to building a brand's brain. Run this when standing up a new brand — all it needs is the Parker MCP connected. It welcomes the person, provisions the brand's own repo through the setup_parker_brain tool (Parker MCP), clones that repo and works inside it, connects and tests the data, asks the short brand intake (the things Parker genuinely can't observe), runs the full build in dependency order, saves it to GitHub, and hands off to get-started. Follows prompts/onboarding-runner.md as the detailed method. Use when someone says set up a brand, build the brain, onboard a new brand, or get started building. Also the right entry when the brand's brain already exists — it detects a built brain and retrieves it, handing off to get-started instead of rebuilding.
The weekly check that keeps this brain current with the parker-brain standard — without overriding anything the team chose. Compares the pinned parker-system/ release against the newest factory tag and offers the bump as one short question; on a yes the migrations run and a script re-syncs the copied skills deterministically. What the team declines stays declined; what they modified stays theirs. Use weekly as a scheduled routine, or when asked to update the brain, check for updates, sync with the standard, or "what's new in Parker".
One-time setup for a fresh brand brain instance. Registers the standing routines (refresh-context, dream, harvest+evaluate ideas, research-loops, update-brain, self-improve) as scheduled cloud agents so they run on cadence without being asked. The job definitions already travel with this repo; this skill arms the schedules, which are per-account and can't be committed. Run once after cloning the brain into a new Claude Code cloud instance, or when asked to set up / register / schedule the routines.
Generate AI ad assets — Veo 3 video prompts and AI image static prompts — with brand context, compliance, and forensic direction. The output is prompt text the user pastes into the AI tool, not the final asset.
Write headlines for ads — static, video text overlays, paid social, landing page hero. Picks the right structural pattern for the brand type (lifestyle vs problem/solution), the awareness stage, and the customer language available.
Write hooks for a specific ad — the first three seconds that earn the click and the watch. Uses the proven hook formats from the canonical taxonomy, picks the right one for the brand and audience, and produces hooks built around a specific ICP and emotion.
The full iteration flow in one skill — choose which ads to iterate on, then make the iterations. If the user names a specific ad, go straight to making iterations; if they ask account-level (which ads should we iterate on, what to iterate this month), select the ads first, then make iterations on each.