菜单
Specify lighting, atmosphere, and light transitions for Seedance 2.0 prompts using named light sources, core parameters, and atmosphere contracts. Use when the scene needs a specific mood, time of day, or lighting style, or when lighting is flat, inconsistent across shots, or clipping.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | seedance-lighting |
| description | Specify lighting, atmosphere, and light transitions for Seedance 2.0 prompts using named light sources, core parameters, and atmosphere contracts. Use when the scene needs a specific mood, time of day, or lighting style, or when lighting is flat, inconsistent across shots, or clipping. |
| license | MIT |
| user-invocable | true |
| user-invokable | true |
| tags | ["lighting","atmosphere","color-grade","openclaw","antigravity","gemini-cli","codex","cursor"] |
| metadata | {"version":"5.0.0","updated":"2026-03-03","openclaw":{"emoji":"💡","homepage":"https://github.com/Emily2040/seedance-2.0"},"parent":"seedance-20","antigravity":{"emoji":"💡","homepage":"https://github.com/Emily2040/seedance-2.0"},"gemini-cli":{"emoji":"💡","homepage":"https://github.com/Emily2040/seedance-2.0"},"author":"Emily (@iamemily2050)","repository":"https://github.com/Emily2040/seedance-2.0"} |
Lighting as narrative state. Measurable atmosphere contracts for Seedance 2.0.
❌ dramatic lighting
✅ single overhead practical as hard key, 5600K, deep shadow fill
window backlight casting long shadows toward camera
neon sign as key light, pink and blue, no fill
firelight flicker, warm amber, unstable
overcast diffused daylight, soft wrap shadows
single bare bulb swinging overhead
red emergency lamp as sole light source
candle practical, warm gold, deep shadow beyond 1m
streetlamp sodium key, cool fill from ground reflection
Key direction: camera-left / camera-right / above / below / behind (rim)
Contrast: low-key (deep shadows) / high-key (bright, minimal shadows)
Color temp: warm amber / cool blue / neutral white (Kelvin optional)
Shadow edge: hard-edged / soft wrap / no shadows
Every atmospheric effect must be describable in physical terms.
thin fog catching the backlight, visibility 5m
dust motes suspended in a sunbeam from camera-left
light rain visible against the key light, not heavy
breath misting in cold air at each exhale
heat shimmer rising from asphalt, subtle
smoke drifting from off-screen right, backlit
If fog becomes a blur: reduce density → increase backlight specificity → simplify background.
| Chinese | English | Usage |
|---|---|---|
| 主光 | Key light | Primary dominant source |
| 辅光 | Fill light | Softens key shadows |
| 轮廓光 | Rim light | Edge separation from background |
| 逆光 | Backlight / Contre-jour | Subject silhouetted or rimmed |
| 低调布光 | Low-key | Dark, high-contrast; drama |
| 高调布光 | High-key | Bright, low-contrast; commercial |
| 实景灯光 | Practical light | Visible source in frame |
| 丁达尔效应 | Tyndall rays / God rays | Light beams through particles |
Use timestamps for in-clip light changes:
0–3s: warm golden overhead light.
3–5s: lights flicker and die.
5–end: only red emergency lamp remains; cool rain spill from open door as rim.
Use this skill when designing, creating, or modifying API endpoints; defining contracts between services; evaluating protocol choices (REST, GraphQL, gRPC, WebSockets); versioning or deprecating an API; designing error responses or pagination; or reviewing an existing API for consistency, security, or ergonomics. Signal phrases: "design the API", "create an endpoint", "REST", "GraphQL", "gRPC", "API versioning", "backward compatible", "breaking change", "error response", "pagination", "rate limiting", "API contract", "OpenAPI", "Protobuf", "webhook", "idempotency", "deprecation", "endpoint structure". Also activate when API responses expose database column names, collection endpoints return unbounded results, or breaking changes are being introduced to active versions without a migration plan. Do NOT shape the API contract around implementation convenience — design for the consumer and the future.
Use this skill when designing system boundaries, data flows, component interfaces, or making structural technology decisions. Activated when the user is initializing a new project, service, or major feature; designing data flow between components; breaking apart a legacy system; defining folder structures or project organization; evaluating core technology or framework choices; or when the current system fails to scale. Examples: "how should I structure this?", "should this be a microservice?", "design the architecture for X", "what's the best way to organize this codebase?", "how should data flow between these components?". Do NOT use for pure implementation (use coding skill) or infrastructure provisioning (use devops-infra skill).
Use this skill when analyzing a brand's positioning, auditing an existing website's brand communication, identifying mismatches between brand intent and visual/copy execution, or defining the brand strategy for a new business from scratch. Activated when the user asks to "audit the brand", "diagnose the brand's positioning", "align copy and visuals to the brand", "define the brand perception", "what phase is this brand in", or "how does the brand extend to visuals and animations". Do NOT use for writing actual copy (use copywriting), editing copy (use copy-editing), or configuring animations without brand direction (use cinematic-motion).
Use this skill when designing or implementing highly animated, immersive, and cinematic web user interfaces. Activated when the user asks to build animations, integrate GSAP, use ScrollTrigger, build Three.js R3F models, implement video-scrubbing, image mask scaling, modulo-based infinite sliders, bento grid lighting, or premium interactive web layouts. Do NOT use for standard, non-animated web interfaces or pure backend APIs.
Use this skill when building cinematic, animated, or immersive web experiences. Covers scroll-driven storytelling (GSAP, ScrollTrigger, SplitText, video scrubbing, parallax, mask reveals), 3D product showcases (R3F, Zustand, studio lighting, model switching, video textures), layout composition (bento grids, masonry, power lines, overlapping typography), and register-aware creative direction. Activated when the user asks to "build a cinematic landing page", "add scroll animations", "create a 3D product viewer", "scrub video on scroll", "build a bento grid with scroll reveals", "animate text on scroll", "add parallax effects", "create a mask reveal", "build an infinite slider", "implement model switching", "add studio lighting to 3D scene", "map video textures on 3D screens", or any task producing premium animated web surfaces. Also activated for FFmpeg keyframe encoding, GSAP ScrollTrigger configuration, SplitText typography, gltfjsx model conversion, Zustand state for 3D, or scroll-bound timeline orchestratio
Use this skill when writing, modifying, or generating code of any kind. Activated when the user asks to build features, implement functions, create components, write endpoints, set up forms, wire things together, or produce any working implementation. Trigger phrases: "build this", "implement", "write the code for", "create a function that", "add this endpoint", "make it work", "update this code to", "wire this together". Do NOT use for: pure architectural decisions before implementation starts (use architecture skill), root-cause debugging of existing broken code (use debugging skill).