design-screen-storyboard

Storyboards and animatics

Version-Timestamp: 2026-09-11T19:51:13-04:00

Objective and inputs

Produce storyboards and animatics within the user's screen-content scope. Read the screen workflow and reuse approved upstream files, brief, source versions and constraints. The catalog dependency display-content identifies required information, not a mandatory rerun. Missing inputs are explicit assumptions or scoped holds.

Method

Map message beats to time, specifying entry, hold, transition and exit. Include frames, copy, assets and intended viewer takeaway. Use an animatic to resolve reading time before effects. Duration follows operator constraints; include mid-loop entry and silent viewing.

Output

Timed storyboard and low-cost animatic with unresolved decisions. Carry source version, candidate status, editable file location, dependencies, limitations and next owner in the handoff. Choose an available tool suited to the artifact; a skill does not establish authentication, paid allowance or native editing capability.

Acceptance

Check all claims appear long enough to evaluate, sequence fits duration and essential meaning does not rely on audio. Record actual evidence and failures. Never label an unexecuted check passed. Maintain the approved baseline until the candidate is accepted.

Applied decision method

Version-Timestamp: 2026-09-27 14:25:39 AST

Read Screen content and motion when designing meaningful beats, readable holds and midway entry. The card adds original worked reasoning; reuse this capability's existing prerequisites, records and acceptance checks. Load only the selected card. Its fictional example is teaching material, not tested project evidence.