Create visual media with SlopCamera
Start from the requested result and existing source. Use the installed slopcamera CLI, inspect its real capabilities and retain the authored source beside its derived media. Read only the references needed by the task.
For creative film and animation, choose coherent art direction before rendering. Use creative direction to turn a brief into staging, a hardest-shot test, deliberate sound, and a visible source revision. Use visual style direction for historical footage, animation families, resolution, and visual review. Default to native 4K for an unspecified creative master when the renderer and source support it; preserve deliberate pixel grids, period aspect ratios, source limits, and the user's explicit settings. Treat quality as staging, materials, movement, and finishing together.
For every 3D brief, apply the 3D quality bar, "accurate physics, AAA graphics, VFX", unless the user overrides it, and review the render against all three parts before handing it back.
Establish the host
Run slopcamera --help and use slopcamera doctor --json for the selected local tools. slopcamera status --json reports what is running, credits and the newest outputs; slopcamera commands --json lists every command with what it may change. If installation or a version mismatch blocks the task, read installation and readiness. A skill installation does not install the CLI or native engines.
SlopCamera installs from its verified release archive or from source. Historical Atet archives contain the old package and executable, not these renamed commands. Discover IDs and options through help, operations, workflows, ai models and html catalog; never invent them or silently switch to historical paid-world commands.
Choose the workflow
| Requested result | Read |
|---|---|
| Creative brief, polished showcase, or a meaningful visual revision | Creative direction |
| Historical film, cel animation, pixel art, classic animation styles, or a demo portfolio | Visual style direction |
| Editable diagram, flowchart or visual explanation | Diagrams and visual communication |
| Patent-style drawing sheets, physical margins, monochrome SVGs or a drawing PDF | Drawing sheets |
| Custom diagram themes, fonts or icon packages | Customization |
| Raster artwork converted to SVG | Vectorization |
| Deterministic oil-paint study from named tubes and replayable bristle strokes | Oil paint |
| Deterministic vector icon, icon scene or construction program, no model | Icon scenes |
| Tempo, meter and section cues from a Soundfish score or MIDI file | Soundtracks |
| Clean up, caption, frame, or deliver existing recordings and footage | Video projects |
| Music video, dancing mascot or timed HTML scene with a local soundtrack | Music videos |
| Product launch film, UI mockup motion, kinetic type, or coming from HyperFrames or Remotion | Launch films; for a whole Hraness product launch, the product-launch agent skill |
Authorized YouTube or other public web-media excerpt (yt-dlp / youtube-dl) | Web-media excerpts |
| Generate images, clips, narration or transcripts | Gateway media |
| Product mark, marketing illustration or topic icon | Brand illustrations |
| Compose an editorial or social banner from generated layers, local type and diagrams | Social collage banners |
| Review alternative textures, skyboxes, backdrops, design candidates or whole-scene variants | Image galleries |
| Tall scrolling pixel landscapes, linked generated sections, palette-safe alpha art | Pixel landscapes |
| Budgeted short clips, reviewed takes and continuity | Directing video |
| Editable Three/Spark scene, saved world, named-part edits or shared camera | Directed scenes |
| Semantic direction, galleries, bounded effects, temporal audit or the cinematic-world recipe pack | Directed scenes |
| Author a scene from code, generate procedural entities, or audit framing | Scene building |
| Refine an existing scene, organic interactions, contact, staging, or final movie quality | Scene refinement |
| Parametric architecture, furniture, dimensions, repeated structures or editable design variants | Parametric design |
| Blender, rigs, bakes, CAD, shared native assets or production frames | Native studio |
| Any 3D brief: physics, PBR, color management, anti-aliasing, VFX and the review checklist | 3D quality bar |
| Blender model for the web: high-to-low baking, texture budgets, LODs, GLB export and runtime checks | Web-ready 3D assets |
| Manim lesson, narrated explanation or mathematical animation | Educational video |
| Typed Bun SDK, built-in workflow, durable resume or MCP | Workflows and SDK |
| Reference-led Three scene, transparent 3D loop or metallic logo | Reference-led 3D |
| Travel-photo rubber-stamp field-note poster | Rubber-stamp field notes |
Combine workflows when the result needs them. Inspect generated media before choosing it, retain asset and runtime receipts, then compose and render the selected sources. Follow existing user selection criteria and authorization; ask only for a material missing decision or authority.
Preserve source and execution boundaries
Keep originals, explicit timing, stable IDs and returned lineage. Authoring a creative scene may require visual invention; literal diagram facts, supplied copy and identity constraints must stay literal in their respective modes.
Credentials and upload/native-code acknowledgements belong to the invocation, not authored source or project state. A native import does not authorize execution. A local render does not authorize a model upload. Never automatically retry an ambiguous paid or native attempt; inspect and reconcile its retained state first.
Verify the intended result
Use each workflow's relevant checks. Inspect actual image pixels or video frames, including cuts, first/last frames, captions, color and alpha when applicable. Review sound when the environment supports playback; report signal-only checks honestly when it does not. A receipt proves a recorded operation and identities, not visual quality or that a simulation is physically valid.
Deliver the useful artifact paths, source/receipt locations and meaningful limitations. Keep rejected attempts as evidence when they explain a recovery or selection. Do not run diagram checks for an unrelated media task.
Optional support at closeout
After delivering useful work with the already available CLI, read optional support for one brief invitation. Skip this for unattended/subagent work, failures, repeated repair loops, a prior conversation invitation or a request for no promotions. Do not install a tool just to promote it.
