Skip to Content
Starlight

Cookbook

Scene YAML that you can paste, for common looks in a venue: a hero word, a lower-third, a logo belt and more.

Use a recipe

Each recipe is a block of scene YAML. You paste it into a scene file, then load the file again in the app.

  1. Save your work in the app with ⌘S / Ctrl+S.
  2. Open the scene file (scenes/<name>.yaml) in a text editor.
  3. Paste the recipe. See Where to paste below.
  4. Change the names that the recipe borrows from the demo project. See What to change below.
  5. Save the file.
  6. In the app, choose File › Reload Project from Disk (⌘R / Ctrl+R).
  7. Look at the canvas. If the file has a mistake, a red line at the bottom left names it (Where a mistake shows).

Where to paste

  • A recipe that starts with - is one layer. Paste it into a comp's list under comps:, at the same indent as the other layers. A comp is a named group of layers.
  • A recipe that starts with loop:, comps: or surfaces: shows these top-level keys. Add its comps under your own comps:. Add its surfaces under your own surfaces:.
  • Never write a top-level key twice. YAML refuses the whole file. The message is Map keys must be unique.

What to change

  • Colours. The recipes use $primary, $base and $ink. These are names in the scene's theme:, as in the demo scenes. If your scene does not have them, use your own tokens. Or use a colour in quotes, such as "#ff8800". Otherwise the scene shows unresolved token $primary.
  • Surfaces. The recipes use the demo surfaces jumbotron, ribbon-main and vomitory. Use the names of your own surfaces.
  • Fonts and files. knockout-heavy and assets/bolt-rib.svg come from the demo project. Use a font name from your brand.fonts and a file from your assets/ folder.
  • Size. The recipes use the default design size, 1920×1080, unless they say otherwise.
  • Loop. A clock's period must divide the scene's loop. For example, a 2 s or 4 s clock fits a 4 s loop. Each recipe says which loop it needs. Clocks, keyframes and eases are explained in the glossary.
  • If the app has unsaved edits when you reload, it asks you first. It keeps the edits as a recovery draft.
  • When you save in the app later, Starlight rewrites the file in its own layout. Your YAML comments are lost (Saving and versions).
  • You can also paste a recipe to Claude and ask it to add the recipe for you.

Pop a hero word

The sports move: the word grows fast, goes a little too far, settles, then holds. Paste it into a comp's list. The scene loop must be 4 s, or a whole number of times 4 s (8 s, 12 s).

- transform:
    - text: "TOUCHDOWN"
      font: knockout-heavy
      size: 240
      fill: $primary
      align: center
      clock:
        period: 4s
        tracks:
          scale:
            - { phase: 0.00, value: 1,    ease: snap }
            - { phase: 0.12, value: 1.16, ease: overshoot }
            - { phase: 0.42, value: 1 }
            - { phase: 1.00, value: 1 }
  position: { x: 960, y: 420 }   # the top of the word
  • align: center centres the word from left to right on the transform's point. The top of the word sits on that point. So y: 420 puts a 240 px word near the middle of a 1080 px surface.
  • The scale grows from the word's centre, because a clock on a layer scales around the layer's centre.

Slide in a lower-third

A colour bar and a name slide in, hold, and slide out once per loop. The clock's period is the scene loop, 6 s here. The x keyframes add to the chip's position.

comps:
  name-chip:
    - transform:
        - shape: rect
          size: 760x96
          fill: $base
        - shape: rect              # the colour bar
          size: 14x96
          fill: $primary
        - transform:
            - text: "J. ALLEN · QB"
              font: knockout-heavy
              size: 48
              fill: $ink
          position: { x: 40, y: 24 }
      position: { x: 0, y: 880 }
      clock:
        period: 6s                 # = the scene loop
        mode: once
        tracks:
          x:
            - { phase: 0.00, value: -820, ease: overshoot }
            - { phase: 0.14, value: 120 }
            - { phase: 0.86, value: 120,  ease: snap }
            - { phase: 1.00, value: -820 }
  • Set loop: 6s at the top of the scene. Or change period to your scene's loop. A once clock that is longer than the loop never finishes.
  • name-chip is a new comp, so no surface shows it yet. Add - use: name-chip to the list of a comp that a surface shows. Or give a surface use: name-chip under surfaces:.

Run a seamless ribbon logo belt

The comp is made at the ribbon's real height, and the logos drift by whole gaps. So the loop has no seam (no visible jump). Use it for any ribbon belt.

loop: 4s
comps:
  band:
    - clone: { of: assets/bolt-rib.svg, count: 8, gap: 240,
               direction: x, drift: -240px/s }   # 240 × 4 s = 960 = 4 gaps: seamless
surfaces:
  ribbon-main: { size: 10080x84, use: band, fit: tile-x, design: 1920x84 }
  • If the scene already has a loop:, do not add a second one. Change drift instead, so that drift × loop is still a whole number of gaps.
  • The belt wraps every count × gap pixels: 8 × 240 = 1920, the width of the design.

Ripple a row (cascade)

stagger starts each copy a little later on the cloner's own clock. So one pop ripples down the row. Put the clock on the clone: write clock: beside clone:, not inside its { }. A clock inside the comp dot makes every copy pulse together.

comps:
  dot:
    - shape: ellipse
      size: 40x40
      fill: $primary
  main:
    - transform:
        - clone: { of: dot, count: 9, gap: 120, direction: x, stagger: 120ms }
          clock: { period: 2s, tracks: { scale: [0.6, 1.2, 0.6] } }
      position: { x: 420, y: 540 }

Breathe an idle background

A slow, soft movement keeps the background moving between the big moments. pingpong goes there and back in twice its period. So give it half the loop: 2 s in a 4 s loop.

- transform:
    - gradient: radial
      size: 1920x1080
      stops:
        - { offset: 0, color: $base }
        - { offset: 1, color: "#050810" }   # darker at the edges: hides tile seams
      clock: { period: 2s, mode: pingpong, tracks: { scale: [1, 1.06] } }

Feed three surfaces from one scene

One comp can feed many surfaces. Here the jumbotron shows the full comp, the ribbon shows a band, and the tunnel surface (vomitory) shows a cropped part. The scene needs the comps main and band, for example band from the belt recipe.

surfaces:
  jumbotron:   { size: 1920x1080, use: main }
  ribbon-main: { size: 10080x84, use: band, fit: tile-x, design: 1920x84 }
  vomitory:    { size: 384x640,  use: main, fit: cover }
  • cover fills the whole tall surface and cuts off the left and right sides of the comp.
  • A size here changes the surface's size for this scene only. project.yaml keeps its own size.

On this page