Media Production

1. Establish the desired output, duration, aspect ratio and supplied reference material. A single image or speech request usually needs only its generation tool.
2. For hosted image generation, use media_production.image.generate with the desired prompt and output options; Core resolves tool settings, inheriting the active conversation provider by default. If selection_required is returned, ask the owner which available provider to use; never silently switch accounts. Use configure only when they request a saved preference. Inspect capabilities.defaults when setup needs diagnosis. Reserve generateWithModel for an explicitly owner-requested provider/model; never pick an older model from memory or bypass a default after an error.
3. Generate image assets with media_production.image. Use existing music_audio speech tools for narration and owner-supplied audio or video clips for other media assets.
4. For local production, use media_production.photocraft for layered raster edits, vectorcraft for vector artwork, hyperframes for social videos and motion graphics, filmcraft for timelines, and lightcraft for photo development. These tools run headlessly; PhotoCraft desktop control is optional. Discover commands and parameter schemas, inspect the source, and try the supported editing operation before replacing it with a custom shell pipeline. Use shell for unsupported work, not as a substitute for an untried editing tool. Validate one representative asset before applying a shared treatment to the whole set. Use returned object/media IDs, preserve originals and keep referenced media at absolute paths. Select persistent LightCraft libraries only when the owner requests library work.
5. For an authored social video or motion graphic, establish a short storyboard and consistent visual direction: one main idea per scene, readable typography at phone size, deliberate spacing, a focused palette, and useful visual assets. Match pacing to the brief; avoid walls of small text, repeated generic panels and gratuitous effects. Use hyperframes.create for a new project and the file tool to author its HTML, CSS and scene timelines. Look for suitable catalog components before inventing complex effects. Preserve supplied source by working in a copy. Tool guidance owns the composition and animation contract.
6. Batch independent grounding reads and author related files together. Use hyperframes.inspect to ground scene timing, then hyperframes.check with options.mode=lint to catch source errors cheaply. During repairs use mode=targeted with affected times and preview neighboring frames; verify text fit, safe margins and continuity. On the final source run the default full check and require scope=full, complete=true and checks.ok=true. Targeted/lint success is partial evidence. Independent checks and previews may run together once source is stable; never edit files while they are being inspected. Reuse current-run evidence and successful checks while relevant source/assets are unchanged. Render delivery quality once and review that exact video for motion, pacing and audio; use a separate draft only when useful for unresolved motion. Rerender only after changes or an observed defect. Passing checks or looking at a still frame alone cannot establish that a video is ready to share.
7. Preview edited artwork and representative timeline/composition positions; batch independent previews once the source is stable. Review against the brief and repair observed defects rather than generating speculative variants after requirements pass. Use existing FFmpeg and FFprobe tools for simple composition, conversion and validation. Inspect frames and audio/duration before claiming the result is verified. Wait for background renders to complete before delivery.
8. Generated and edited artifacts are attached automatically. Attach other composed/local files through file_system.file.attach so the owner receives a player or download. Do not expose provider URLs, credentials or base64 in chat.