CueFrame — Brand demo recipe

Use the project and capability policy for scope, current state and metered work.

Kit truth over MCP (current limits): kit CONTENTS are not yet inspectable over MCP (get_profile lists names only), so $brand: tokens resolve blind — verify resolved fonts/colors with a preview_frame still, and when the kit conflicts with an explicit client spec, the spec wins (hardcode it and note the conflict). Bind kits by the SERVER id from get_profile (slug binding is unreliable — it can silently bind nothing); always confirm via the project response brandKitId.

A use-case recipe that runs end-to-end from inside the user's own project folder. You (Claude) already see their code and their running app — that's the unfair advantage. This skill turns that context into a brand-consistent product video: pull the brand from the repo, capture the app, and author a demo whose brand identity is enforced by the engine, not re-typed per clip.

Two things make this different from cueframe-product-video: