maestro

Maestro runs a Grill Gate interview to lock the brief, deals art directions through a direction round, then builds using design foundations and motion modules. It finishes by rendering and critiquing the result against the locked brief before shipping.

Use CSS transitions for simple state changes, Motion (formerly Framer Motion) for React layout and gesture animation, GSAP for timeline choreography and scroll-driven stories, and WAAPI for one-off dependency-free tweens. Maestro's engine chooser maps each situation to the right tool.

Maestro routes product demos through its shotcraft module, which provides a mode gate, a 157-card shot vocabulary, and an eight-stage pipeline rendered through Remotion. The user first picks what kind of film it is before any engine is chosen.

Yes, it includes a distilled Three.js module covering scene fundamentals, shaders, postprocessing, and React Three Fiber. The upstream threejs-skills corpus is not vendored due to licensing, but the distillation stands alone.

Use generative models for photoreal humans, real-world locations, and material texture; use code rendering for anything that must be frame-exact, versionable, or re-renderable. Maestro gates model selection behind a user decision and offers bake-offs across engines.

Generic output comes from AI-slop patterns like default purple gradients, card grids, and eyebrow labels. Maestro's audit module catalogs these tells with mechanical grep checks and severity-ranked fixes, plus a brand-surface shipping gate before any build is declared done.