The clip lives or dies on the action loop. Write every link from run-up to landing in order, name the physics you want by part, and spend the negative list on flying, hovering and teleporting.
This Skill carries one prompt structure distilled from 12 human-verified Seedance cases on goodcase.ai. It is a sibling of seedance-prompt-library (all templates in one Skill); install this one when you only want this kind of clip. Do not invent structure from general video-generation knowledge: follow the structure below and ground the draft in one anchor case from references/cases.md.
Use when
- Snowboarding, mountain biking, parkour, street basketball, water game shows and phone-shot stunt clips where a body has to obey gravity and contact.
- Chinese: Snowboarding, mountain biking, parkour, street basketball, water obstacle courses, and stunt clips in a phone-shot style, where the body must obey gravity and contact.
Workflow
- Collect inputs. Ask only for what is missing: subject or product, setting, duration, aspect ratio, whether reference images / audio exist, and which language the final prompt should be in.
- Pick one anchor case. Read
references/cases.md, choose the case closest to the request, and name it in the reply. One anchor, never an average of several. - Fill the structure block by block. Every block below must be present in the final prompt; an empty block is where prompts go vague.
- Header parameters: duration, aspect ratio, reference image, on-location audio, and the overall look stated as phone-shot action footage
- Global continuity: the site, the apparatus, the main subject and the bystanders, each in its own short block
- Camera continuity: who holds the camera and how it travels, with cuts and viewpoint jumps ruled out
- The action loop: every link from run-up to landing named once, in order, as one chain
- Beats by timecode, each carrying the body detail plus the camera move that goes with it
- Constraint block: the environment stays put, the force has a named source, and the move must not read as flight
- Negative list: look drift, camera teleports, broken physics, injury, subtitles and watermarks
- Apply the guidance and check the pitfalls (next two sections) before returning anything.
- Return the finished prompt as one copy-pasteable block, the anchor case link, and a three-line checklist of what to verify in the generated video.
Guidance (from the cases)
- Write the stunt as one ordered chain of contact and reaction. The rooftop bungee case runs a STUNT ENGINE line from
屋顶助跑 → 飞越护墙 → 高空下落 → 命中圆形弹性面中心on to the landing, and demands the four phases接触—下陷—压缩—回弹all be visible. - Name the physics part by part. The mountain-bike final asks for
suspension compression, braking, cornering, jump physics, dirt displacement, so the bike behaves instead of gliding. - Lock rider, gear, trail and light in a single sentence up front. The valley ride case opens with
Same female rider, bike, clothing, trail, and daylight throughoutand never describes them again. - Make every reaction start from contact. The water game-show case writes
反应必须由接触触发and blocks her from standing up or leaning back before the moving wall actually reaches her. - Spend the negative list on cheats rather than on taste. The mountain-bike final bans
no teleportation, no floating bikes, no unrealistic physics; the bungee case adds flying, hovering, hidden cables and anti-gravity.
Pitfalls
- Writing only the outcome and skipping the contact. The body rebounds or launches before it touches anything; give contact, compression and release their own time slots.
- Stacking extra angles inside a one-take. Write
不切镜、不瞬移、不更换视角and describe the camera as the operator moving on foot with the athlete. - Landing light and upright. Ask for knees and hips folding deep to absorb the impact, and put
落地无重量,站直落地in the negative list. - Over-specifying spin direction and rotation count. Limbs twist and the body clips; the bungee case writes
不要锁定具体翻转方向and asks for continuous natural rotation instead.
Language
Reply in the user's language. The prompt itself can stay in English when that is what the user's Seedance workflow expects; ask if unclear. The Chinese version of this structure follows.
Chinese: Sports and extreme stunts
This type of footage rests entirely on the action loop. From the run-up to the landing, write out each stage in order, name exactly which physical elements are needed, and use the negative list specifically to eliminate flying, hovering, and teleporting.
Structure:
- Opening parameters: duration, aspect ratio, reference image, on-site sound, with the overall texture written as extreme sports phone-shot footage
- Global continuity: venue, equipment, protagonist, bystanders, each taking a short section
- Camera continuity: who is holding the camera, how the lens moves, explicitly stating no cuts and no angle changes
- Action loop: from the run-up to the landing, name each stage once in order, linking them into a chain
- Cut shots by timecode, write body details for each shot, then pair it with the camera action for that shot
- Constraint section: environmental position does not drift, make clear where the force comes from, and it must not be portrayed as flying
- Negative list: shape drift, camera teleporting, physics failure, injury and bleeding, subtitles and watermarks
Key points:
- Write the stunt as an ordered chain of contact and reaction. The STUNT ENGINE section of the rooftop bungee one goes from
屋顶助跑 → 飞越护墙 → 高空下落 → 命中圆形弹性面中心all the way to the landing, and also requires接触—下陷—压缩—回弹all four stages to be visible. - Name the physics item by item. The mountain bike final one calls for
suspension compression, braking, cornering, jump physics, dirt displacement, so the bike looks like a bike, rather than sliding along the ground. - The person, bike, track, and light are locked down in the opening sentence. The valley cycling one begins with
Same female rider, bike, clothing, trail, and daylight throughout, and never repeats the description afterward. - All reactions begin with contact. The water obstacle course one says
反应必须由接触触发, and before the wall panel is actually touched, she is not allowed to stand up early or lean back early. - The negative list is for cheating actions, not for aesthetics. The mountain bike final one bans
no teleportation, no floating bikes, no unrealistic physics, and the bungee one also adds flying, hovering, invisible ropes, and anti-gravity.
Common pitfalls:
- Only writing the result and skipping contact. The body will bounce up or fly out before touching anything; give contact, compression, and rebound each a time segment.
- Cramming extra camera positions into a single continuous shot. Write
不切镜、不瞬移、不更换视角, and describe the camera action as the photographer running after the athlete. - The landing is too light and floaty, standing straight up and then stopping. Require deep knee and hip flexion to sink down and absorb the impact, then put
落地无重量,站直落地into the negative list. - The flip direction and number of rotations are written too rigidly. The limbs will twist and clip through the model; the bungee one says
不要锁定具体翻转方向, and what is wanted is natural, continuous rotation.
Copy-ready lead-in / 可复制引导语
For users who would rather paste into a chat model than run this Skill, hand them this line above the structure:
I want an extreme-sports clip. [The sport is skateboarding, in a concrete bowl under a city overpass at dusk.] [I am sending my own photo as the rider; keep the face and outfit locked throughout.] Using the prompt template below, rewrite it into one ready-to-use Seedance video prompt for me:
I want to make an extreme sports short film, [the project is skateboarding, the venue is a concrete bowl under an urban elevated bridge at dusk], [I provide my own photo as the protagonist, with face and styling locked throughout]. Please use the prompt template below to help me rewrite it into a Seedance video prompt that can be used directly:
Notes
references/cases.mdis generated fromdata/in LearnPrompt/awesome-seedance and refreshed daily; do not hand-edit an installed copy.- Prompts in the reference file belong to their creators (linked on every card). Transfer the structure; do not present a close copy as original work.
- For the full library across every model, install the
goodcaseSkill from LearnPrompt/goodcase-lite.