What problem does it solve? Styling HyperFrames video compositions with Tailwind CSS v4's browser runtime introduces version-specific pitfalls: v3 directives break, dynamically generated class names get missed by the runtime scanner, and missing styles cause flashes during deterministic frame capture. This Skill provides the exact patterns and guardrails to write Tailwind v4 correctly inside HyperFrames compositions. ## Core Features & Use Cases - CSS-first v4 theming: Define design tokens with @theme and custom utilities with @utility inside text/tailwindcss style blocks instead of a tailwind.config.js. - Render-safe styling rules: Enforce static class names, explicit border colors, stable dimensions, and transform/opacity animations so frames render deterministically. - Validation workflow: Run npx hyperframes lint, validate, inspect, and a draft render proof to confirm no missing-style flashes on frame 0. - Use Case: After scaffolding a project with hyperframes init --tailwind, you need brand colors and a headline layout that renders identically in preview and final MP4 output. This Skill guides you to declare tokens in @theme, use complete static class tokens, and verify window.__tailwindReady resolves before capture. ## Quick Start Ask the assistant to add Tailwind v4 theme tokens and utility classes to my HyperFrames composition and validate the render output.