메뉴
Build, validate, and compress Seedance 2.0 prompts to a hard 2000-character limit using the Five-Layer Stack, @Tag delegation, and the new Compression Engine. Use when constructing or debugging any T2V, I2V, V2V, or R2V prompt for the short-form workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | seedance-prompt-short |
| description | Build, validate, and compress Seedance 2.0 prompts to a hard 2000-character limit using the Five-Layer Stack, @Tag delegation, and the new Compression Engine. Use when constructing or debugging any T2V, I2V, V2V, or R2V prompt for the short-form workflow. |
| license | MIT |
| user-invocable | true |
| user-invokable | true |
| tags | ["prompt","compression","t2v","i2v","v2v","r2v","character-limit","openclaw","antigravity","gemini-cli"] |
| metadata | {"version":"5.0.0","updated":"2026-03-03","openclaw":{"emoji":"⚡️","homepage":"https://github.com/Emily2040/seedance-2.0"},"parent":"seedance-20","author":"Emily (@iamemily2050)","repository":"https://github.com/Emily2040/seedance-2.0"} |
This skill helps construct and compress prompts for Seedance 2.0, with a recommended target of 30-100 words.
| Layer | Budget (chars) | Purpose |
|---|---|---|
| 1. Core Intent | ~20-40 words | Subject + Action. The emotional and narrative heart. |
| 2. Visuals | ~20-30 words | Camera + Lighting + Style. The cinematic eye. |
| 3. Audio | ~10-20 words | Music + SFX + Ambience. The soundscape. |
| 4. Technical | ~10-20 words | @Tags + Constraints + Physics. The rules. |
| Total | ~30-100 words | Recommended Target |
A woman's face, catching the last light not A beautiful, stunning shot.His shoulders slump not He is sad.Dolly shot, camera-left not The camera moves smoothly.Gourmet hamburger ad, macro shot not a long description of a hamburger.For a guided workflow that builds a prompt, use [skill:seedance-interview].
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).