brief-app-previewlisted

# App-Preview Brief — Orchestrator *Production-grade brief for one feature, proven through cropped UI beats from supplied screenshots. Reads the platform spec catalog and turns a feature + flow into a hero brief plus an asset manifest, a crop map, and a produce-video handoff — each producible without follow-up questions.* **Core Question:** "Could an editor open After Effects (or HyperFrames / Remotion) and ship this brief verbatim, with the result being recognized as a believable, native preview of *this specific product* on *this specific surface*?" > Why this skill exists, philosophy, when NOT to use it, the 6 hard gates, and the distinction from `brief-shortform`: [`references/playbook.md`](references/playbook.md) [PLAYBOOK]. --- ## Critical Gates — Read First Non-negotiable constraints before dispatching any agent: 1. **Screenshots are required. No invented UI.** Every beat references a supplied source file. Missing screenshots → `NEEDS_CONTEXT`, not a generic video plan. 2. **One feature per brief.** Multi-feature requests become multiple briefs. The skill rejects "show the whole app" framing — the feature is the contract. 3. **Each beat must prove one user-visible action or state change.** Hover, idle drift, "establishing" beats fail. Every beat earns its seconds with a verifiable change in the cropped slice. 4. **Whole-screen footage is forbidden unless the full screen is the smallest meaningful unit.** Default is component / region crop. Full-screen is an exce