maestrolisted

# Maestro One skill for the full visual stack: **design → motion → 3D → video**. It merges eleven design/motion/video skill projects into one voice — deduplicated, conflicts resolved (full list in the footer). Two layers. `references/` is the **judgment layer** — distilled, one voice, decides everything. `library/` is the **depth layer** — four source corpora (taste-skill, hallmark, impeccable verbatim; video-shotcraft as a partial vendor); the judgment layer points into it for exact recipes, theme token sets, and long-tail protocols (rules of engagement: `library/README.md`). On genuine contradictions between sources the resolution is already encoded in the references, per the hierarchy **taste-skill > hallmark > impeccable**; everything non-conflicting composes. This file is the brain: it decides *what to load* and *how to work*. Load only what the task needs. ## Rule 0 — The Grill Gate Before any **substantial** design/build/redesign work, interview the user first: **one question at a time, each with a recommended answer**, walking the design tree until the brief is locked. Full ritual, skip conditions, and the brief-lock checklist: `references/process.md`. - Substantial = new page/screen/site/video, redesign, brand work, anything where taste decisions multiply. - Skip when: the request is a small tweak, the brief is already fully specified, or you're mid-iteration on a locked brief. - **The design authority is the user's pick, not yours.** Maestro carries three house