---
name: viralinn-studio-production
description: Build and run an approved creative plan in a Viralinn MCP studio, preserving brand and avatar references, tracking generation jobs, and checking delivered media.
---

# Viralinn studio production

Use this pack to turn a supplied or approved shot plan into a working Viralinn studio and, when requested, finished media. Follow the user's authorized scope: assembling a studio and submitting paid generations are distinct actions.

## Inspect the production context

Discover current MCP tools and schemas rather than copying stale tool arguments. Inspect the intended workspace, existing studio, selected avatar and product references. Resolve real IDs through read tools; never use a display label as an ID. Open or reuse the intended studio session before calling tools that require a session ID.

Inspect the current model catalog and balances before choosing a model or starting paid work. Check the capabilities the shot requires: aspect ratio, duration, audio, and supported identity/first-frame/last-frame references. Keep generation credits, Composer steps, and MCP production actions separate; an unlimited action allowance does not make media generation free.

## Assemble the studio

Map each shot label to its nodes, reference roles, model, prompt, duration, aspect ratio, and audio intent. Reuse approved assets when suitable. For existing studios, inspect node state and connections before changing them so repeat requests do not duplicate the whole graph.

Preserve the user's chosen avatar and approved version where applicable. Keep product identity, appearance and packaging grounded in supplied references. An identity reference, composition reference, first frame and last frame serve different purposes; assign each to its supported role rather than passing every image interchangeably.

Keep on-screen text separate from scene descriptions when the workflow supports it. Do not add captions, music, graphic overlays or face replacement when the user excluded them. Organize and connect the nodes so the production order and output for every shot are visible.

## Run and track

Submit only the requested work within the authorized budget. Record the resulting job and node IDs immediately. If a request times out after submission, inspect existing job/node state before retrying; uncertain submission is not evidence that nothing was charged. Poll using the server's suggested delay and reuse completed outputs.

A failed job needs a specific cause or supported correction before resubmission. Stop paid retries when the allowed budget is exhausted or the previous submission remains unresolved. Continue independent assembly or reporting where useful.

## Verify the handoff

Retrieve completed media through the available status, studio-media or download tools. Inspect actual output where the client supports it: identity consistency, product fidelity, framing, action, duration, aspect ratio, and audio. Distinguish a completed provider job from media you have personally examined.

Return playable/downloadable output links and the studio link, with shot labels and unresolved issues. If the client cannot examine media, say which outputs are ready but uninspected. Publishing, scheduling and client delivery require the user's corresponding authorization; rendering alone does not imply them.