ııı motion.mdVideo style specification
Anthropic / V237

Claude Code Security — vulnerability scans and patches

Proceed through scan, findings, details, fix, and submission. Move closer to relevant content at each level so issues and solutions remain traceably related.

Composition and choreography Playable · Replaceable content
Overall choreographyRule example
0.00 / 50.00 seconds
Motion and composition example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Claude Code Security — vulnerability scans and patches · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="sequence"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>
Visual elementsScan containerRepository rowResult listIssue detailsFix buttonPatch cardPointer
MOTION LANGUAGE

Motion and composition

Local motion · Composition rules

01

Expand cards by information hierarchy

35.00s · Composition reference

Sand-colored background, hand-drawn black icons, white scan cards, and short serif feature statements.

Preserve the full entry → scan → issues → fix → PR sequence, revealing deeper result levels as it progresses.

02

Expand details before triggering a fix

Expand details before triggering a fixRule example
0.00 / 12.00 seconds
19–31 seconds · Motion example Open separately ↗
View HTML source
<!doctype html><html lang="zh-CN"><meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1"><title>Claude Code Security — vulnerability scans and patches · sequence</title><style>html,body{margin:0;width:100%;height:100%;overflow:hidden;background:#e1d9ca}canvas{display:block;width:100%;height:100%;object-fit:contain}</style><body data-mode="clip" data-start="19" data-end="31"><canvas width="1000" height="600"></canvas><script src="data.js"></script><script src="common.js"></script><script src="scene.js"></script><script src="bridge.js"></script></body></html>

Use close-ups of key lines in long code; do not treat both list and details as static full-screen screenshots.

Red labels indicate severity, while green diffs indicate fixes; status colors carry meaning.

03

Alternate actions and results

Start with the scan overview, expand issue details, then show the patch after fixing. Allow the current information to be read before moving deeper.

04

Replace the inspection task

Adapt to design checks: project→scan→issue→recommendation→revision, preserving correspondence between checks and solutions.

Severity, code, and result counts may change, but do not reverse status-color meanings.

SEQUENCE

Sections and rhythm

Click a section to seek to it in the choreography example above.

Composition reference at 0.00 seconds
0.00s
Composition reference at 10.00 seconds
10.00s
Composition reference at 15.27 seconds
15.27s
Composition reference at 27.00 seconds
27.00s
Composition reference at 35.00 seconds
35.00s
Composition reference at 41.00 seconds
41.00s

Visual references · Discrete still frames

KEEP THE RELATIONSHIPS

Creating other themes

  • Adapt to design checks: project→scan→issue→recommendation→revision, preserving correspondence between checks and solutions.
  • Severity, code, and result counts may change, but do not reverse status-color meanings.

Production constraints

Scan container / Repository row / Result list / Issue details / Fix button / Patch card / Pointer

  • Preserve the full entry → scan → issues → fix → PR sequence, revealing deeper result levels as it progresses.
  • Use close-ups of key lines in long code; do not treat both list and details as static full-screen screenshots.
  • Red labels indicate severity, while green diffs indicate fixes; status colors carry meaning.