Convene the 27-senior virtual agency for a new project: parse requirements, debate and vote the stack (Supabase/Firebase/Node, Riverpod/Bloc, spatial 3D core, mesh renderer, offline layer…), synthesize a design language, generate the full scaffold (Flutter app, backend, RLS migrations, Dockerfiles, CI, Terms/Privacy docs), cross-examine every artifact, compile Figma-ready wireframes, run the compliance audit, and start the asset watcher. Everything lands under projects// with the complete meeting transcript.

The 27 senior personas that debate every project: names, titles, focus areas, and operating principles.

Emit the spatial canvas code (scroll-driven Z-axis camera, Matrix4 perspective parallax layers, CustomPainter starfield, snap-point rooms, reduced-motion fallback; optional flutter_scene/flutter_cube mesh stage and Rive HUD) into an existing project or a fresh module directory.

Analyze art in the project's asset drop zones (format, dimensions, dominant palette) and re-derive the design tokens — colors, brightness, padding grid, radii — so the app natively adapts. Writes docs/ADAPTATION_REPORT.md with every rule applied and WCAG contrast verification.

Start/stop the watcher on app/assets/incoming — any image dropped there re-runs verification and theme adaptation automatically. Call without project_dir to list active watchers.

Detect the OmniCinema media generator on this machine (well-known SSD paths + overrides), check its loopback IPC health, and report the CASE A/B/C state with next steps.

CASE C: "Would you like devuniverse-mcp to automatically clone, install dependencies, and link OmniCinema-MCP for 100% free cinematic assets? [y/N]" — with confirm: true this clones the pinned OMNICINEMA_REPO_URL, runs npm install + build, starts the IPC service detached (logged to data/logs/), and syncs the bearer token from data/ipc-token.txt. Refuses unpinned repository URLs.

CASE A: request an image/texture/audio/video from the linked OmniCinema loopback API, save it into app/assets/generated/ with a provenance manifest entry, and re-adapt the theme to the new material.

Compile the roundtable's screen plan into design artifacts: SVG wireframes (drag into Figma), a generated Figma development plugin that rebuilds the frames natively with auto-layout + tokens, and an optional REST handoff comment on your Figma file (FIGMA_TOKEN). The REST API cannot create designs — the plugin is the editable-draft path, and that constraint is documented in the output.

Reverse-engineer the patterns of a reference the user provides: palette, typography, framework/interaction fingerprint (three.js, GSAP ScrollTrigger, scroll-snap, WebGL…), structure, and an equivalent-rebuild plan mapped onto devuniverse modules. Videos get ffmpeg keyframe + palette analysis when ffmpeg is present. Pattern-level only — protected artwork and trade dress are never copied. apply_theme=true blends the extracted palette into the project tokens.

Crawl GitHub and Hugging Face for recently published MCP servers / development packages and log them to data/dev-review-queue.json as pending_human_review (with risk flags: missing license, low adoption, suspicious install patterns). Nothing is ever auto-installed; human decisions survive re-scans.

The legal bench drafts a complete Terms of Service, GDPR/CCPA Privacy Policy (lawful bases, retention, data-subject rights), and store compliance checklist from the project's actual data categories. Documents carry a review-by-counsel banner — structured drafts, not legal advice.

Static scan of a project for liabilities: committed credentials, plaintext endpoints, undisclosed tracker SDKs, sensitive permissions, missing policy documents. Writes compliance/AUDIT_REPORT.md with severity-ranked findings and remediations.