T8mars/minimax-h3-prompt-skill-T8 / skills/dual-support-elastic-character-control
dual-support-elastic-character-control
VerifiedCreate original short videos using the 双支座弹性偶|控制器驱动形变复位 Creative DNA for MiniMax H3 or Seedance 2.0. Use when the user wants this causal, camera, motion, rhythm, or payoff structure with new subjects and surfaces.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.7 KB |
| agents/openai.yaml | config | 522 B |
| references/summary.md | markdown | 1.6 KB |
| references/template.md | markdown | 5.2 KB |
references/template.md
View on GitHub# 双支座弹性偶|控制器驱动形变复位 Template
## Mechanism
Bind two simple graphic characters to two continuously visible physical supports. Change only one measurable support parameter at a time so the pair first demonstrates a shared response, then an asymmetric independent response, then a third materially different relation test. The order, axis and controller may change across instances; character identity and support ownership must remain readable until both supports stabilize into a legible paired state.
## Invariants
### inv-01
- Rule: Establish two distinct graphic characters, each visibly bound to one stable physical support.
- Purpose: Creates independent ownership before deformation.
- Failure if removed: Floating characters with no support cannot make gesture causality readable.
### inv-02
- Rule: Change one measurable support parameter and make both characters answer through a readable shared response.
- Purpose: Defines the first causal response rule without prescribing compression or an axis.
- Failure if removed: Changing body shape without a matching support change feels arbitrary.
### inv-03
- Rule: Change a different parameter asymmetrically so one character responds while both bindings remain intact.
- Purpose: Proves independent control inside the duet.
- Failure if removed: Applying identical changes to both sides never demonstrates separate ownership.
### inv-04
- Rule: Apply a third materially different support relation or controller path without repeating the prior response.
- Purpose: Shows a reusable control grammar rather than one canned deformation sequence.
- Failure if removed: Repeating the same axis and order makes the middle a surface routine.
### inv-05
- Rule: Synchronize both supports and finish with two legible characters still attached to their original sides.
- Purpose: Restores the relationship after extreme deformation.
- Failure if removed: Losing a face, swapping sides or ending as abstract ribbons breaks identity closure.
## Variable Slots
| Slot | Constraint |
|---|---|
| lead_subject | An original stable subject or pair with a readable role. |
| setting | A new setting with fixed spatial anchors and no source-specific surface. |
| escalation_variable | One causal variable that changes through visible stages. |
| performance_rule | A restrained acting or motion rule that keeps the mechanism legible. |
| camera_grammar | An information order that proves each state without copying source shot boundaries. |
| payoff | A clean final physical, informational or social consequence. |
| sound_family | An original hierarchy of diegetic cues; no unsupported source-audio claim. |
## Required Human-Facing Anchors
- Establish two distinct graphic characters, each visibly bound to one stable physical support.
- Change one measurable support parameter and make both characters answer through a readable shared response.
- Apply a third materially different support relation or controller path without repeating the prior response.
- Synchronize both supports and finish with two legible characters still attached to their original sides.
## Anti-Copy Boundary
- the source dark-haired woman in a white sweater and beige trousers
- the source cream goose-like cartoon blobs with tiny eyes and orange beaks
- the source apartment interior and fixed vertical framing
- the source exact palm choreography and extreme long-neck ending
- MiniMax and Hailuo AI watermarks
## Transfer Tests
1. In an original magnetic observatory, two motorized gimbal bases carry distinct luminous seed-pod characters. Opposite base rotations twist the pods independently, both bases then orbit one central marker while the tethers remain separate, one base tilts to create a single oblique sail response, and the bases finally dock side by side so both pods settle into compact readable forms.
- Preserved: inv-01, inv-02, inv-03, inv-04, inv-05
- Changed: lead_subject, setting, escalation_variable, performance_rule, camera_grammar, payoff, sound_family
2. On a circular felt loom, two autonomous shuttle discs carry stitched cloud characters. A shared phase pulse makes both clouds ripple, one shuttle alone takes a zigzag rail and turns its cloud into a folded fan, the discs exchange inner and outer circular lanes without crossing ownership, and two latch stations stop them as a balanced paired emblem.
- Preserved: inv-01, inv-02, inv-03, inv-04, inv-05
- Changed: lead_subject, setting, escalation_variable, performance_rule, camera_grammar, payoff, sound_family
## Model Skeletons
### MiniMax H3
integrated_multimodal_description: [new subject, environment, ordered actions, camera, light and final state preserving every anchor]
overall_soundscape: [diegetic ambience, action cues and causal payoff]
non_diegetic_music: [original music arc or N/A]
### Seedance 2.0
任务:[原创实例意图]
总时长约[4–15]秒。
主体定义:[稳定人物、物体与空间关系]
事件或镜头:[按因果顺序实现全部锚点]
整体风格与画质:[原创媒介、光影、色彩与声音]
约束:[连续性、物理逻辑、反复制与结尾状态]
Adapt shot count to the user's concept. Preserve the causal mechanism, not a fixed storyboard.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |