cinematic-ui

Guides film-inspired art direction for cinematic websites using composition, typography, and lighting references.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill cinematic-ui-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cinematic-ui
Source: https://github.com/oxie/prime-agent-skills/tree/main/cinematic-ui
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill cinematic-ui-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Translating film and cinematic aesthetics into coherent web design is difficult without a structured method; this Skill provides a disciplined workflow for framing, typography, light, material, and pacing decisions while preserving the project's existing design system, accessibility requirements, and content contracts. ## Core Features & Use Cases - Evidence-grounded art direction: Decompose inspected film frames, screenshots, or reference websites into observed, reported, or proposed-analogy confidence levels before translating them into web layout and token decisions. - Craft reference library: Selective references cover composition patterns, cinematic typography, light and material treatments, narrative pacing, optional bounded motion, and production checks for semantics, contrast, keyboard, and failure states. - Reusable static CSS/SVG recipes: Optional quiet-surface, material-surface, nested-surface, and inline-media CSS assets with standalone fixtures and native Node test files, requiring no runtime dependencies or providers. - Use Case: A designer building a cultural venue's editorial landing page uses the Skill to ground a visual thesis in inspected evidence, choose a weighted-split composition and title-card typography, build a readable static page first, then verify narrow, reduced-motion, and forced-colors behavior before handoff. ## Quick Start Ask the agent to apply cinematic art direction to a specific page or component, for example: design a film-inspired editorial landing page for an architecture portfolio with a quiet daylight treatment.

Frequently Asked Questions about cinematic-ui

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a cinematic website without copying film imagery?▼

Ground the direction in inspected evidence, translate observed framing or light into a web purpose, and select one visual thesis with restrained supporting choices. Build a readable static page first using semantic HTML and existing project tokens, adding only authorized enhancements.

What references does a film-to-web design workflow need?▼

Useful references cover evidence gathering with confidence levels, composition patterns, cinematic typography roles, light and material treatments, narrative pacing with bounded motion, and production checks. Load only the one or two references relevant to the current task rather than a full catalogue.

Does cinematic web design require animation or JavaScript libraries?▼

No. A strong static page is a valid result, and motion is optional, finite, and decorative-only. The Skill mandates no library, CDN, remote font, or runtime dependency; native CSS and HTML are preferred.

Can I reuse the quiet-surfaces and material-surfaces CSS in my project?▼

Yes, copy only the library CSS files such as quiet-surfaces.css or surfaces.css through your normal pipeline, mapping their custom properties to existing host tokens. Demo CSS and scripts are fixture-only and should not ship to production.

When should I not use cinematic art direction?▼

Avoid it for ordinary noncinematic UI edits, generic app or backend work, technical diagrams, film or video production itself, and automatic whole-site redesigns. The existing brief, design system, and accessibility requirements always take priority over cinematic references.