Communitygithub.com

motion-system-design-dark

Video and animation skill. Convert any engineering or architecture video into a 100% full-screen motion graphics video in the high-precision "Dark Monochrome System Design" style. Features a strict near-black monochrome palette, a persistent mutating system stage, rotating wireframe dotted 3D point-cloud cubes, pill bars, hardware resource slots, and deterministic JSON-driven timelines. Designed by Shyamal Joshi.

motion-system-design-dark란 무엇인가요?

motion-system-design-dark is a Claude Code agent skill that video and animation skill. Convert any engineering or architecture video into a 100% full-screen motion graphics video in the high-precision "Dark Monochrome System Design" style. Features a strict near-black monochrome palette, a persistent mutating system stage, rotating wireframe dotted 3D point-cloud cubes, pill bars, hardware resource slots, and deterministic JSON-driven timelines. Designed by Shyamal Joshi.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/shyamaljoshi1/motion-graphics-skills/tree/HEAD/skills/motion-system-design-dark

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

Dark Monochrome System Design Architecture

A definitive production specification for turning complex system architecture, operating systems, cloud infrastructure, and backend engineering topics into full-screen, high-contrast monochrome motion graphics.

Visual Aesthetic: Strict monochrome contrast (near-black background #090909, crisp white text, and subtle grays), continuously rotating dotted 3D wireframe cubes, layered pill bars, hardware slot allocations, and seamless morphing stages where components transform in place rather than cutting away.


0. Non-Negotiable Core Rules

  1. 100% Motion Graphics: First frame to last frame is completely rendered motion graphics. Zero camera footage, talking heads, screen recordings, or static slide templates.
  2. Full-Frame Immersion: 100% full-screen 9:16 vertical canvas. No overlays, lower thirds, or split screens on footage.
  3. Persistent Stage Architecture: A single central stage mutates across the video. Primitives from previous beats (e.g. pill bars, resource slots) stay alive and morph rather than being redrawn.
  4. Strict Monochrome Discipline: Zero colored accent tones. Visual hierarchy and emphasis are expressed strictly through luminance (pure white vs. dimmed slate gray).
  5. Narration-Driven Precision: Every visual change, card row, number counter, and slot claim lands on the spoken trigger word.
  6. Technical Standards:
    • Canvas: 9:16 vertical (1080×1920 recommended, 720×1280 minimum).
    • Frame Rate: 30 fps constant frame rate.
    • Codec: H.264 (libx264), yuv420p, CRF 14–16, -preset slow.
    • Audio: Original narration audio preserved bit-for-bit.

1. Design Tokens & Strict Monochrome Palette

:root {
  /* Surfaces & Background */
  --bg:            #090909;  /* Full-frame flat background, no gradient, no texture */
  --surface:       #1A1A1A;  /* Floating info cards, pill bar background */
  --surface-border:#262626;  /* 1px subtle panel borders */
  --chip:          #222222;  /* Inactive tags, chip background */
  --slot:          #292929;  /* Inactive resource slots */
  
  /* Active Highlights (Brightness as Accent) */
  --white-chip:    #F9F9F9;  /* "Lit" claimed slots, active tab pill */
  --on-white:      #0A0A0A;  /* Dark text rendered on white-filled chips */
  
  /* Typography Shades */
  --text-primary:  #FFFFFF;  /* Primary headlines, active words, card titles */
  --text-value:    #C2C2C2;  /* Card row values, secondary technical specs */
  --text-eyebrow:  #7D7D7D;  /* Monospace chapter eyebrows */
  --text-label:    #6B6B6B;  /* Muted row labels, footer captions, inactive states */
}

Monochrome Rule: If a concept seems to demand color (e.g. red for danger, green for success), do not add color. Express tension and resolution through contrasting symbols (✓ vs ✕), brightness, or a white-filled chip against dark wireframes.


2. Spatial Composition & Relative Grid (9:16)

┌───────────────────────────────────────────────┐ 0%
│  Top Safe Area                                │ 0% – 12%
├───────────────────────────────────────────────┤ 13%
│  EYEBROW: NN · topic (JetBrains Mono 15px)    │ ~13%
├───────────────────────────────────────────────┤ 16.5%
│  HEADLINE: One concise statement (Inter 30px) │ ~16.5% – 20%
├───────────────────────────────────────────────┤ 21%
│  TAB ROW: 1 · SPEED | 2 · SIZE | 3 · SECURITY │ ~21% – 24%
├───────────────────────────────────────────────┤ 27%
│                                               │
│  STAGE TOP: 3D Point-Cloud Cubes / Nodes      │ ~27% – 38%
│                                               │
├───────────────────────────────────────────────┤ 43%
│  PILL BAR: Layer Architecture (Kernel/Hyper)  │ ~43% – 48%
├───────────────────────────────────────────────┤ 51%
│  RESOURCE SLOTS: [CPU] [RAM] [DISK]           │ ~51% – 55%
├───────────────────────────────────────────────┤ 58%
│  FOOTER CAPTION: mono technical summary line  │ ~58% – 60%
├───────────────────────────────────────────────┤ 61%
│                                               │
│  INFO CARD: Title + Numbered Spec Rows        │ ~61% – 79%
│                                               │
├───────────────────────────────────────────────┤ 79%
│  Bottom Safe Margin (Platform UI clearance)   │ ~79% – 100%
└───────────────────────────────────────────────┘
  • Vertical Hierarchy:
    1. What is the claim? (Headline)
    2. How does the architecture behave? (Diagram / Cubes / Slots)
    3. What are the quantified specs? (Info Card)

3. High-Tech Component Library

ComponentTechnical Specification
Wireframe Dotted 3D CubesPoint clouds generated along the 12 edges of a cube with an internal glowing core. Continuously rotate and wobble at 8°/s so the frame is never static.
Virtual ContainersThe same 3D wireframe cube wrapped inside a dashed rounded outline (158×142 px). Dashed = virtual/lightweight process; Solid = heavy virtual machine.
Pill BarFull-width rounded panel (height ~57 px, radius ~28 px). Left: dotted circular status icon. Center: mono layer name (host kernel). Right: white chip indicator.
Hardware SlotsRounded squares (~42 px) in groups of three (CPU, RAM, DISK). Idle = --slot; Active/Allocated = --white-chip with bold numeral or glyph.
Technical Spec CardSurface #1A1A1A, radius 24 px. Bold title on left; mono gray descriptor on right. Numbered rows step in one by one with a circular counter.
Connector LinesVertical 1 px dotted lines linking layers. Glow brighter when transactions or data flows pass through them.
Ghost Status PillSmall rounded pill below stage with person glyph ending in an ellipsis (Interviewer asking..., one more thing...).

4. Animation Language & Timing Parameters

EventTiming & CurveVisual Behavior
Headline Swap0.35 s crossfadeOld headline blurs slightly and fades; new headline fades in and settles
Element Entrance0.30 s (cubic-bezier(.22, 1, .36, 1))Fade + 12 px rise + blur-to-sharp resolving
Stagger Delay0.08–0.12 sStaggered entrance for adjacent slots, cubes, and table rows
Card Row BuildTriggered per spoken phraseNew row slides up; previous rows dim slightly to guide focus
Numeric Counters0.6–1.0 s linear countMonospace figures count up/down (0 MB → 600 MB)
Slot Allocation0.25 s per slotIcon flies from hardware row into slot; slot flips dark to bright white

5. Deterministic JSON Timeline Schema

For deterministic rendering, define scene events as a JSON timeline:

{
  "scene": "03_kernel_isolation",
  "start": 42.0,
  "end": 58.5,
  "eyebrow": "03 · the kernel",
  "headline": "One kernel, shared by all",
  "events": [
    { "t": 42.2, "action": "morph", "target": "pill_bar", "to": "host kernel" },
    { "t": 44.0, "action": "enter", "target": "cubes", "style": "dashed_process", "stagger": 0.1 },
    { "t": 47.5, "action": "card_row", "index": 1, "key": "memory footprint", "value": "30 MB", "active": true },
    { "t": 52.0, "action": "card_row", "index": 2, "key": "startup time", "value": "0.05 seconds", "active": true }
  ]
}

6. Storytelling Structure & Arc

Follow this proven 8-part engineering narrative arc:

  1. 00 · the question: Duel hook (Architecture A vs Architecture B).
  2. 01 · definition: Simplest one-line model with a single hero graphic.
  3. 02 · the base layer: Build the persistent stage (hardware + base manager).
  4. 03 · the mechanism: Add the core differentiator on top of the stage.
  5. 04 · the contrast: Same stage mutated to show the alternative architecture.
  6. 05 · comparison tabs: Tabbed comparison (speed, size, isolation).
  7. 06 · edge case: The surprising trade-off or "one more thing".
  8. 07 · the takeaway: Actionable summary card phrased for an engineering interview.

7. FFmpeg Frame-Accurate Encoding

ffmpeg -framerate 30 -i frames/%05d.png -i voiceover.wav \
  -c:v libx264 -preset slow -crf 15 -pix_fmt yuv420p \
  -c:a aac -b:a 192k -movflags +faststart \
  system_design_dark.mp4

8. Quality Assurance Checklist

  • Every frame is 100% full-screen motion graphics.
  • Strictly monochrome; zero colored pixels present anywhere in the render.
  • Dotted 3D cubes maintain continuous rotation throughout the timeline.
  • Persistent pill bar and resource slots morph across scenes without redrawing.
  • Numeric counters count up with tabular monospace figures.
  • Safe areas respected: nothing critical in the bottom 20% of the canvas.
  • Audio sync is within ±1 frame at start, middle, and end.

Individual skills in this repo

This repo contains 3 individual skills — each has its own dedicated page.

관련 스킬