ohad6k

Use when a brief has to become a film. Turns a one line ask into a Claude Design prompt written in the animations-v3 engine's own language, plus the built piece.jsx and a contact sheet to look at before anyone renders. Covers reference roles, the kit, the…

Use when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history and native emulo:mine is not available. This is the cross-agent skills.sh bootstrap, not the native namespaced plugin.

Load the user's Emulo profile, mined from their local Claude Code, Codex, and OpenCode session logs, so you work like them instead of a cold start. Use before working on their task.

Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Emulo taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.

Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Emulo from real local AI coding-session history.

Use for execution, debugging, verification, planning, and shipping when the user's Emulo working profile should guide the task. Do not use for design/UI/UX work, marketing or social writing, or Emulo setup/mining.

Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Emulo writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.

Use when a user wants an AI-built local project pushed to GitHub and deployed live on Vercel with the least friction, while keeping git, secrets, provider setup, and live proof explicit.

Use VibeRaven when working on an AI-built app that must ship to real users; when the user asks to ship, deploy, go to production, connect auth, database, payments, RLS, env vars, webhooks, or monitoring; when production-only errors appear; or when the agent…

Use when an AI agent needs to stop guessing, find which version broke an app, compare releases, read git tags/diffs/changelogs, and connect the code change to provider context such as database, storage, deployment, and external runtime behavior before editing.

Use when VibeRaven architecture questions have been answered, a feature/fix has unclear boundaries, or an agent needs to turn product answers plus repo evidence into a workstream architecture plan before editing.

Use when an AI coding agent starts real app work, product feature design, provider work, migrations, auth, billing, storage, webhooks, deploys, or any task where unclear architecture could cause broad or unsafe changes.

Use when changing, reviewing, debugging, deploying, or documenting production-sensitive work involving providers, releases, migrations, auth, billing, webhooks, env vars, incidents, rollback notes, fragile customer paths, or architecture boundaries.

Use when the user explicitly asks to run, set up, update, re-mine, or deepen Ditto from real local AI coding-session history and native ditto:mine is not available. This is the cross-agent skills.sh bootstrap, not the native namespaced plugin.

Use for marketing, social, replies, product copy, launch copy, and writing in the user's voice when their Ditto writing profile should guide the task. Do not use for unrelated execution or UI/UX design alone.

Use only when the user explicitly asks to run, set up, update, re-mine, or deepen Ditto from real local AI coding-session history.

Use for UI, UX, visual hierarchy, frontend-design judgment, references, redesigns, and design critique when the user's Ditto taste should guide the task. Do not use for unrelated execution or marketing/social writing alone.

Use for execution, debugging, verification, planning, and shipping when the user's Ditto working profile should guide the task. Do not use for design/UI/UX work, marketing or social writing, or Ditto setup/mining.