cinematography
Design cinematic image and video prompts for genmedia. Use this for shot language, camera movement, lighting, lens choices, color grade, film texture, scene blocking, and production-ready visual direction.
What this skill does
# Cinematography with genmedia
Use this skill when the user needs cinematic direction, not generic "make it
cinematic" prompting. Load references as needed:
- `references/shot-language.md`
- `references/lighting-lens-color.md`
- `references/examples.md`
Load `model-routing` alongside this skill for default endpoint choices.
Write concrete visual direction. Avoid empty prestige words and em dashes.
## Inputs to collect
Ask only for what affects the shot:
- Subject and action.
- Medium: still image, video, image-to-video, edit, storyboard frame.
- Genre and mood.
- Framing: close-up, medium, wide, overhead, POV, profile, locked-off.
- Camera motion for video: push-in, dolly, tracking, handheld, crane, drone.
- Lens feel: wide, normal, telephoto, macro, shallow or deep focus.
- Lighting: natural, practical, studio, noir, high key, low key, backlit.
- Output: aspect ratio, duration, first frame, last frame, download path.
- Preferred model, if the user wants a specific cinematography model or
quality/cost profile.
## Genmedia workflow
1. Start from routed endpoint IDs.
```bash
genmedia models --endpoint_id openai/gpt-image-2 --json
genmedia models --endpoint_id fal-ai/nano-banana-pro --json
genmedia models --endpoint_id bytedance/seedance-2.0/text-to-video --json
genmedia models --endpoint_id bytedance/seedance-2.0/image-to-video --json
genmedia models --endpoint_id xai/grok-imagine-video/text-to-video --json
```
Use text search only as fallback discovery for a missing camera-control
role:
```bash
genmedia models "cinematic video generation camera movement" --json
genmedia docs "video generation camera movement prompt" --json
```
2. Inspect schema and use only supported controls.
```bash
genmedia schema <endpoint_id> --json
genmedia pricing <endpoint_id> --json
```
3. Upload references when using image-to-video, first frame, last frame, style
reference, or character/product continuity.
```bash
genmedia upload ./frame.png --json
```
4. Run stills with direct download.
```bash
genmedia run <endpoint_id> \
--prompt "<cinematography prompt>" \
--download "./outputs/cinema/{request_id}_{index}.{ext}" \
--json
```
5. Run video async.
```bash
genmedia run <endpoint_id> \
--prompt "<shot prompt>" \
--image_url "<uploaded frame if supported>" \
--async \
--json
genmedia status <endpoint_id> <request_id> \
--download "./outputs/cinema/{request_id}_{index}.{ext}" \
--json
```
## Prompt build order
Use the SCLCAM structure:
1. Subject: who or what is in frame.
2. Context: location, time, weather, story moment.
3. Lens/framing: distance, angle, focal length feel, depth of field.
4. Camera motion: only for video or if motion blur is desired.
5. Atmosphere: haze, rain, practicals, reflections, texture.
6. Mood/color: palette, contrast, grade, exposure style.
7. Output controls: aspect ratio, duration, first-frame continuity.
Example structure:
```text
[subject] in [context], framed as [shot size and angle], [lens feel],
[lighting setup], [camera movement if video], [color grade], [texture],
[duration or aspect ratio], [continuity constraints]
```
## Model routing
- Premium realistic still: use `openai/gpt-image-2`.
- Premium stylized still: use `openai/gpt-image-2`, then
`fal-ai/nano-banana-pro`, then `fal-ai/nano-banana-2`.
- Fast draft still: use `fal-ai/flux-2/klein/9b`.
- Highest quality video: use `bytedance/seedance-2.0/text-to-video` or
`bytedance/seedance-2.0/image-to-video`.
- Motion from a strong frame: use `bytedance/seedance-2.0/image-to-video`.
- Fast or lower-cost video: use `xai/grok-imagine-video/text-to-video` or
`xai/grok-imagine-video/image-to-video`.
- Complex camera language: inspect Seedance 2.0 first, then Kling v3 when
multi-prompt or element controls matter.
- Story sequence: use the storytelling skill with this skill as shot-language
support.
- Character or product continuity: use the relevant domain skill first, then
apply cinematography as the variable block.
## Quality bar
Before returning, check:
- Camera movement is physically plausible for the scene.
- Lens, shot size, and camera angle do not contradict each other.
- Lighting direction is clear and consistent.
- Color grade supports the mood without flattening subject detail.
- Video prompt describes one shot unless the selected model supports multiple
prompts or shot lists.
- Downloaded files come from `downloaded_files[]`.
If a result looks generic, improve specificity in camera, blocking, light, and
environment before adding more adjectives.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.