Creative Studio

Orchestrate still, motion, and vector creative pipelines.

Skill metadata

Source	Bundled (installed by default)
Path	skills/creative/creative-studio
Version	1.0.0
Author	VibeOS
License	MIT
Platforms	linux, macos, windows
Tags	creative, image, video, vector, studio
Related skills	figma-edit, video-nle, raster-edit, excalidraw, p5js, manim-video, ascii-video, comfyui, choose-interaction-surface, challenge-gate, desktop-operate

Reference: full SKILL.md

info

The following is the complete skill definition that VibeOS loads when this skill is triggered. This is what the agent sees as instructions when the skill is active.

Creative Studio Skill

Run a predictable Create pipeline: brief → generate/edit → QA → export → manifest. The manifest records measured file facts separately from authored provenance, responsive relationships, and project budgets. Prefer native tools and MCP over pixel clicks. Use computer_use only for editor playbooks when API/MCP cannot finish the job.

This skill does not replace specialized creative skills — it routes to them and keeps artifacts consistent.

When to Use

• User wants a still image, short clip, SVG/vector, or editor-assisted polish.
• Need a single brief format and export checklist across providers.
• Batch creative work that should land in a workspace folder.

Do not use for deep web research (use professional-research / challenge-gate) or OS admin tasks.

Prerequisites

• Image/video providers configured as needed (image_generate, video_generate).
• For editor playbooks: desktop computer_use permissions on the target OS.
• Optional MCP (Figma, etc.) when installed — never invent vendor APIs.

How to Run

1. Write creative-brief.md from templates/creative-brief.md.
2. Pick mode: still | motion | vector | editor.
3. Generate or draft with the matching tool/skill.
4. QA with vision_analyze / file checks.
5. Export under the brief’s export_dir with stable names.
6. Build asset-manifest.json; review budgets and missing provenance.
7. Destructive editor actions → human approve.

Quick Reference

Mode	Preferred surface	Fallback
still	image_generate	editor playbook
motion	video_generate + video_analyze	NLE playbook
vector	SVG scripts / excalidraw / Inkscape	Illustrator playbook
editor	figma-edit MCP / video-nle / raster-edit	desktop-operate + computer_use

Asset artifact	Role
design/asset-metadata.json	Human-authored role, provenance, variants, fallback
design/asset-policy.json	Project-specific size and completeness gates
asset-manifest.json	Deterministic measured facts + policy results

Procedure

1. Brief

Copy templates/creative-brief.md. Fill goal, audience, constraints, aspect, export formats. Keep one brief per deliverable set.

2. Generate

• still: image_generate → optional edit → vision QA.
• motion: video_generate → video_analyze → iterate brief if needed.
• vector: produce SVG (or Excalidraw JSON) via skill/scripts; run scripts/lint_svg.py on every .svg export.
• editor: open project folder; Figma → figma-edit, NLE → video-nle, Photoshop/Affinity → raster-edit; else OS playbook / desktop-operate. Then scripts/check_exports.py --dir exports/.

3. QA checklist

• Matches brief constraints (size, aspect, text accuracy).
• No placeholder/lorem left in final.
• Files exist at promised paths.
• Purchases / account creation / overwrites → human gate.

4. Asset manifest and budgets

Copy templates/asset-metadata.json and templates/asset-policy.json into the project design/ directory. Metadata entries are keyed by project-relative asset path:

{
  "assets": {
    "public/hero.webp": {
      "role": "hero",
      "provenance": {"source": "generated", "license": "owned", "seed": 42},
      "responsive_variants": ["public/hero-768.avif"],
      "fallback": "public/hero-poster.jpg"
    }
  }
}

Then run:

python3 skills/creative/creative-studio/scripts/asset_manifest.py . \
  --source public --source src/assets \
  --format json --output asset-manifest.json

Use --fail-on-violation only after the project policy is reviewed. The tool never rewrites or deletes an asset. Confirm route/network usage before changing an over-budget source file.

4. Bot walls while fetching references

If a reference site challenges: load challenge-gate (human handoff). Do not thrash stealth scrapers for moodboards.

Pitfalls

• Do not add new core tools for one-off creative vendors — MCP / skill / CLI.
• GUI automation is brittle; prefer regenerate SVG/image over endless clicks.
• Respect site ToS when gathering reference material.

Verification

• creative-brief.md present and filled.
• At least one export file exists and opens.
• SVG exports pass scripts/lint_svg.py (viewBox, no lorem).
• scripts/check_exports.py --dir exports/ is green.
• asset-manifest.json is current; required provenance, responsive variants, fallbacks, and project budgets pass.
• QA notes recorded (pass/fail + gaps).

CLI: vibeos creative run|doctor|preset creative-studio. Eval: python scripts/eval_creative.py --workspace <dir>. Offline smoke: scripts/smoke-creative-studio.sh.