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.
Establish the host
Run slopcamera --help and use slopcamera doctor --json for the selected local tools. 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 currently installs 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 |
|---|---|
| Editable diagram, flowchart or visual explanation | Diagrams and visual communication |
| Custom diagram themes, fonts or icon packages | Customization |
| Raster artwork converted to SVG | Vectorization |
| Record, clean up, caption, frame or deliver video | Video projects |
| Generate images, clips, narration or transcripts | Gateway media |
| Budgeted short clips, reviewed takes and continuity | Directing video |
| Editable Three/Spark scene, saved world, named-part edits or shared camera | Directed scenes |
| Blender, rigs, bakes, CAD, shared native assets or production frames | Native studio |
| 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.