← ClaudeAtlas

marketing-studiolisted

Use when generating any brand video, animation, image, or audio asset (logo reveal, social clip, product demo, launch video, OG image, README GIF, music, voiceover) for any product/repo, or when working inside C:\Projects\animations. Required background for /logo-reveal, /social-clip, /product-demo, /launch-video, /og-assets, /audio-track.
ucsandman/claude-skills · ★ 0 · AI & Automation · score 72
Install: claude install-skill ucsandman/claude-skills
# Marketing Studio All brand video/animation/image assets render in ONE engine repo: `C:\Projects\animations` (Remotion + Blender + Playwright + ComfyUI feeders). Never generate animation code inside a product repo — work in the engine, then copy the finished artifact into the calling repo. **REQUIRED READING before any asset work:** `C:\Projects\animations\docs\PLAYBOOK.md` — engine map, brand onboarding steps, and the verified gotchas (Blender 5.1.2 API traps, camera math, seamless-loop rules, capture-feeder lessons). Those were expensive to discover; do not re-derive or second-guess them. ## Workflow shape (every asset skill follows this) 0. Shared-repo guard: `git -C C:\Projects\animations status --short`. If the tree has uncommitted modifications you did not make, ANOTHER session is likely mid-flight in the engine repo — tell the user what you found and ask whether to wait or proceed (scope-lock if proceeding in parallel). Never build on top of a stranger's uncommitted edits silently. 1. `cd C:\Projects\animations && python launch.py --check` — verify the toolchain. 2. Brand check: does `brands/<id>.json` exist for the product? If not, run the PLAYBOOK's "Onboarding a new brand" section first (tokens from the product repo's DESIGN.md/tailwind/CSS vars; mark component; registries). Ask the user only for values you cannot derive. 3. Execute the asset recipe (per-skill). 4. Rendered proof: inspect 2-4 stills (Read tool) at key frames BEFORE any full